In the 80s. If you look at what your examples have in common, you’ll notice you’ve heard it in the 80s.
Too bad 80s nostalgia is all the hype nowadays, but at least this seems to be passing in other subcultures. I really hope it passes in software development too.
Oh, man. Can you tell what the second step is? I’d really like to learn that.
Well, they have a choice of pandering to this one large customer for whom they’ll always be the untrusted underdog, or pandering for the larger, more diverse market.
They never managed to become profitable as the untrusted underdog, so the option of keeping doing the same was obvious, I guess.
Lol! Be like GitLab instead:
1 - Be the underdog with good reputation in a market completely monopolized;
2 - Have the incumbent self-destruct by vibecoding its product and pushing AI above every other feature to its customers;
3 - Loudly announce that you are leaving your past good behavior behind, and that you are betting everything on vibecoding and pushing AI to your customers!
Modern CPUs can manage what interrupts them. Almost nothing actually does.
Computers have a CPU just to get in the way of things interrupting the main CPU.
It’s a HELLO II keyboard. Probably the next model after the original one.
Cron is absolutely lawful, not neutral. If there’s any deamon that defines lawfulness it’s sendmail, but after it, it’s cron.
What are you guys doing to your JS packages for them to last so long?
You can set a connection pool. Or use a database proxy.
EDIT: Oh, you are using Django for shell scripts?
There’s no dead person out there complaining that they spent too much time in a computer…
So, if I’m reading things right, anything that runs on Z-Wave or Zigbee will necessarily run locally, because those are mesh protocols?
Anyway, thanks a lot. Those are really simple keywords to check.
I’ve been looking for some smart outlets, and it seems impossible to discover which ones can be used with normal well-known protocols and which can only be used through a phone app locked into a cloud service.
You are saying that the error messages terminate at some point?
There’s a good reason sysv isn’t on the meme.
If you think it never broke, that’s because you weren’t doing anything different or creating anything that required it.
That said, systemd had a tendency to break even if you didn’t either. But nowadays the bugs are mostly fixed, and the stupidity is contained on parts people mostly don’t adopt.
Running the code again is fast and requires no thinking. Finding the problem is slow and requires a lot of thinking.
It’s worth looking under the light-post in case your keys somehow rolled there. Just not for long.
The fact that this is becoming the most known quote from that mission is amazing on several good and bad ways.
Are extensible records usable already?
Not that I would pick TS because of that, but the disdain is undeserved when it has some very useful features that Haskell has been trying to copy for years.
Last time I said “No! This is getting silly!” and decided to try all those language-server GUI text editors I lost a couple of weeks and decided to nuke my emacs config and make LSP actually work there instead.
You can always do pre-Modern web development. There’s nothing stopping you.
In fact, with the modern browsers, it’s better than ever.
It’s agile if the plan is constantly reviewed with every new information in mind and you can change what you are working in to better implement it.
If you do do Scrum, that’s almost never the case.