Maybe it's just because both our industry as well as the internet always going to the extrema, but I'd love to see a nuanced take on the subject at some point.<p>My experience so far is middling; I found that it can be extremely helpful when working on novel things; greenfield projects it can lay a solid foundation for. If I'm learning some new framework it can shit out a first version that helps me understand how the thing works.<p>However, as soon as things get a bit more complex, they immediately start shitting the bed. Working in existing codebases of more than like 25 files and they become useless. Hell, even asking some models to document a 150 line batch install file made it hallucinate all kinds of stuff that didn't exist.<p>Furthermore, you really do have to talk to them like they're autistic idiot-savants. Precise steps, boundaries, everything. But even then they often just go off into the deep end. Even when I explicitly tell it to do one thing, one thing only and not change anything else, over 50% of the time it starts changing everything.<p>It's another tool, and like with all tools you need to know how and when to use it, I guess. As an industry we're not going to finger out the right ways if half the world refuses to use a powerdrill because well gosh darn it, hammers have always been good enough, and the other half swears up and down you don't need cement anymore because you could just as easily screw bricks together.
I had a fun day with replit yesterday. I signed up to try it out after someone at work mentioned it.<p>I gave it a really simple challenge: a note taking app. Allow the user to write a sentence of plain text, and add it to an array with a time stamp. Show the text on screen. Save it in local storage.<p>I could hand code this in about ten minutes.<p>Replit went off and built a truly impressive UI that looked like something that would take me a couple of evenings to pull together. It was professional and polished, but it didn't work. Hitting enter to add the item did nothing.<p>I chatted to it and explained. It confidently did a few revisions but didn't fix it.<p>It started adding logging and asked me to paste in the logs. After each subsequent paste it would say some variation of "ah I see the problem" and revise again.<p>After the third time, I didn't reply with the console logs and instead suggested we change tack. Replit completely ignored my input and carried on talking as if I was following instructions "yes I see the issue now, ok I've fixed it"<p>It was just a string of hallucinations, pretending to take user input but it fact not doing so. In the end I started asking it completely off topic questions but it had an imaginary convo with me instead. I gave up.<p>I've had much more success with non agentic LLMs like Gemini or Claude but they all are great at the initial response and slowly degrade add the conversation continues
Imo there is nothing wrong with generating code with AI, it's the effort spent on supervising the quality of product that matters.<p>But that requires you to have certain levels of knowledge on that domain to begin with, which is not something you can just "vibe" your way out, at least for now.
This was the dream. How it was supposed to be. Speak and it becomes. But developers found a way to gatekeep the whole process by inventing thousands of different languages/wheels over time.<p>And they held the keys. Now that they are steadily working most of themselves out of a job, they are still stuck with their hubris-tainted glasses, unable to move on.<p>6 months ago I had no idea how Github works. Now I have thousands of commits and I have learnt to git reset --hard as second nature now :-) Hell, yesterday I figured out by chance, how to only revert a particular file. So yeah, baby steps.<p>I am "building" every day, talking to my AI Coder friend. We are having a lot of fun. I don't go full Agent Mode. I am always on Ask Mode. (Because - hard lessons - you know)<p>I am learning about Lighthouse (97% aggregate for my Next.js app)<p>Yesterday I made my site an "App", because someone asked if "there's an app for that"<p>Now I know about PWA and all it's requirements. Cool.<p>The point is. I am having fun building stuff. And that would not have been possible for me a year ago.<p>Ask yourself. If you as a coding genius had to develop a program without any internet access, how far would you get?<p>So stop crying that the bar has been lowered. Raise the bar. Be the guy that can outsmart the AI when it tries to take over the world. There will be few of you needed, but the need will be critical. We will always need a few Myron Aubs. Just not millions of them.<p>Happy building (Even if you are not "coding")
I've been a software engineer for over 30 years and I have to say using AI and vibe coding has made me a 10x programmer. It's all about prompting and debugging, knowing how to fix issues is still a necessary skill and how to build/architect things from a prompt perspective. I've released 8 npm modules in the past 2 weeks alone just for some silly stuff I was using.