# AI Is Changing Engineering Culture More Than We Realize > Source: > Published: 2026-05-22 12:30:00+00:00 “A grounded look at the technical and psychological realities of modern AI tooling.” When ChatGPT became mainstream in 2022, most developers had the same reaction: “This changes everything.” And honestly, it did. For the first time, developers could: Then the ecosystem exploded. Suddenly there was: Now every week another “AI-powered developer tool” launches. But after working with these systems continuously, I think the bigger story is no longer about model capability. It is about engineering culture. Because AI is not just changing how developers build. It is slowly changing how developers think. The first phase of developer AI tools felt balanced. Developers still: AI mostly accelerated implementation. It handled: The human was still clearly driving the system. But now the ecosystem is moving toward something very different: agentic workflows. And this changes the relationship entirely. Modern AI systems can now: That is no longer autocomplete. That is partial delegation of engineering itself. And honestly, this is where things become psychologically interesting. Because the question is no longer: “Can AI generate code?” The question is: “How much engineering participation are developers slowly giving away?” One thing many non-developers miss is that different models behave very differently in real workflows. For example: That means prompting itself has quietly become an engineering layer. Not just “asking questions.” But: A surprising amount of modern development is now: engineering the AI interaction layer. Which creates another strange shift: developers increasingly optimize communication with models instead of directly interacting with systems themselves. That is a fascinating cultural transition. One observation that keeps standing out to me: There are now hundreds of thousands of AI tools. But underneath them, only a very small number of foundational models are powering most of the ecosystem. A huge percentage of AI products still rely on infrastructure from: Which means many startups are not building intelligence itself. They are building: on top of centralized model providers. That does not make these products useless. But it changes the economics of the ecosystem. Because intelligence itself is becoming infrastructure. And infrastructure naturally centralizes. The current AI ecosystem sometimes feels less like the early internet and more like cloud computing: A lot of AI conversations online still feel disconnected from infrastructure reality. Training and serving modern models is extremely expensive. Not abstractly expensive. Physically expensive. The ecosystem depends on: Even inference itself becomes expensive at scale. Which is why: As models become larger and more capable, infrastructure pressure increases everywhere. We are already seeing: The AI ecosystem currently behaves less like traditional software and more like industrial infrastructure. That changes how sustainable rapid scaling actually is. One of the biggest changes I’ve noticed among developers is how quickly the culture around learning is changing. Earlier: Now increasingly: Again, this is not entirely bad. AI genuinely increases productivity. But there is a tradeoff emerging: speed is increasing faster than understanding. And that gap matters more than people realize. Because engineering is not only about output. It is also about: If developers stop engaging deeply with systems, engineering culture itself changes. Not immediately. Gradually. Quietly. This is one area where I think the industry still has unresolved questions. Junior developers traditionally learned through: But agentic AI systems are increasingly automating exactly those layers. Which creates a strange future possibility: The issue is not whether AI can generate code. It clearly can. The issue is: how future developers build deep intuition if participation itself keeps shrinking. Because engineering maturity usually comes from prolonged interaction with complexity. And complexity is increasingly being abstracted away. There is also an economic contradiction inside the AI boom that feels under-discussed. Most companies want: That logic makes sense individually. But collectively, there is a difficult question underneath it: If AI systems reduce large portions of knowledge work over time… Who becomes the customer? Who pays for: Technology ecosystems still depend on humans participating economically. Which makes the current “replace as much labor as possible” mindset feel unstable long-term. Especially when advanced AI access itself is becoming increasingly premium. I still think AI is one of the most useful technologies developers have received in years. It helps with: I use these systems constantly. Most developers probably do now. But I also think there is a meaningful difference between: That line matters. Because once developers stop understanding the systems underneath the output, the role slowly changes from: engineer to: operator. And maybe that is the deeper shift happening right now. Not just automation of work. But gradual outsourcing of engineering cognition itself. A lot of AI discussions focus on: But honestly, I think a quieter issue may arrive much earlier. Convenience changes behavior. And AI is becoming the most powerful convenience layer software has ever introduced. The risk may not be that machines become too intelligent. The risk may be that humans slowly stop engaging deeply with difficult thinking because instant generation becomes easier than understanding. That applies to: And maybe the long-term divide in tech will not be: developers vs AI But: developers who still understand systems deeply versus developers who only orchestrate outputs. That feels like a much more realistic future. I don’t think the solution is rejecting AI. That would be unrealistic. AI is already embedded deeply into engineering workflows. But maybe the goal should not be: removing humans from engineering completely. Maybe the goal should be: reducing friction while preserving understanding. Because engineering is not just about shipping outputs. It is about: Those things still matter. Even if generation becomes instant. And maybe that is the real question developers should keep asking themselves in this AI era: “Am I using AI to think better… or slowly replacing my participation entirely?” What's your take? Are you using the free tiers for production code, or stick to local models? Let's discuss in the comments. Disclaimer The content of this blog is based on personal experience and my thoughts and thinking. Each individual’s insights may differ based on personal analysis.