---- My poem about sacrificing Engineering Best Practices on the Altar of AI Efficiency.

First, they made CI/CD pipelines to automate the builds and deployment - and I said nothing because I didn't want to watch the scripts run. It's only running my code anyway, and more automation is good. Less for me to do!

Then, they integrated AI into our IDE - and I said nothing because the guardrails kept it in check. It's only writing code following my instructions, and more automation is good. Less for me to do!

Then, they requested source control access so the business owners could skip all the feature planning back-and-forth and just chat with an AI agent until the feature looks how they want it - and I said nothing because they're not merging into master. I'm still in charge of reviewing code, and I have an AI agent helping me review code using some rules and invariants I've handed it, and more automation is good. Less for me to do!

Now, they are requesting an always-on AI agent reviews and merges their code into master with 0 human interaction because their PRs which contain 300K lines changed each have started to pile up over the last 3 days. And I have to just do it because boss man pays my bills. But hey, more automation is good. Less for me to do.... until everything breaks and I have 1 hour to find why the million lines of code merged this week don't work anymore.

----

The story makes it sound like I didn't push back. I did. But after being forced to ignore a full career's worth of red flags and best practices I'm now just whoring my skills out to see how deep this AI-fully-replacing-devs rabbit hole goes. Besides, when else am I going to have crazy money to just throw at a new server and set it up to replace the SDLC end-to-end with a rich man's AI? And there's still the fun technical challenge of "can I make this system secure enough that even when I automate myself out of a job I couldn't revenge hack it?"