The best engineers know how to read the room. This is not really an engineering problem, it’s a people problem. The engineers people trust most are the ones who know when to reassure, when to stay quiet, and how to make others feel understood.
Everyone assumes AI will replace most jobs within a year. The technology might be ready, but the economics aren’t. Data centers, power grids, and component costs don’t follow Moore’s Law. When demand outstrips infrastructure, token prices go up, and companies start doing the math on AI versus people.
AI makes ‘one more prompt’ irresistible. The next feature is always ten minutes away. The hardest engineering skill in the age of AI isn’t building. It’s deciding when to ship.
AI makes writing code so cheap that iterative enhancement stops making sense. Instead of refining small slices, teams are regenerating entire features and iterating on the whole thing. Agile isn’t dead, but its assumptions are bending hard.
After maintaining an authentication library with 125 million downloads for over a decade, here’s what I learned about the real cost of auth: it’s not the build, it’s the maintenance nobody plans for. And no, an AI agent monitoring your dependencies isn’t the answer.
AI made code cheap. The bottleneck was never the code. It was scoping, estimation, and communication, the skills teams treated as optional for years. That bet no longer pays off.
Constants feel clean until six files break when you rename a hash key. Class methods give you the same performance with an API boundary that survives refactoring.
Deep linking looks simple until it breaks in production because three teams own different pieces of it. Here’s the Phoenix server-side setup, including the content-type gotcha that will cost you an afternoon.
A Makefile trick that auto-populates the ngrok hostname into your Phoenix dev server. Small dev-environment friction compounds across a team faster than you’d expect.
The habits that made you successful in an office will hurt you when you go remote. Here’s how to replace observational communication with written communication.
