81 karma · joined December 23, 2022
But they seem to be conflating human vision with computer vision.
A cheeky response is "their profit margins", but I don't think that quite right considering that their earnings per share is $-0.28.
I've not looked into Cloudflare much, I've never needed their services, so I'm not totally sure on what all their revenue streams are. I have heard that small websites are not paying much if anything at all [1]. With that preface out of the way–I think that we see challenges on sites that perhaps don't need them as a form of advertising, to ensure that their name is ever-present. Maybe they don't need this form of advertising, or maybe they do.
I don't the average mileage or a hydrogen vehicle nor tank size, so I'll take your word on that. Using your numbers and the map I plotted a route that does get you from San Diego to the Oregon border. But you will need a tow truck to meet you at the end, because there would not be enough fuel to get you back to Sacramento.
Travel time makes a big difference too, e.g. at peak times please keep your shoes on.
Today I will only apply to a job that requires me to make an account (like workday) if at least one of these criteria are met (i) I am exceptionally qualified (in my own eyes), (ii) I have a reference, (iii) I already have made an account previously. Though thankfully there are many (smaller) companies these days (at least in my current field) that don't require me to make an account.
> Notably, on Tuesday, Jun 27, 2023, we see two commits: 23:38:32 +0800 and 17:27:09 +0300. If we do the math, there is about a 9-hour difference between the two commits.
Putting it all into UTC we get:
23:38 - 8 = 15:38
17:27 - 3 = 14:27
That's not 9 hours by my numbers. Or another example:> Even more damning, on 6 Oct 2022, we see the following: one commit at 21:53:09 +0300 followed by another at 17:00:38 +0800. This is only a difference in a matter of minutes!
Putting it all into UTC we get:
21:53 - 3 = 18:53
17:00 - 8 = 09:00
I think these timezones were swapped (accidentally) by the article's author. If we do the calculation again: 21:53 - 8 = 13:53
17:00 - 3 = 14:00
That _is_ a matter of minutes.> Gatun Lake, which forms a key stretch of the canal system and provides fresh water for its locks, saw little rain this year, as El Niño triggered a withering drought.
https://fortune.com/2023/12/04/panama-canal-dry-backed-up-br...
Oh man that is my nightmare. Nothing says "broken system" like having to circumvent the system to get something done.
Leaving GitHub aside, I generally feel that anything a candidate does that adds friction to the general flow of the process will affect the candidacy of the candidate.
I have no evidence for this whatsoever but if you consider a person with 100 applications in their inbox, and if an AI has pre-sorted 80% of them, then that person is _probably_ more likely to start with the AI sorted applications.
For reference I am a backend dev at a SaaS company dealing primarily in Python & Go, doing HTTP/gRPC services and talking to databases.
Last night I attempted to make a program that would display an image and allow the user to click the image and then display the hex value of the colour under the cursor.
I wanted my application to use a crosshair cursor and after an hour of looking at the docs for NSCursor[1] and stackoverflow I just gave up.
I don't know how someone gets started in this ecosystem but I am sure once you know it this stuff is easy.
[1] https://developer.apple.com/documentation/appkit/nscursor
I would love to see a startup offer a budget to new hires to get advice from a financial advisor, of the employees choosing of course. Something like “we offer a reimbursement of up to X for new hires when they submit a receipt from a qualified financial advisor…”.
I think that it would be particularly useful to young hires or those new to startups.
I am interested to know more about your workflow given that you do not use pull requests, could you please elaborate on that?
I cannot imagine that you’re all just pushing to master.
- review feedback format
- variable naming
- keeping line lengths to 80 lines
- log message formats (sweet jesus the amount of time wasted debating that alone)
Whenever I see these conventions about commit formatting they generally seem to focus on the first line (notable exceptions being Git and the Linux kernel among others I assume), one line is rarely enough to describe the change – I’m not advocating for writing an essay for a 5 line change though in some cases it might be warranted.
Professionally I rarely see useful commit messages, by useful I mean something that could be read by someone without context and get a general understanding of why a change was made. Frequently I have seen “updates” / “wip” etc. in the master branch. More frequently I see that the quality of commit message decreases with an engineer’s seniority – though like every thing there are exceptions.