Who recommends Chrome? I don't.
448 karma · joined December 15, 2020
Who recommends Chrome? I don't.
The only repos I left on GitHub are forks and one with a bit of public engagement.
Email is one of the most gatekept interfaces in the world.
I am currently taking it.
From the landing page:
> Most of us, when we want to ship a product, we start at the beginning and with the most obvious ingredient: the product. Because when you can create, the act of creating feels most natural and straightforward. But it makes it so easy to end up with a product that nobody wants to buy. And isn't that every new entrepreneur's worst nightmare? All that work, and nobody cares.
People in the trades have a ruthless pragmatism that SV has forgotten.
"...a Pull Request is a delivery. It's like UPS standing at your door with a package. You think, "Nice, the feature, bugfix, etc has arrived! And because it's a delivery, it's also an inspection. A Code Review. Like a freight delivery with a manifest and signoff. So you have to be able to conduct the inspection: to understand what you're receiving and evaluate if it's acceptable as-is. Like signing for a package, once you approve, the code is yours and your team's to keep."
The metaphor has limits. IRL I sign immediately and resolve issues post-hoc with customer service. The UPS guy is not going to stand on my porch while I check if there's actually a bootable MacBook in the box. The vast majority of the time, there's no issue. If that were the same with code, teams could adopt a similar "trust now and defer verification" approach.
The article has a section on Modularity but never defines it. I wrote a post a few weeks ago on modularity and LLMs which does provide a definition. [1].
[1] https://www.slater.dev/2026/02/relieve-your-context-anxiety-...
It conflates purpose with outcome. I don't accept the premise that software's purpose is to "automate away other jobs". That may be an outcome, but software's purpose is to enable completely new possibilities. Think bicycles of the mind.
The Apollo guidance computer didn't replace astronauts. It made the missions possible in the first place because no human can continually correct the spaceship trajectory every 250ms for 10 days on end.
We're not receiving some cosmic karma. We're more like cotton pickers after the cotton gin. Someone still has to plow and plant.
https://www.slater.dev/2025/09/its-time-to-license-software-...
https://www.slater.dev/2026/02/relieve-your-context-anxiety-...
So I've been using cmux for a few hours this morning, and I like it. One thing I'd like to disable is the reordering of tab groups. Currently it shows the most recent notifications on top. This also makes the keyboard shortcut for a given conversation change all the time, which is a cognitive burden for me.
https://www.slater.dev/2025/08/llms-are-not-bicycles-for-the...
I can recommend Grokking Simplicity by Eric Normand. https://www.manning.com/books/grokking-simplicity
On the flip side, there's a story of an adventurous young couple who drove through the Democratic Republic of Congo [1]. They reported an incident where the road dipped and was submerged in water. Local men were standing around ready, for a fee, to chuck rocks in the water. The rocks piled up so the travelers' tires were able to grip the bottom and they were able to proceed on their journey. After they passed through, they observed in their rear view mirror the men now removing the rocks so the next driver would also have to pay.
I think wishing AI away to keep my moat is like wanting to remove those rocks. It's human to look out for #1 but it's a kind of tragedy of the commons.
The point of the article is to exonerate the pilots and expose a broader issue of honesty and transparency from Boeing and regulators that is covering up a systematic defect in Boeing aircraft design. The shared electrical bus renders other redundancies ineffective. The fact that the RAT has recently deployed 37 times uncommanded means another electrical failure at takeoff is a matter of time.
When you ask "why" 5 five times, it's never an individual. That's a big part of safety culture. Otherwise people cover their rears and don't divulge information that would save lives.
Aside: Isn't it wild that due to a software bug, Boeing directs airlines to reboot their 787-8s every 51 days?
$184M in profit or cost?
It's called a loss leader, not a gift, and it's a marketing and adoption tactic. They already bought the machines which cost about as much to run idle as at 100% utilization. Might as well put that idle capex and opex to use.
Or just collectively bill OSS the $184M and stop signaling virtue.
If those don't work, you may have a business case for building it.
I'm a founder and dev looking to for a good problem to solve. If the need could be proven (e.g. 10 people with decision power said they wanted it), I'd consider making it.
The GitHub encrapification finally affects me. I am militantly unwilling to pay per minute to use my own computer. Time to leave. I can trigger and monitor builds myself thank you very much.