The debate bothers me. Why anyone feels they need to only code one way or the other is strange. I do both. Actually, there are three options: By hand, hands off, and AI assistance while you code by hand. I'll do any of the three depending on what Im building or how I feel. Why does it have to be a hard line "Im not using AI anymore" or "I have to use AI for everything"?
I'm going back to coding by hand
51–54 of 54 posts
Re: I'm going back to coding by hand
#52Re: I'm going back to coding by hand
#53I'm not. I just don't want to implement code for reading files, setting up and population databases, logs, etc. manually anymore. I want to automate boilerplate, the occasional frontend code, etc. and focus on the parts that are interesting for me. This way I can get things done that I wouldn't otherwise.
I hope I never have to use your software
Re: I'm going back to coding by hand
#54Earlier quoted context omitted.
>I build the base manually and then I can iterate with AI faster once the fundamentals are solid. I've had tremendous success with this approach as well.
Why do we need humans in the loop, what exactly can’t be replaced by an AI in your workflow? It sounds like having another AI telling the first AI not to “drift” away from the fundamentals would do the trick? Does this activity require some kind of super human abilities that can’t be done by an AI? What exactly is it that gives satisfaction? Bossing around a junior developer or reviewing code generated by said junior…
Just as I speak, it is reworking a UI compositor design, after I told it to use the reactive framework I have built for damage restoration, because in the end, this is a reactive problem. The implications, it drew on its own. But I had to nudge it.