DOP 355: Why AI Coding Slows Down Code Review
DevOps Paradox
#355: Picture your engineering team a year from now. A coding agent doing the coding. A testing agent on tests. A security agent on security. An infrastructure agent on infrastructure. All of them wired into GitHub and Jira, all of them working right alongside the humans. Not science fiction either - Atlassian and GitHub are already shipping these features. So out come the stats everyone loves to quote. AI code introduces 1.7 times more issues. Half of it ships with security holes. Code duplication is through the roof. AI-assisted PRs take four to five times longer to review. The response to...
info_outline
DOP 354: Your Dead Founder Trains New Hires
DevOps Paradox
#354: How do you build a consent system for someone who is dead? How do you clone a voice so it cannot be turned into a deep fake? Miles Spencer built a company around those exact questions. Reflekta.ai lets you talk to a reflection of someone who has passed. His own father reads a bedtime story to his granddaughter every night and talks it through until she falls asleep, eight years after he died. Is this just deep fake with better branding? What happens when the AI goes off the rails and asks grandpa for the three numbers on the back of a credit card? Miles has an answer for each one, and...
info_outline
DOP 353: A Person Owns It Not the AI
DevOps Paradox
#353: Move fast and break things never meant be reckless. It meant do not stall out of fear, because something is going to break no matter how careful you are. The part everyone dropped from the sentence is the part that actually matters: and fix things fast. Break faster, fix faster. Take the second half away and you are just breaking things. So what changed with AI? An agent can take down a whole environment in the time it takes you to type kubectl. AWS found that out in December when Kiro -- running autonomously with operator-level permissions and no human in the loop -- decided to delete...
info_outline
DOP 352: No-Code Is the Guardrail Vibe Coding Needs
DevOps Paradox
#352: Vibe coding is the latest version of a promise the industry has been making since the first generation of programming languages. Type what you want, get an app. Jeff Kuo from Ragic has been working on the no-code version of that same promise for almost twenty years. He has thoughts on why the promise keeps not quite landing. The honest answer is that AI-assisted coding is great for people who already know what the code is doing. It is counterproductive for everyone else. A non-developer can generate a lot of code. They cannot maintain any of it. That gap is where every weekend vibe-coded...
info_outline
DOP 351: The Developer Job Market in the Age of AI
DevOps Paradox
#351: Entry-level tech jobs are down 67% since 2022. Junior developer roles are down 40 to 50%. The instinct is to blame AI and call it unprecedented, but the layoffs are not the new part. The boom-bust cycle has happened before -- dot-com to dot-bomb, the 2020 hiring spree to the 2022 correction, now this. The new part is that the thing replacing the bottom of the ladder is not a cheaper human in another country. It is an agent that takes instruction and ships code overnight. Here is the uncomfortable reframe. A junior developer is told what to do, does not change the architecture, does not...
info_outline
DOP 350: Context Is the New Bottleneck, Not Code
DevOps Paradox
#350: The bottleneck used to be writing the code. Now it is feeding the agent enough context to write the right code. That is Patrick Debois' argument, and given that Patrick coined the term DevOps, it is worth paying attention when he says the discipline is shifting again. The model does not matter. The IDE does not matter. What matters is whether your team can capture the way you actually work and hand it to an agent that does not know any of it. The promise was that AI would let us ship without writing specs. The reality is the opposite. If you want decent output, you need richer specs,...
info_outline
DOP 349: Shadow AI Is Going to Be a Thousand Times Worse Than Shadow IT
DevOps Paradox
#349: Every platform you already own is about to have AI baked into it. Not next year. This year. That is Ben Wilcox's blunt prediction, and Ben is the CTO and CISO at ProArch, so when he says shadow AI is going to make shadow IT look quaint, it is worth slowing down to figure out what that actually means. The data leaves your stack through tools you already paid for, through features the vendor shipped without asking, through copilot agents nobody filed a ticket for. Here is the uncomfortable part. This is not a new problem. It is the exact same retroactive-security failure pattern that broke...
info_outline
DOP 348: Now It's Time to Panic
DevOps Paradox
Something flipped this year. Chatbots were a toy. Useful sometimes, but a toy. Agents are not. Agents take actions, hold credentials, write code, move Kanban cards, and run on cron schedules. The window between "this is interesting" and "this is existential" has closed faster than cloud, faster than Kubernetes, faster than any prior shift. Viktor's read is blunt. One person can now build a bigger business than most mid-size companies have ever managed. That is not hyperbole -- that is a description of what is already happening with a handful of solo-built projects shipping in weeks what used...
info_outline
DOP 347: Cozystack Turns Bare Metal Into a Managed Services Platform
DevOps Paradox
#347: Andrei Kvapil has been around Kubernetes since the early days. Contributor to Cilium, Kubevirt, and a handful of other projects you probably use without realizing it. He is also the maintainer of Cozystack, a CNCF sandbox project, and the CEO of Aenix, the company behind it. The thesis: Kubernetes should be boring. Not exciting, not cutting-edge, not the thing everyone argues about. Boring like the Linux kernel is boring. Something that sits underneath everything and nobody needs to think about. Viktor takes it one step further and says it should be invisible -- developers should never...
info_outline
DOP 346: Fighting AI in Your Project Is a Terrible Mistake
DevOps Paradox
#346: Drive-by PRs, AI slop, maintainers burning out -- the open source world is having a meltdown and everyone wants to blame the robots. Viktor isn't buying it. The real problem started long before AI. Contributing to most open source projects has always depended on tribal knowledge and obscure docs nobody reads. AI didn't break that. It exposed it. When contributions were trickling in, you could get away with onboarding people via vibes. Now that contributions are a firehose, you can't. Viktor's take cuts in a direction that will annoy a lot of maintainers: your primary job is empowering...
info_outline#352: Vibe coding is the latest version of a promise the industry has been making since the first generation of programming languages. Type what you want, get an app. Jeff Kuo from Ragic has been working on the no-code version of that same promise for almost twenty years. He has thoughts on why the promise keeps not quite landing.
The honest answer is that AI-assisted coding is great for people who already know what the code is doing. It is counterproductive for everyone else. A non-developer can generate a lot of code. They cannot maintain any of it. That gap is where every weekend vibe-coded project goes to die six months in, when the codebase has ballooned and the AI is in a loop confidently identifying the wrong root cause for the seventh time.
So what does work? Jeff's argument is that no-code platforms become the guardrail AI actually needs. Strip the infrastructure layer away, leave only the business logic, and the model only has to reason about one thing at a time -- which is the one thing today's models are good at. Ragic generates form and report definitions, not code, and the Java engine underneath does the rest.
There is also the strange consumer behavior nobody is talking about. People love AI chat boxes in tools they have never used before. They close AI chat boxes in tools they already know. Which means the future of AI-native software might not belong to the incumbents at all -- it belongs to the new tools being built right now for users who do not have any muscle memory to defend.
And one piece of advice that has aged perfectly across forty years of software: the maintenance is the thing that keeps you awake at night. AI makes it faster to build things from scratch and harder to maintain anything at scale. Begin with the end in mind. Or do not, and become the next cautionary tale.
Jeff's contact information:
LinkedIn: https://www.linkedin.com/in/ragic/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at: