For the last two decades, many software careers began with CRUD (Create, Read, Update, Delete) applications. A junior developer would receive a ticket to build a user form, add database persistence, create an API endpoint, add validation, and render a table view. They would then repeat this cycle
What actually happened is that the AI showed up on Monday asking where the repository lives, spent Tuesday reading the entire codebase, and by Wednesday was submitting pull requests while openly questioning architectural decisions made by senior engineers. The latest models don't just "write a function."
I spent a week running Gemma locally, comparing it against Llama, Qwen and GPT-4o, trying to answer one question: Is Google's open model strategy finally good enough for real production workloads?
I was in a founder's kitchen last month. Whiteboard behind him, coffee going cold, three months of runway left. He walked me through his architecture: Kafka streaming between six microservices, a GraphQL federation layer, a vector database for "future AI features."
I haven’t seen that kind of pure, unadulterated joy in years. I think I used to feel that way about my Java builds 14 years ago, before the cynicism of a thousand deployments set in.
That’s the thing about experience: you start taking the small wins for granted, forgetting the magic of a successful compile
Most technical posts today are not written to be useful. They are written to look useful. In the AI era that is a losing game. If your post sounds like everyone else, it will be read like everyone else, which is to say skimmed, liked, and forgotten.