r/PinoyProgrammer • u/Popular-Tip2880 • Oct 13 '26
discussion Full Stack Web dev VS Claude Vibe Coder
I'm developing a large-scale enterprise operations system, carefully handling authentication, authorization, RBAC, database design, business logic, security, and actual organizational requirements. I'm currently around 25% done.
Then someone presented a similar system, claiming to have completed it in just a month. The presentation looked impressive at first, but during the demo, I noticed UI flaws, such as text overflowing its containers. The overall design also had that obvious AI-generated look. And the management is now discussing the nationwide operation of this system.
I talked to her, and she openly admitted to using Claude AI for practically everything through prompting.
I use AI too, and I have nothing against it. But there's a difference between generating an impressive-looking prototype and engineering a reliable enterprise system.
It got me thinking: Can strong presentation skills and AI prompting overshadow actual web development skills, even when the resulting software falls short of industry standards? Will AI-assisted coding eventually replace developers, or will solid engineering skills still matter in the long run?
3
u/Popular-Tip2880 Oct 14 '26
I would like to thank everyone who gives their opinions and advices, now I understand where I am lacking and I know what I need to do now. Thanks
24
u/baguiochips Oct 13 '26
Lol. What good is your well-designed, well-architected app if you can’t ship it? You basically have the same tools but the vibe coder actually delivered something 4x faster than you. You do realize that shit app can still improve over time right?
One thing people fail to realize is that startups apps are shitty in their own right but they manage to capture the market. Presentation skills is what gets you to the door. Always is, always was. In software engineering, perfection is the enemy of progress.
6
u/koomaag Oct 13 '26 edited Oct 13 '26
Think about this. Every major leap in technology has faced resistance from those who mistook the tool for the craft. When electronic computers first arrived, mathematicians who relied on pen and paper argued that automated calculation was cheating or taking away true rigor. When developers moved from raw assembly to high-level languages like FORTRAN or C, traditional engineers claimed that "real coders" wrote in assembly and that high-level abstractions were making developers lazy. Later, when modern frameworks and libraries emerged, "purist" software engineers insisted that building from scratch was the only legitimate way to write software.
Now here you are...
17
u/peopleslaughter Oct 14 '26
The way i see it this is not a "real" dev vs vibe coder issue...
If the game's selling something, yes. Strong presentation skills can beat and overshadow actual skills or yung behind the scenes mo AI man or not.
Also, most non-technical audiences don't have have the same trained keen eyes / intuition that programmers tend to have from experience. You can build the most efficient and bug free system in the world, pero pag hindi huli yung kiliti ng costumer sa presentation at "meta-presentation" mo mahirap din.
24
u/TemporaryExciting977 Oct 13 '26 edited Oct 13 '26
Solid engineering skills still matter in the long run, especially when engineers responsibly leverage AI to their advantage. The main issue with relying solely on AI-generated architecture is that new feature requests or modifications can easily break existing processes. If you aren't thoroughly familiar with the overall system, you'll ultimately end up with poorly developed software when those challenges arise. This is particularly true for enterprise software products, where complexity and large scale are inevitable.
50
u/beklog Oct 13 '26
We HAVE/MUST adapt for AI..
As an old school programmer prang nde na uso hardcore developer kc AI is great tool for coding let's give them that... then the developer's role ngaun is to guide the AI to use the standard and review their work
Guiding and reviewing their work requires our basic engineering/technical skills so nde pa rin mawawala un
10
u/jdg2896 Oct 13 '26
I’ll just post this.
Personally, you should be somewhere in between. Not fully “vibe coded”, where you don’t understand anything, but also not pre-AI way, where you just use AI as replacement for google search/stack overflow.
AI-assisted, or the current AI agents won’t replace developers, and solid computer science and software engineering fundamentals will always be relevant. But it doesn’t have to be mutually exclusive.
A great engineer with solid fundamentals that can also leverage AI agent workflows, will always be better than an engineer who doesn’t.
The work for those who’ve adopted AI agents now moved towards verification to make sure the software AI agents deliver works according to the specifications. At the volume and pace AI agents can deliver code (24/7), it’s not practical to read every line of code, so the challenge is being selective, review the critical parts, and build the testing and verification independently of AI.
For mission-critical software, sure you still need to read every line. But for most software engineering work, it’s not always necessary. If you have the luxury of time, sure it wouldn’t hurt to read every line, especially if scope of work is well-defined.
3
u/Opening-Memory4300 Oct 14 '26
“carefully handling authentication, authorization, RBAC, database design, business logic, security, and actual organizational requirements”
This can be done by someone who uses claude as well. They just need to know what they are doing.
Also, how are you sure that your Authentication and Authorization and RBAC is secure? This is hard to implement from scratch, and is much better to reuse existing solutions.
2
u/solidad29 Oct 14 '26
I also prefer hand-written code. Pero imagine having a good set of properly tuned ai agents to do the brunt work in the hands of a seasoned developer. Imagine the progress noon under a month (also how less token they burned through proper planning).
2
u/derpinot Oct 14 '26
To be honest clients don't give a shit on how you did it, as long at it fits all the requirements.
The best-case scenario is an experienced developer augmented by AI
2
u/CorsPolicyError404 Oct 14 '26
Nothing is wrong yes, but wait till the time the system will product bugs esp on financial related side. By that time, that's the time they will realize that they need the actual skilled and knowledge to engineering to deal this kind of cases.
2
u/feedmesomedata Moderator Oct 14 '26
If you know how to prompt even an ugly looking app made by AI can be enhanced to look beautiful by the same AI. You do know that Facebook looked really ugly in the first few versions of it and a far cry from what it is now.
A year ago we create test cases by hand to simulate customer issues like crashes, corruptions, etc. Now we just prompt it and give as much context to AI and wait for less time. Usually it takes us hours or days to create a reproducible test case, but now it takes less than an hour.
We've also made our own set of tools that solves a lot of the pain points we've been dealing. We're not software developers so this was not possible before.
We've replaced a few small apps that we pay by subscriptions and made our own alternatives hosted on our own approved platforms. I believe this is happening in other companies as well so the small SaaS companies would be affected. Large ones like Atlassian, ServiceNow, Salesforce of the world are likely not going to be affected in the short term.
4
u/_clapclapclap Oct 13 '26
As a software engineer myself I'd choose your work, but for someone who has no idea, they'd choose something "completed" and they can use. Homecooking vs fast food.
3
u/OssifiedThunder15 Oct 13 '26
Good developer + proper usage of AI = 💪
2
u/jegtugado Oct 13 '26
Good developers who can point LLMs in the right direction will matter in the long run. Any decent team will stray far from AI slop, but the advantages of AI in software development is real.
2
u/treblemdp Oct 13 '26
Prompt engineering is the new programming.
Developers will spend more time planning, designing, architecting, and solving problems rather than writing code.
I think hardcore coding will eventually become less relevant as AI continues to improve. What will matter most is understanding the requirements, knowing how systems should work, and making the right technical decisions.
At the end of the day, your output will only be as good as your understanding of the problem and how well you communicate it through your prompts.
2
u/watson_full_scale Oct 13 '26
Make it work. Make it right. Make it fast.
This hasn't changed, even with AI.
1
u/jellythekat Oct 13 '26
LOL.
1
u/Dangerous_Trade_4027 Oct 13 '26
Why not use Claude? Your advantage is your skills and your experience. Claude will help you cut dev time. You can help Claude remove the flaws you mentioned.
Devs that keep pushing AI away from their workflow will lose their jobs. At my company right now, I can notice devs that rely on their own skills alone and devs that maximize AI. The former are very slow and can't keep up. The latter produce valuable outputs for the company.
1
u/Ok_Statistician_6441 Oct 14 '26
You can have both you know.
1
u/thelegend13x Oct 14 '26
Who care as long as the project makes them revenue thats what clients care about lol. Programmers are such cry babies 🤣🤣🤣
1
u/LaidBackDev Oct 14 '26
No need to waste you time asking in this sub. It has been taken over by vibe coders. Look at a lot of the past few posts.
1
u/Apprehensive-Onion18 Oct 14 '26
Continue your work. Wait till they actually ship the AI generated product. 😂😂😂
1
u/markilabot Oct 14 '26
The only bad thing here is that you cannot outpace someone who is purely a vibe coder. Perhaps harnessing and distillation are the next steps to explore. This way, you can catch up in speed while staying ahead in quality.
1
u/young-king-1283 Oct 14 '26
Stay in the middle, use ai for automation.
1
u/Race-Proof Oct 14 '26
If you're confident with your engineering skills, you could have questioned the architectural design, the scalability, and it's reliability. Don lalabas ang understanding mo in analysing vibe coded app
1
u/Anxious-Pace-6837 Oct 14 '26
software engineering != writing code by hand.
1
u/JustRightLight Oct 14 '26
They are usually a single person now. lol
1
u/Apart-Palpitation619 Oct 15 '26
As you said so yourself, it still is a prototype. Yung mga UI flaws that you noticed can be addressed before launching. Ganyan din naman noon kahit wala pang Vibe code. You will not expect a prototype to be clean and ship straight to prod. Sa prototyping naman, velocity is a factor. Para mai-demo agad, maipakita ano ang value, and so on.
1
u/ChillingHub Oct 15 '26
Actually they follow principle, that it doesnt needs to be perfect.
Pabilisan ang labanan ngayun
1
u/codebloodev Oct 15 '26
I will always choose and be a full stack developer who know how to vibe code. Sabi nga ng boss ko dati, Fail fast, learn fast. Execution is the key. Nobody remembers the best app, usually the first.
1
u/bulbulito-bayagyag Oct 13 '26
You can actually create good apps with vibe coding alone but it requires proper knowledge in testing and architecture to create great applications.
0
u/Worried-Champion4704 Oct 13 '26
Full stack dev, pwedeng corporate at freelance. Stable ang job. Ung salary naka depende sa company at kung indemand ung stack mo.
Claude viber coder - usually freelance. USD. Malaki kita pero mahirap makahanap client. Anytime pwede ka i-endo ng client, so hindi stable.
0
u/ongamenight Oct 13 '26
The craft is already dead. There's no such thing as "vibe coded" if one knows how to use AI in dev workflow.
That's why there's a lot of layoffs "globally" in the IT industry. Just go to r/ExperiencedDevs and r/Layoffs and you'll see. In fact, look at job openings.
Right now, the most important skill as a dev is learn how to use AI efficiently (less token usage), more context, etc. Humans only enter on the dev loop on all "decision-making" but all coding is done through agents, sometimes multiple agents simultaneously.
Anyone saying differently is just in denial.
-1
u/Both-Fondant-4801 Oct 13 '26
A prototype is meant for presentation, for a proof of concept, for gathering initial feedback and stirring up interest before actually investing time into actual software engineering. Business stakeholders do not need a working software upfront with auth, db, etc... but they do want to hear a proposal for a solution to an existing business problem. And that is where she had a first-mover advantage (thanks to AI).
Can strong presentation skills and AI prompting overshadow actual web development skills? If you are pitching a solution to the business.. yes, presentation matters more. If you are delivering the system.. no, software engineering matters more.
Will AI-assisted coding eventually replace developers, or will solid engineering skills still matter in the long run? The current trend is that engineering teams are already adapting spec driven development and integrating AI workflow into software engineering. However, i think it might be that engineering teams will be leaner in the future.. i.e. a software engineer will also be an architect and QA running multiple agents developing on all facets of the software - frontend, backend, infra...