My first meaningful code was in Modula-2 and then C and C++ in grad school.  

All these were strongly typed languages.  

I remember naming member variables m_iPrice m for member, i for integer, etc. 

That’s when IDEs gave you no support in remembering what was what....

I'm excited to share some news with you.

I'm launching a brand new course called "Bottlenecks to Breakthroughs: Master Effective Software Delivery".

This is a fresh adventure for me, and while I'm super thrilled, I won't lie, there's a bit of butterflies-in-the-stomach feeling too. 

Let me...

I'm back for another year of "Advent of Code" challenges!

If you haven't heard of it, it's a month-long coding frenzy where people tackle a fresh two-part problem every day.

The thrill? Competing against your friends (or peers worldwide) for the speediest solution and bragging rights.

Now,...

If you're aiming for your teams to deliver value rapidly, fostering their autonomy is key.

Consider this: frequent cross-team meetings and decision-making processes can hinder swift progress.

A logical starting point involves examining fundamental constraints:

1 Team Structure: Defining clear...

Ever heard these statements in your team meetings?

“For this project, it makes sense to have a long running branch because…”
“It does not make sense to have automated tests for this code, because…”
“We need to deploy this service manually...

I upgraded some tooling yesterday, and since it affected the code writing process (very far “left”), I was ~50% faster to getting my code to be good with the new tooling.

Which leaves me wondering why I didn’t do that sooner…

Happy Friday!!!

Technical debt is often likened to a credit card : borrow now, pay back later.

The key notion is that tech debt is something you eventually pay back.

But here's the catch: it's rarely repaid. ‍

Imagine a poorly managed country endlessly borrowing until bankruptcy.

That's the true nature of...

There is a paradox in planning, where the most crucial decisions often need to be made early when you possess the least amount of information.

“Strategic Procrastination” thus can be a counterintuitive yet effective strategy.

Here's how it can work for you:

1 Preparation is Key:...

In the realm of building scalable systems and architectures, a common focus is often on increasing transactions per second. However, this narrow perspective can occasionally lead us into a corner, especially when other dimensions of scalability demand attention.

Consider this: scalability isn't...