{"slug": "a-ceo-said-ai-replaced-developers-then-an-entire-engineering-community-opened", "title": "A CEO Said AI Replaced Developers. Then an Entire Engineering Community Opened DevTools.", "summary": "A Vietnamese CEO's claim that AI replaced developers backfired when engineers found critical security flaws in the app he showcased. The app, built with Claude, exposed credentials in the frontend and had unprotected admin pages, highlighting the gap between generating code and engineering production-ready software.", "body_md": "A story about AI, software engineering, and the difference between shipping code and shipping production systems.\n\nA few days ago, a post from a Vietnamese CEO sent shockwaves through the local tech community.\n\nHis claim was bold.\n\n\"I pay around $20/month for Claude. It replaced developers for our internal software.\"\n\nHe argued that small and medium businesses no longer needed software developers, expensive SaaS subscriptions, or months of development.\n\nInstead, they could simply describe what they wanted in natural language, and AI would build it.\n\nThe post spread rapidly across social media.\n\nThousands of people agreed.\n\nSome celebrated it as the future of software development.\n\nOthers saw it as the beginning of the end for software engineers.\n\nEveryone seemed to have an opinion.\n\nThen, a few days later, something interesting happened.\n\nA handful of engineers managed to find the application behind the viral post.\n\nOut of curiosity, they did what engineers naturally do.\n\nThey opened the website.\n\nThey pressed F12.\n\nThey opened DevTools.\n\nAt first, nobody was trying to prove anyone wrong. They simply wanted to understand how it had been built.\n\nThen the first screenshot appeared.\n\n\"Wait... why is this exposed in the frontend?\"\n\nA few minutes later, another one.\n\n\"This credential shouldn't be here.\"\n\nThen another.\n\n\"Is the admin page actually protected?\"\n\nMore engineers joined in.\n\nSome inspected the JavaScript bundle.\n\nOthers monitored the network requests.\n\nSome traced the API calls.\n\nWithin hours, screenshots, code snippets, and technical analyses started spreading across engineering groups in Vietnam.\n\nOne finding became five.\n\nFive became twenty.\n\nThe conversation was no longer about whether AI could generate code.\n\nIt had evolved into a much more interesting question.\n\nWhat's the difference between software that works and software that's ready for production?\n\nTo be fair, the application looked surprisingly good.\n\nThe UI was clean.\n\nAuthentication existed.\n\nUsers could log in.\n\nData could be created and updated.\n\nIf someone had shown me only the demo video, I probably would've said:\n\n\"Wow. AI is getting incredibly good.\"\n\nAnd honestly, I still believe that.\n\nBecause what happened next wasn't evidence that AI is bad.\n\nIt was evidence that software engineering is much bigger than writing code.\n\nThe first thing experienced engineers inspect usually isn't the UI.\n\nIt's what the browser already knows.\n\nWithin minutes, several issues became obvious.\n\nSensitive configuration values were exposed directly in the frontend.\n\nCredentials that should never live inside client-side code were accessible.\n\nAdministrative functionality wasn't actually protected by authorization.\n\nIn one case, it was simply hidden from users using CSS.\n\nThe browser wasn't supposed to display it.\n\nBut nothing stopped someone from navigating there directly.\n\nSome API endpoints trusted the frontend far more than they should.\n\nSeveral security checks that normally belong on the server appeared to be missing.\n\nIn several places, the application assumed users would behave honestly.\n\nSoftware rarely gets attacked by honest users.\n\nThe most interesting part?\n\nNone of these findings required sophisticated hacking techniques.\n\nJust a browser.\n\nA few minutes.\n\nAnd DevTools.\n\nThis is where I think many discussions go wrong.\n\nPeople immediately say:\n\n\"See? AI writes terrible code.\"\n\nI don't think that's true.\n\nClaude didn't randomly decide to expose secrets.\n\nIt didn't intentionally replace authorization with CSS.\n\nIt didn't wake up one morning and think:\n\n\"Today I'm going to ignore security best practices.\"\n\nIt simply optimized for the task it was given.\n\nIf the prompt was:\n\n\"Build me an admin dashboard.\"\n\nThen it built an admin dashboard.\n\nNot a secure production system.\n\nThose are two very different requests.\n\nAI did exactly what it was asked to do.\n\nThe real problem wasn't AI.\n\nThe real problem was assuming that generating code is the same as engineering software.\n\nIt isn't.\n\nThis is something our industry has struggled to explain for years.\n\nMany people think software engineering is writing code.\n\nIt isn't.\n\nWriting code is only one small part of the job.\n\nReal engineering happens in the invisible layers.\n\nThe things users never notice.\n\nThings like:\n\nNone of these appear in a product demo.\n\nNone of these make a startup launch video look cooler.\n\nYet these are the things that determine whether software survives in production.\n\nThis is actually the exciting part.\n\nFive years ago, building an MVP required a team.\n\nToday?\n\nOne founder with AI can build something surprisingly impressive over a weekend.\n\nThat's incredible.\n\nAnd honestly, I love it.\n\nMore people can validate ideas.\n\nMore startups can experiment.\n\nMore businesses can automate repetitive work.\n\nAI has dramatically lowered the cost of creating software.\n\nThat is unquestionably a good thing.\n\nBut lowering the cost of creating software doesn't eliminate the need for engineering.\n\nIt simply changes where engineering creates value.\n\nThis is probably the biggest misconception I see online.\n\nPeople assume developers are paid to type.\n\nThey're not.\n\nWe're paid to reduce uncertainty.\n\nWe're paid to reduce risk.\n\nAnyone can generate code.\n\nExperience helps answer questions like:\n\nThese questions rarely appear in prompts.\n\nBut they appear every single day in production.\n\nIn fact, I use AI every day.\n\nThey've made me dramatically faster.\n\nAI writes boilerplate.\n\nAI explains unfamiliar code.\n\nAI generates tests.\n\nAI reviews pull requests.\n\nAI helps me prototype ideas in hours instead of days.\n\nIt's one of the best productivity tools I've ever used.\n\nBut I don't confuse acceleration with expertise.\n\nGiving a Formula 1 car to someone who just got a driver's license doesn't create a Formula 1 driver.\n\nIt creates a faster beginner.\n\nAI works the same way.\n\nIronically, this story wasn't about a CEO.\n\nIt wasn't about Claude.\n\nIt wasn't even about security vulnerabilities.\n\nIt exposed something much deeper.\n\nFor years, many people—including our own industry—mistakenly equated software engineering with writing code.\n\nAI shattered that illusion.\n\nWriting code is becoming cheaper every month.\n\nEngineering judgment isn't.\n\nIf anything, AI has made it even more valuable.\n\nBecause now anyone can generate thousands of lines of code.\n\nThe difficult part is knowing whether those thousands of lines should ever reach production.\n\nI don't think AI is replacing software engineers.\n\nI think AI is replacing the part of software engineering that we mistakenly believed was the job.\n\nTyping code.\n\nThe real work has always been:\n\nIronically, AI is making those skills more valuable than ever.\n\nBecause when anyone can generate code...\n\nThe hardest part is no longer writing software.\n\nIt's knowing whether that software deserves to be deployed.\n\nThe viral post wasn't wrong about one thing.\n\nAI has fundamentally changed software development.\n\nIt has lowered barriers.\n\nIt has empowered founders.\n\nIt has made individual developers dramatically more productive.\n\nThat's worth celebrating.\n\nBut the engineering community's response reminded us of something equally important.\n\nThere's a huge difference between **software that impresses in a demo** and **software that survives in production**.\n\nOne proves an idea.\n\nThe other earns trust.\n\nAnd trust has always been the hardest thing to engineer.\n\nPerhaps the biggest lesson from this story isn't that AI will or won't replace developers.\n\nIt's that AI has finally forced us to answer a question our industry has been avoiding for years:\n\nWhat do software engineers actually do?\n\nAnd maybe, for the first time, we now have a better answer than simply saying:\n\n\"We write code.\"\n\n**What do you think?**\n\nHas AI changed what it means to be a software engineer?\n\nOr has it simply revealed what software engineering has always been about?", "url": "https://wpnews.pro/news/a-ceo-said-ai-replaced-developers-then-an-entire-engineering-community-opened", "canonical_source": "https://dev.to/khapu2906/a-ceo-said-ai-replaced-developers-then-an-entire-engineering-community-opened-devtools-2k7l", "published_at": "2026-07-22 02:36:51+00:00", "updated_at": "2026-07-22 03:02:28.749999+00:00", "lang": "en", "topics": ["artificial-intelligence", "ai-tools", "ai-safety", "developer-tools"], "entities": ["Claude", "Vietnamese CEO"], "alternates": {"html": "https://wpnews.pro/news/a-ceo-said-ai-replaced-developers-then-an-entire-engineering-community-opened", "markdown": "https://wpnews.pro/news/a-ceo-said-ai-replaced-developers-then-an-entire-engineering-community-opened.md", "text": "https://wpnews.pro/news/a-ceo-said-ai-replaced-developers-then-an-entire-engineering-community-opened.txt", "jsonld": "https://wpnews.pro/news/a-ceo-said-ai-replaced-developers-then-an-entire-engineering-community-opened.jsonld"}}