This post reminds me of a conversation I had with my dad in the late 90s when I was mostly using VB6 and he was encouraging me to learn C++. Even back then, the syntax and ceremony of the language repulsed me, and my admittedly arrogant reply was that if I ever needed C++, I'd just hire someone to do that part for me. For what it's worth, I still stand by that strategy 30 years later. Delegation is one of the most po…
You can't talk about delegation without talking about what and who you're delegating. Delegating a demo or an exploration to a junior is fine if you can help them with feedbacks and make them grow and the business is not on the line. Delegating a critical development to a senior engineer you've vetted on previous delivery is fine too. Delegating a critical development to a junior is a recipe for disaster. Now, I'm st…
One thing I've noticed in my own behaviour is that the more tired I am, later in the day, the less rigorous I am about auditing what Opus suggests for me. This specific detail is a blind spot for many, I suspect.
The problem is always going to be the 2% of the time it does something horribly wrong on an architectural scale. You don't know when the poison pill might come.
Conclusion: if you wouldn't drive after drinking, smoking weed or staying awake too long, perhaps you shouldn't commit code generated by an LLM that is really amazing 98% of the time.