If everyone can code now.

Then details matter more than ever.

Action comes first, motivation comes second.

It’s not the other way around.

The future always wins. It’s undefeated. So don’t fight the future, everyone. It’s happening whether you like it or not. - Chris Do - The Futur Podcast

Every generation is blamed for cheating by using tools the previous generation did not have access to.

I remember working in Photoshop and there were no layers. When there was no magnetic lasso. I remember when autocomplete was not a thing in the IDE. I remember when the IDE did not exist, you wrote in notepad. I remember when sampling in music was considered cheating. When using open source was considered unprofessional. When using Wikipedia was cheating. When using stock photos was cheating. When using Stack Overflow was cheating.

I will remember when using GenAI was considered cheating.​​​​​​​​​​​​​​​​

Today I watched the Getting Lost documentary about the awesome tv-series Lost. One interesting fact is that the writers never expected to get past the pilot. They focused on making one episode that worked. But they are experienced writers and by trade they embedded potential in the characters and left small plots that could be picked up.

Like friendly TODOs in code. Not promises to implement. Just honest markers that say “this could be something.” or ”remember to fix this later.”

Across from the office a store needed more space. They put up an addition. The thing that struck me was the speed. A month or two from bare ground to a 20x20x10 meter (my really bad estimates here) structure standing there. Walls going up. Roof getting added.

Pre-manufactured parts. They just assembled what arrived.

Everyone talks about AI replacing programmers. I think it replaces something else entirely.

The experienced developer now has prefab components. The AI tools are the pre-manufactured pieces. You can assemble something real while the meeting to discuss whether to build it is still being scheduled.

The bottleneck shifts. It’s not “can we build this” anymore. It’s not even “how long will it take to build.”

It’s whether the organization can approve and validate as fast as you can build.

You could have a working prototype before the first planning meeting ends. The code can be written faster than the documentation explaining why we need it.

But here’s the question: do we trust a structure built in a day? How long does code need to sit before we believe it won’t collapse under pressure?

The building across the street will stand for decades. It better. But it was assembled in weeks because someone else already solved the hard engineering problems.

Same pieces we’re using now. Just faster assembly.

I write because I might be a few steps ahead of someone who wants to learn something new. Someone who needs a path forward.

We all have a unique mix of skills, behaviors and experiences. This combination becomes your unfair advantage when you share it.

Share your experiences.

“I might be wrong” is a cornerstone of how I manage. It keeps me flexible and open to reconsidering when someone explains I’m off base.

I’ve been taking improv classes for a couple of months now.

The thing I love most about improvisation is the feeling of a team working together toward a goal.

When we have aligned goals and clear structure, we trust each other and we want each other to succeed.

Then it is a marvel.

The problem isn’t with AI’s capabilities.

Companies are trying to automate chaos and expecting AI to magically create order from disorder.