Some thoughts of a senior developer/IT architect (me) about how to survive in the AI world. Somewhat lengthy read, but I really feel *this* is the way to think about it. First I want you to keep in mind the LEAP the technology has done in this year alone. Lets take a look at your options: THE PURIST: You ignore AI. 0% AI. You preserve your craft, skills. The problem: Main issue. You'll be too slow. THE VIBER: You go 100% AI. Claude Code is your temple. You no longer solve problems by hand at all. The problem: You'll lose your skills. Eventually your expertise. You'll be replaced. THE HYBRID: You see AI as a tool. You write some code by AI, some by hand. The problem: You gain very little. You have to constantly pace yourself. I've been kind of stuck in this limbo for a while and over the year I've discovered that there's a 4th option, which I think is the philosophy worth adapting. THE AUGMENTED: You may or may not have noticed but modern API (Opus 5.5) can one shot things you needed experts for previously - Access your tickets via API, auto-analyze them via AI before working on them. - Build a custom IDE for your specific problem - Automate testing/verification - build UI tests for your websites - Optimize your build and deployment pipelines - Create a mobile app of whatever tool you need (!) - Suck at linux? Manage your linux for you. But the key is not stopping here. The key is to use the time won to LEARN what else you can do and become better at your craft. If your utilities throw errors - let them be auto-caught, auto-reviewed and auto-fixed by an agent. These are your tools after all, not your core expertise. I personally have built some fascinating tools that are saving me hundreds of hours. Personally, I think this is the best way to move forward, especially in IT. Advantages: - You're being WAY more efficient - Your craft/expertise still matter - You keep learning - You are being creative - It's really fun Thoughts? Am I too far gone?