“On paper, this sounds empowering. In practice, it means that a mid-level backend engineer is now expected to understand product strategy, review AI-generated frontend code they did not write, think about deployment infrastructure, consider security implications of code they cannot fully trace, and maintain a big-picture architectural awareness that used to be someone else’s job.

That is not empowerment. That is scope creep without a corresponding increase in compensation, authority, or time.

From my experience building and scaling teams in fintech and high-traffic platforms, I can tell you that role expansion without clear boundaries always leads to the same outcome: people try to do everything, nothing gets done with the depth it requires, and burnout follows. The engineers who survive are the ones who learn to say no, to prioritize ruthlessly, and to push back when the scope of their role quietly doubles without anyone acknowledging it.”

The same person who cannot get through a novel can watch a three-hour video essay on the decline of the Ottoman Empire. The same teenager who supposedly lacks attention span can maintain game focus for hours while parsing a complex narrative across multiple storylines, coordinating with teammates, adapting strategy in real time. That’s not inferior cognition. It’s different cognition. And the difference isn’t the screen. It’s the environment.

Here we go again… :)

Re-reading this 💎

In the age of AI, let it handle CRUD stuff meanwhile let human handle important business decisions