About the risk that vibe coding may go astray. Some irresistible quotes:
> […] Claude is a fuckin' slot machine, not a human. Every query is a pull of the lever, with potentially infinite upside or downside. It's addictive, sure. Lots of dopamine and adrenaline, and what's more, over time, your outcomes are even improving. But your slot machine doesn't "get" you. You don't have a beautiful rapport with it. You're just getting better at prompting, and getting consequently luckier with your pulls. Any bond you might perceive there is illusory.
and
> Paraphrasing astronaut Frank Borman, you should be using your superior judgment (only vibe code when there's an instant Undo) to avoid having to use your superior skill (vibe coding your way out of the mess you made.)
I've had good results recently by deleting all my social media apps from my phone, BUT allowing myself to use them through Mobile Safari. And I did not bookmark them; e.g. for Instagram I type "in" and then Enter.
This gives me some friction, without having to go cold turkey. All the popular social media sites have mobile websites that are "good enough", but slightly clunkier than the apps, and also they can't send me notifications.
My phone screentime per day has dropped by about 1/3rd.
I did the same, and additionally set my display to grayscale. I don't even want to open social websites unless I actually wish to browse them. The compulsive fix these apps provided when I was bored or waiting was taken away and my habit subsided.
A young man went back to visit his old economics professor, under whom he had studied many years earlier. He took a look at the final exam the professor was preparing to give the students. He said, "Professor, this exam is identical to the one you gave us year ago!"
The professor replied, "That's okay, all the answers have changed."
Scons is definitely slow in some scenarios. It has O(m * n) performance if a rule has m inputs and n outputs. I tdiscovered this when working with a code base that had a single rule with all .ts files as inputs, and all .js files as outputs. As the number of files we had got bigger, SCons got painfully slow. Of course we can rewrite our rules, but that shouldn’t be necessary, especially since it was quite hard to figure out why our builds got so slow.
I stumbled across this, and it's nice. It's a very straightforward walkthrough of what happens when a small program calls open() and then read().
If you look up today's Linux source code, the code has of course evolved and is a bit more complex, but not a lot more. The nice thing about the 2001 code is that it's still dead-simple.
> […] Claude is a fuckin' slot machine, not a human. Every query is a pull of the lever, with potentially infinite upside or downside. It's addictive, sure. Lots of dopamine and adrenaline, and what's more, over time, your outcomes are even improving. But your slot machine doesn't "get" you. You don't have a beautiful rapport with it. You're just getting better at prompting, and getting consequently luckier with your pulls. Any bond you might perceive there is illusory.
and
> Paraphrasing astronaut Frank Borman, you should be using your superior judgment (only vibe code when there's an instant Undo) to avoid having to use your superior skill (vibe coding your way out of the mess you made.)