Post

This is where my opinion has landed as well. Most of the “typing” is done by LLMs for my own code these days, but I’m still in my IDE, reading, watching the diffs go by, interrupting to tell it to do something differently, refactoring regularly to make sure the code is legible.

And I like this workflow a lot. If I have an idea that’s a big departure from the current state it’s very cheap to try it. I’m iterating with the LLM, I’m using the components I’m building constantly, tweaking small things that feel wrong. I can bring ideas to life I may have skipped on before.

And because I can talk to the LLM with my voice, it can interpret my words very well, it reduces the typing I do and thus the pain I get from tennis elbow. Hopefully those days will be soon behind me, but in the meantime this is a huge win for me.

And this has all made it very clear to me that whenever I see slop in the wild, it has little to do with the LLM. If you aren’t spending the time to make sure what you’ve built meets the quality bar, that’s a you problem. A skill issue, the kids might say. You can build great software with LLMs.