| ▲ | 0xbadcafebee 5 hours ago | |
I also haven't written more than a couple lines of code in months, but I definitely do read the code. You have to, or at least provide lots of Claude Rules to help steer it. AI has too many bad coding practices by default. But you don't need to modify lines of code by hand, you can just tell it what to fix. I'm predicting a Docker for AI Coding. There really is a ton of stuff you need to set up to do AI coding/vibe coding in a way that's safe, has good results, and is fast. You don't just need a dev environment, you need a whole SDLC; codified good engineering decisions, test framework, credential management, an interactive UI and notifications, guardrails, a "waterfall" of progressive design/build/test, context management, and much more. It's too much for people to put together themselves without tons of time and experimentation. Same as containers, which is why Docker came about: to let an end user do complex things in an easy way. AI coding is like a self-driving car. Making the car move is easy; making it get you to the destination you want safely is very hard. | ||
| ▲ | DontchaKnowit an hour ago | parent [-] | |
"You can just tell it what to fix" For a lot of small changes, I am waaaaaay faster than an LLM. | ||