Juan Cruz Martinez

A team can spend three years working around a bad technical decision to avoid a three-month rewrite. The rewrite has a project plan, a deadline, and an estimate. The workaround is paid off quietly: one exception, one incident, a slower change at a time. Visible costs get debated. Hidden costs become normal.

Good work does not always speak for itself. Sometimes it needs a clear explanation from the person who did it.

AI makes prototypes cheap enough to build before a disagreement is settled. That makes them useful—and easy to mistake for decisions. Define the question, evidence, shortcuts, expiry, and disposition before the demo exists.

@FrancescoCiull4 Refactor it out of this world

@jcmartinezdev you mean erase 😂

Should Microsoft rewrite Teams in Rust?

A lot of writing about software is either too tactical or too vague. One side gives you tips, tools, and hot takes. The other talks about leadership in abstractions. The Long Commit lives in the middle: practical, reflective writing for people who are deep enough in software to know that the real questions are rarely just technical. I write about AI, engineering judgment, seniority, leadership, career growth, and how software work is changing. Subscribe if you want fewer hacks and more durable thinking. newsletter.thelongcommit.com

AI can make you faster. It can also make you passive. Don’t outsource the parts that build judgment: • Understanding the problem • Thinking through tradeoffs • Reviewing carefully • Learning from mistakes • Explaining your decisions Use AI to increase leverage. Not to avoid thinking.

@thekitze Would you be willing to use a normal user, and give only your wife the admin password of the machine? Then it's totally doable.

I WILL PAY FOR YOUR HELP!!! help me find a way to lock my mac computer after 10 o clock at night with a NO WORKOROUND. IT'S IMPOSSIBLE. I AM DESPERATE. I'VE HACKED EVERY TRAP THAT I'VE SET FOR MYSELF. PLEASE

Every authentication UX decision sits on the same axis: how much of the security and reliability work do you want to own? A useful way to think about customization is through four approaches: 1. Branding and configuration 2. Page templates 3. Bring your own UI 4. API first These are not maturity levels. Each is a different tradeoff between control and ownership. Choose the lowest level that solves a real product constraint. I explain how these options map to @auth0 here: auth0.com/blog/picking-t…

AI will make coding faster. That makes engineering judgment more valuable, not less.

**Recovery is part of the engineering system.** Not because a nicer calendar fixes burnout. Because a team that never lets attention land eventually weakens the judgment the work depends on. Watch for: - mornings fractured by meetings - threads that never close - decisions reopened every week - emergencies becoming the normal process Protecting recovery means changing how the work runs: fewer open loops, real decision closure, and enough space between demands to think clearly.

Let’s gooooo!!! 🇦🇷🇦🇷🇦🇷, now back to sleep 😴

Ownership does not mean doing everything yourself. It means making sure the important thing does not get dropped. That includes: • Clarifying the goal • Finding the gaps • Pulling in the right people • Communicating progress • Managing risks • Following through • Learning from the outcome Ownership is not heroism. It’s reliability under ambiguity.

Gooooooollllllllll 🇦🇷🇦🇷🇦🇷🇦🇷

3am and ready to watch 🇦🇷🇦🇷🇦🇷, let’s goooooo

Agent autonomy should change with the task. How quickly will failure become visible? How cleanly can the work be undone? What evidence exists beyond the agent’s own summary? Who gets the escalation? If detection is slow, rollback is painful, and proof is weak, narrow the scope. More autonomy is earned by better verification, not by confidence.