Developer Experience

92% of developers use AI coding tools, but productivity has barely moved - stuck at 10%. Here’s why using AI doesn’t automatically mean getting more done.

I was at Pragmatic Summit when Chip Huyen reframed the AI conversation - if any product can be generated from a clear description, code isn’t the constraint, and true value lies elsewhere.

I was in the room at this year’s Pragmatic Summit when Laura Tacho dropped the numbers: nearly all developers use AI coding assistants, over a quarter of production code is AI-written - and yet productivity gains haven’t budged past 10%.

Building an app with AI feels easy - until real users arrive.

The following is an attempt to clarify the circumstances of a production incident that happened more than 10 years ago; it is also a lesson to all of us to decouple our production servers from boilers in distant Balkan countries.

Same reasons for quitting, same salary expectations, same frustrations. Wait a minute, where is it coming from? Let's see... Oh, no. Reddit.

Whether AI will replace human developers has become a typical headline. A recent talk at the Infobip Shift conference in Zadar took a more subtle approach: The future of software development isn’t a human-versus-machine battle but a new kind of collaboration.

Software engineers want trust, recognition, and connection.

When you ask a developer for a quick chats or to do an ad‑hoc task, it's costing teams time and money.

You don’t need 10x engineers. You need a team that ships safely, learns constantly, and doesn’t rely on heroics. Build systems that make that possible.

Ever opened code that feels like ancient hieroglyphics? You’ve likely encountered primitive obsession or premature generalization. But don’t worry - there’s a way out!

Psychologist reveals why short-term focus, AI fear, and broken team models are crushing developer productivity—and how to fix them.

The code review process should work for the team, not against it.