In the ever-evolving tech world, the question of whether AI will take jobs has resurfaced, this time with AI as the focal point. Historically, similar fears emerged with low-code, no-code, and offshore labor. This time, the concern is legitimate but often misdirected. Programmers' jobs aren't just about writing code; code is a byproduct. The real work involves understanding problems, translating business rules, and making critical decisions.

The author argues that AI excels at certain tasks like generating CRUDs and writing repetitive code, which scares those whose skills are limited to these areas. A significant portion of the market operates at this level, making them vulnerable to automation. However, those who understand the domain, make strategic decisions, and can explain their code are less at risk.

Those who gain strength with AI include developers who understand the business domain and architects. These professionals use AI as a force multiplier, enhancing their capabilities. AI, while good at responding to prompts, lacks the ability to understand organizational context or take responsibility for failures. This limitation means that systems still need human oversight.

The future may see fewer developers for trivial tasks but a greater demand for those who can bring clarity and architecture. The real question isn't whether AI will take jobs, but whether one can explain the purpose of their code. Preparing for this future involves focusing on fundamentals and using AI as an assistant rather than a replacement.