Juan Cruz Martinez

Juan Cruz Martinez

@jcmartinez.dev

I stream, blog, and make youtube videos about tech stuff. I love coding, I love React, and I love building stuff!

53 followers75 following485 posts

The tighter you try to control things, the less control you actually have. And as a consequence, everyone will be less happy and less productive.

Ta-da! Is this because now my €200/month plan provides the same value as the €20/month was providing until yesterday? I need to make good use of them.

After every meaningful project, write a short note: • What problem did we solve? • Why did it matter? • What options did we consider? • What tradeoffs did we make? • What changed because of the work? • What should we remember next time?

That note can become: • An internal update • A promotion artifact • A blog post • A talk • A decision record • A reusable team pattern Visibility compounds when you turn work into learning.

If you can solve a problem but cannot teach the decision, the team still depends on you. Use mentoring to make your judgment inspectable. Can you explain:

• which constraints mattered? • which trade-off you accepted? • what evidence changed your mind? • where the same answer would be wrong? The learner’s questions are part of the test. Write down the one you could not answer cleanly. That gap is your next learning task.

Make you you have clear goals, seek constant feedback from others, and keep learning. Then use all that in your 1:1s with your manager, and communicate clearly where you are progressing, where you need support, and where you could improve.

Today I opened vim and I struggle to access some shortcuts. I thought it was already muzzle memory. This is the true sign that agentic coding is deteriorating my coding skills.

A move into engineering management can change what you need from technical reading. If your work has shifted from writing Rust to architecture decisions, a book on system design may serve you better than more Rust internals.

But what stroked me the most is seeing European companies, from small startups to huge enterprises and traditional slower companies embracing AI, building with AI, pushing AI forward and truly innovating.

It happens to me every single time! I set up an amazing recurring prompt, I’m amazed by how well it works. Two days later I couldn’t care any less about it, and I hate the fact that I don’t like the output and I need to correct it all the time. My love for AI is short lived!

When you ask your manager for more responsibility, name the engineering work you want to own. Agree on timing and a follow-up so you can check whether your role has actually changed.

• Explain the problem • Explain why it mattered • Share what you changed • Name the tradeoffs • Show the result • Credit the people involved • Write down what others can learn Bad visibility says: “Look at me.” Good visibility says: “Here’s what changed, why it mattered, and what we learned.”

If you're considering another internal role, start coaching a colleague through the module only you know how to maintain. Making that responsibility transferable can keep it from tying you to your current role.

The real thread to your software engineering job is not AI. It’s the engineer who knows how to use AI properly, specify requirements clearly, evaluate architectural trade-offs, and can optimize for token consumption.

If you want to be an engineer you’ll have to spend a lot of time learning real engineering first. Once you are a capable engineer, start with the AI tools. The other way around doesn’t work.

AI researchers: AI will kill us all in 10 years AI CEOs: we need 300B so we kill us all before someone else’s AI kills us all. Me: how many R’s in strawberry?

Try this: • Pick one problem your team keeps avoiding • Understand why it has not been solved yet • Talk to the people affected by it • Propose a simple path forward • Create momentum • Bring others with you • Make the result visible That’s senior engineering.

The best engineering leaders don’t optimise for faster decisions. They optimise for decision quality. Speed only matters when the decision creates meaningful progress.

Considering your first engineering management role? Look at the work you'd be learning: helping people deliver, communicating intent, handling competing priorities. If those responsibilities appeal to you, don’t let doubt take over. newsletter.thelongcommit.com/p/the-case-...

newsletter.thelongcommit.comThe Case for Becoming a ManagerI read an article recently arguing that senior engineers shouldn't become managers. Observations are mostly right. The conclusion is still wrong. I made the switch last year and here's what I learned.

When you ask a senior engineer to coach a colleague through a difficult decision, make room for it in their workload. That coaching needs time beyond the review comment that started the conversation.