{"slug": "we-all-became-architects", "title": "We All Became Architects", "summary": "Zone01 Kisumu hosted an AI & Software Engineering mini-conference at Rotary, featuring a panel discussion and a keynote from Amariah Abishai, founder of Atlarix. The session's central argument was that as AI takes over code generation, developers must shift from bricklayer to architect—owning the blueprint, applying engineering judgment, and verifying AI output rather than pasting it blindly. Abishai framed the change with the line, \"Nobody sent a memo, but the job quietly changed.", "body_md": "Last week, **Zone01 Kisumu** hosted an *AI & Software Engineering* mini-conference at Rotary, featuring a panel discussion followed by a keynote from **Amariah Abishai, Founder of Atlarix**.\n\nI helped organize the session, but I left with a question that I think many developers are quietly asking:\n\n**If AI can write the code, what am I actually here to do?**\n\nThe panel explored questions many developers are facing:\n\nThere wasn't one perfect answer.\n\nBut one thing became clear: **the fundamentals still matter. The workflow is what has changed.**\n\nAmariah's keynote built on this idea with a line that stayed with me:\n\n**\"Nobody sent a memo, but the job quietly changed.\"**\n\nThe shift can be thought of as moving from **bricklayer to architect**.\n\nBefore, a lot of our value came from writing and implementing the code ourselves.\n\nNow, AI can help lay many of those bricks.\n\nOur responsibility increasingly becomes deciding:\n\nThe machine can help lay the bricks.\n\n**We still own the blueprint.**\n\nThis is especially important for junior developers.\n\nThere is a real temptation to let AI generate everything and simply move on. But if you don't understand what the code is doing, eventually you'll reach a problem you can't prompt your way out of.\n\nUsing AI shouldn't mean:\n\n**AI writes → I paste → I move on.**\n\nIt should look more like:\n\n**I think → AI assists → I understand → I verify → I improve.**\n\nThe faster AI becomes at generating code, the more important it becomes to understand the code well enough to question it.\n\nOne of my biggest takeaways from the session was simple:\n\n**AI-generated code still needs engineering judgment.**\n\nA model can produce code that looks correct, compiles successfully and still contains a serious flaw.\n\nThat's why fundamentals, testing, code reviews and understanding system architecture remain important.\n\nAI can accelerate implementation.\n\n**It doesn't remove responsibility.**\n\nThe tools are becoming increasingly accessible. Anyone can generate a prototype.\n\nSo perhaps the scarce skill isn't simply *\"Can you write code?\"*\n\nIt's:\n\n**What is worth building, how should it be built, and how do you know it's good?**\n\nMaybe that's what it means to become an architect.\n\nNobody officially gave us the title.\n\n**The tools changed, and the role changed with them.**", "url": "https://wpnews.pro/news/we-all-became-architects", "canonical_source": "https://dev.to/atieno_thedvev/we-all-became-architects-4794", "published_at": "2026-09-16 20:42:37+00:00", "updated_at": "2026-09-16 21:23:32.158430+00:00", "lang": "en", "topics": ["artificial-intelligence", "ai-tools", "developer-tools"], "entities": ["Zone01 Kisumu", "Amariah Abishai", "Atlarix", "Rotary"], "alternates": {"html": "https://wpnews.pro/news/we-all-became-architects", "markdown": "https://wpnews.pro/news/we-all-became-architects.md", "text": "https://wpnews.pro/news/we-all-became-architects.txt", "jsonld": "https://wpnews.pro/news/we-all-became-architects.jsonld"}}