Let’s fix a prompt by prompting

Let’s fix a prompt by prompting

1 5
calendar_today agoschedule2 min read
— Originally published at badrkouki.medium.com

This is the story of my encounter with one of the absolute dirtiest project codebases I’ve ever seen in more than seven years of software engineering. And surprise, surprise — it was almost entirely AI-generated. (Wow, shocker, I know.)

Introduction

We’ve all heard the hype about how generative AI is going to replace developers and build MVPs in seconds. But nobody talks about the radioactive technical debt left behind when non-technical founders start spamming prompts at an IDE. What was supposed to be a functional product turned out to be a bloated monster of conflicting logic and architectural rot.

Before diving into my personal story, we need to talk about the collective delusion currently happening in the business world. We need to step inside the mind of a non-technical person discovering AI coding tools for the very first time.

Every software engineer today — from principal architects to juniors — knows the reality. We know that just because an AI can spit out code snippets doesn’t mean a complex product can be built overnight. We know that just because a Product Manager saw a flashy concept on a reel doesn’t mean it’s a working system.

But to the non-tech founder? We’re just a bunch of lazy, overpaid people.

To them, their “million-dollar idea” is just a single prompt away from reality. They genuinely believe a production-ready application should and could be shipped in a week (eight days maximum if they’re being generous).

This is the modern non-technical mindset: prompt, push, prompt, push. They expect to launch the next Facebook by midnight and wake up to a bank account flooded with cash.

What they completely fail to understand is that a real product requires architecture. It requires a scalable infrastructure, a maintainable codebase, proper analytics, robust logging, tight security, and other pillars. You cannot simply prompt away systemic architecture. Writing code is the easy part; building a sustainable system is where the actual work happens.

With that reality check out of the way, let me walk you through my journey with one of the many (soooo many) AI-generated disasters.

You can read the whole story on my medium article that I've posted today
https://badrkouki.medium.com/lets-fix-a-prompt-by-prompting-a69ee352f9a9

🔥 Join developers growing publicly
Share your knowledge, build in public, and grow your developer presence with a global community.

More Posts

I’m a Senior Dev and I’ve Forgotten How to Think Without a Prompt

Karol Modelskiverified - Mar 19

TypeScript Complexity Has Finally Reached the Point of Total Absurdity

Karol Modelskiverified - Apr 23

Why Prompt Engineering Is Just an Expensive Way to Be Incompetent

Karol Modelskiverified - May 21

I Wrote a Script to Fix Audible's Unreadable PDF Filenames

snapsynapseverified - Apr 20

Your Tech Stack Isn’t Your Ceiling. Your Story Is

Karol Modelskiverified - Apr 9
chevron_left
158 Points6 Badges
Tunisiabadrkouki.dev
2Posts
0Comments
1Connections
> Senior Mobile Dev | Flutter OSS contributor | Cyborg coder by day, open-source ghost by night

Related Jobs

View all jobs →

Commenters (This Week)

23 comments
2 comments
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!