<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Achiri Divine</title>
    <description>The latest articles on DEV Community by Achiri Divine (@achiri_divine_d9dfb0d06d4).</description>
    <link>https://dev.to/achiri_divine_d9dfb0d06d4</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4240805%2F7a91645c-927a-4353-9e8f-32e586f4a03d.png</url>
      <title>DEV Community: Achiri Divine</title>
      <link>https://dev.to/achiri_divine_d9dfb0d06d4</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/achiri_divine_d9dfb0d06d4"/>
    <language>en</language>
    <item>
      <title>AN ARTICLE ON THE RELEVANT ON SOFTWARE RENGINEERING IN WEB APP AND THE DANGER OF VIBE CODING AND WEBAPPS WITHOUT THE PRACTICE OF SOFTWARE ENGINEERING.</title>
      <dc:creator>Achiri Divine</dc:creator>
      <pubDate>Thu, 12 Nov 2026 11:35:56 +0000</pubDate>
      <link>https://dev.to/achiri_divine_d9dfb0d06d4/an-article-on-the-relevant-on-software-rengineering-in-web-app-and-the-danger-of-vibe-coding-and-345o</link>
      <guid>https://dev.to/achiri_divine_d9dfb0d06d4/an-article-on-the-relevant-on-software-rengineering-in-web-app-and-the-danger-of-vibe-coding-and-345o</guid>
      <description>&lt;p&gt;&lt;strong&gt;Title:&lt;/strong&gt; &lt;strong&gt;Why Software Engineering matters in Web Apps and Why Vibe Coding Worries me&lt;br&gt;
published: true&lt;br&gt;
tags: webdev, software engineering, ai, beginners&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;Introduction&lt;/strong&gt;&lt;br&gt;
AI can now build a web app from one prompt. That's exciting, but I think we're skipping an important question: what happens after the app "works"?&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. What is vibe coding?&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You describe what you want, and an AI writes the code.&lt;/li&gt;
&lt;li&gt;You accept it without really reading or understanding it.&lt;/li&gt;
&lt;li&gt;If the page loads and the buttons click, you call it final.&lt;/li&gt;
&lt;li&gt;It's fine for a weekend experiment.&lt;/li&gt;
&lt;li&gt;It's risky once real users enter real data.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;2. Why software engineering is relevant in webapps.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Writing code is only one part of building a web app. Engineering also covers.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Planning what the app should do and who it's for&lt;/li&gt;
&lt;li&gt;Designing how the frontend, backend and database fit together&lt;/li&gt;
&lt;li&gt;Using Git so mistakes can be undone&lt;/li&gt;
&lt;li&gt;Testing features so they keep working&lt;/li&gt;
&lt;li&gt;Reviewing code before it goes live&lt;/li&gt;
&lt;li&gt;Protecting user data and logins&lt;/li&gt;
&lt;li&gt;Deploying safely and noticing when something breaks&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A web app isn't finished when it runs on your laptop. It has to survive bad input, attackers, traffic and time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. The dangers of vibe coding&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;-Security holes:&lt;/strong&gt; &lt;br&gt;
API keys in front-end code, forms that trust any input, weak logins, open databases. If you can't read the code, you can't spot these.&lt;br&gt;
&lt;strong&gt;-Code nobody understands:&lt;/strong&gt; &lt;br&gt;
When it breaks, you don't know where to start.      Each AI fix can break something else.&lt;br&gt;
&lt;strong&gt;-No tests:&lt;/strong&gt;&lt;br&gt;
 A small change can quietly break the booking form, and you find out when a customer complains.&lt;br&gt;
&lt;strong&gt;-Technical debt:&lt;/strong&gt;&lt;br&gt;
 Messy, repeated code makes every new feature harder to add.&lt;br&gt;
&lt;strong&gt;-Poor scaling:&lt;/strong&gt; &lt;br&gt;
An app that works for 5 users can crash at 5,000.&lt;br&gt;
&lt;strong&gt;-User data risk:&lt;/strong&gt; &lt;br&gt;
Weak storage or no backups can mean leaks or lost data.&lt;br&gt;
&lt;strong&gt;-Hurts learners:&lt;/strong&gt;&lt;br&gt;
 If AI writes everything, you never build debugging and design skills.&lt;/p&gt;

&lt;p&gt;It's not only an AI problem&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Apps built with no planning, Git, tests or documentation were always fragile.&lt;/li&gt;
&lt;li&gt;They work on launch day, then become hard to fix and hard to hand over.&lt;/li&gt;
&lt;li&gt;Vibe coding just gets you to that points faster.**&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;4. How I think  is the best way of how we should use AI&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Read and understand generated code before using it&lt;/li&gt;
&lt;li&gt;Keep secrets in environment variables, never in front-end code&lt;/li&gt;
&lt;li&gt;Test the important features, like forms and payments&lt;/li&gt;
&lt;li&gt;Commit small changes with Git so I can go back&lt;/li&gt;
&lt;li&gt;Plan features and data before I start prompting&lt;/li&gt;
&lt;li&gt;Treat AI as an assistant, not the engineer&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;5. Conclusion&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Vibe coding is good for quick ideas and prototypes.&lt;/li&gt;
&lt;li&gt;It can't replace software engineering.&lt;/li&gt;
&lt;li&gt;Apps people depend on must be secure, tested and maintainable.&lt;/li&gt;
&lt;li&gt;That comes from knowledge and discipline, not vibes.&lt;/li&gt;
&lt;li&gt;AI makes good engineers faster, but it can also help careless builders     ship bigger mistakes faster.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>softwareengineering</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
