Support this channel on Patreon ► https://www.patreon.com/zoranhorvatGenerative AI can write code, but it cannot develop software on its own. Here is why the…
Support this channel on Patreon ► https://www.patreon.com/zoranhorvatGenerative AI can write code, but it cannot develop software on its own. Here is why the…
The problem isn’t the tool; it’s the lack of engineering foundations. Generalizing all AI-assisted development as ‘vibe coding’ is a massive oversimplification. There is a vast difference between a beginner blindly copy-pasting LLM output into a codebase they don’t understand, and a senior architect using LLMs as a high-powered assistant to speed up boilerplate, local schema generation, or parsing scripts. When you already know exactly how the underlying system operates, how memory is managed, and how to design clean software architectures, the LLM is just a productivity multiplier. You still design the data flow, audit the tool-use sandboxes, and review every single line of code. It doesn’t replace thinking; it replaces tedious typing.
As a senior developer I have serious doubts about the whole thing. Yes, I don’t do tedious typing anymore, now I do extremely tedious code review all day, my least favorite part of the job. And I have to be very vigilant because the AI is an idiot more often than not. Then when I finally publish my own code it’s time to go review my colleagues’ ai code and figure out what they missed in their review.
I don’t feel much of a productivity multiplier. I’m not saying we won’t get there, but this current iteration ain’t it.
you are a senior developer, start to transform your view in a senior architect. With AI there’s no more need of developers. An architect ius needed, and if it haas a solid dev backround as yours projects will change view. Technology is always changing and it’s hard to stay at pace. But if you look from an higher perspective your project your experience will only help the AI to do the Job for you
lol no. this is what a mediocre dev thinks.
Agree. Using AI as a tool is very productive. On the other hand, letting AI drive everything is insanely time consuming and tiring work due to back & forth prompts.
The most important thing developers forget is planning. I am senior and used to delegate dev to Junior Devs. If you have not enough experience in software architecture you are missing the most important thig: You cannot start developing. You must start planning, first of all require your agent to plan the steps for the target mission. Than examine the plan produced, ask to divide int single in testable units. Most AI Vibe programmers start with develop directions. That is wrong. The longest part of the job is to prepare the Agent to perform correctly
I’ve found AI powered autocomplete suggestions is actually quite nice. The time save when it gets it right is sometimes significant, but the time lost when it gets it wrong is usually negligible.
good grief, AI powered autocomplete is so bad it slows down my development by an order of magnitude.
It’s really set up for failure. It can only fall short of a deterministic, type-aware, contextual autocompletion, something IDEs have been supporting for like a decade.
Yeah, as soon as it was added I immediately saw a massive decrease in effectiveness. It starts by showing exactly what I want, then I hit tab and it autocompletes some bullshit that I do not want. I then have to undo and retype everything rather than using tab. It’s a insane failure of dev tooling.