"However… even this might still be too slow. Why understand every line of code deeply if you can just build and ship?" Because the journey is the destination.

"However… even this might still be too slow. Why understand every line of code deeply if you can just build and ship?" Because the journey is the destination. Using AI extensively so far appears to be a path that mostly allows for a regression to the mean. Caring about what you're doing, being intentional, and having presence of mind is what leads to interesting outcomes, even if every step along the way isn't engaging or yielding the same output as telling an LLM to do it. I suppose if you don't care about what you're doing, go ahead and get an LLM to do it. But if it isn't worth doing yourself... Why are you doing it? Really, do you need those Chrome extensions? Alternatively, though... If you do, but they aren't mission critical, maybe it's fine to have an LLM puke it out. For something that really matters to you though, I'd recommend being deep in it and taking whatever time it takes. Also the tutor approach seems great to me. I don't feel like it's making me dumber. Using LLMs to produce code seemed to make me lazy and dumber though, so I've largely backed off. I'll use it to scaffold narrow implementations, but that's it.