My econ and consulting background changed how I write software.
I do not start from code first. I start from constraints, incentives, and outcomes.
What problem actually matters? Who benefits? What metric should move?
That thinking helps me avoid building “nice tech” that no one needs.
In practice, it makes me better at:
- prioritizing features by impact
- making tradeoffs under time pressure
- communicating decisions to technical and non-technical people
- shipping with business context, not just technical correctness
AI tools speed up execution. But framing the right problem is still human work.