"Following an interview that Tom’s Guide conducted with Rabbit CEO Jesse Lyu, in which he said the company was planning to launch next-gen AI hardware in 2026, we received a number of tips alleging that Rabbit has failed to pay since late summer."
The article is mostly talking about using the `cron` scheduler and running things at 2am on Sunday because there's especially low traffic. These cron jobs are "I don't care when it runs, but it should have minimal chance of causing problems."
Your use-case is totally different: "I want this job to run at this time" so the only lesson that applies to you is that the `cron` utility might behave weird during DST switches. No idea if it underlies your cloud provider, so it may be completely irrelevant.
I think people generally mean "state", but in the US-centric HN community that word is ambiguous and will generally be interpreted the wrong way. Maybe "sovereign state" would work?
I agree that suddenly adding a formatter to existing code could be disruptive. But how does "buy in from the team" work over time? If you hire someone new and they don't like the format rules, do you stop using the formatter?
I think it depends on the situation. If it's just not their preference then there's probably no need for a change. However, if it's going to prevent the new person from doing their job then a change is probably justified.
People being prevented from doing their job because of code formatting? In my nearly 20 years of development, that statement was indeed true, but only before the age of formatters. Back then, endless hours were spent on recurring discussions and nitpicky stylistic reviews. The supposed gains were minimal, maybe saving a few seconds parsing a line faster. And if something is really hard to read, adding a prettier-ignore comment above the lines works wonders. The number of times I’ve actually needed it since? Just a handful.
Code style is a Pareto-optimal problem space: what one person finds readable may look like complete chaos to someone else. There’s no objective truth, and that’s why I believe that in a project involving multiple people, spending time on this is largely a waste of time.
For example, "nit: maybe call the function updateCreditCard instead of updateCard"
If you disagree and think your function name is better (or that the two are equally bad), then I'm happy to go along with what you've got. But maybe you didn't think of this name or maybe I've convinced you. Either it's a quick fix (and no re-review needed) or you just dismiss my comment.
> As an American, a lot of UK geography and history questions are beyond my ken
But note that the UK-based contestants have no problem with sequences like "US vice presidents ordered by number of terms served" or "US capitals ordered alphabetically by the state they're in".
First, that archers can actually be more effective against mounted troops than foot: the mounted troops ride close together, horses are hard to fully armor, and one horse getting hit in the leg can cause a lot of chaos.
Second, at Agincourt, the French knights _walked_ through the arrow-fire quite successfully, but the effort (physical, mental, cumulative effect of small wounds) tired them enough that the English soldiers could beat them hand-to-hand. And that this ability to inflict small damage before the main fighting is why archers were valuable.
"Maybe the memes making fun of this person are, in fact, an exaggeration."
Sure. I don't need much convincing that Ballmer was only "bad" rather than "uniquely terrible". It seems a pretty normal thing that the negative reaction was outsized.
But I also think it would be more interesting to look at cases where the reaction by the haters was _spot on_. Or even where it _undersold_ how bad things were.
> “Can I use any language?” > > “Sure.” > > Move quickly, before he realizes his mistake.