Popular Blog Posts

Lessons from working in IT. No tools or frameworks, just the things that actually mattered for my growth and long term career progress.

A “simple” bot rule broke my indexing. Redirecting everything worked for social previews, but not for Google. I fixed it by reworking my bot handling, OG routing, SSR, and Nginx.

Standups were never really about the format. Remote work didn’t break them - it made it clear why they exist in the first place.

A reflection on what senior engineers actually do: thinking in systems, balancing trade-offs, understanding domain, and taking ownership beyond code.

A practical Agile maturity questionnaire designed to assess how independently a team operates. Includes scoring guidance and management considerations to help determine the right level of external support.

To ramp back up after ~5 years away from professional coding, I started building things in my spare time. This website was one of those projects. I also spent time on Docker, Spark, and generally getting back into a systems mindset.

“It wasn’t the change that was big. It was everything connected to it.” - A tale of why the word “Googlebot” turned into 3 days of work.

In the previous post, we introduced a questionnaire-based tool to assess Agile maturity. Once you've collected the data, what comes next? How do you use those results to make better decisions as a coach, engineering manager, or leader?

In the previous post, we explored why measuring Agile maturity is essential and how it complements Bruce Tuckman’s model of team development. Now it’s time to look at the five maturity levels in detail. Each level represents a distinct phase in a team’s evolution—from heavily supported to fully self-organizing. Understanding these stages helps Agile coaches and managers provide the right support at the right time.

After three years at Codeplay, through an Intel acquisition, shifting priorities, redundancies, workshops, coaching, and more than a few unexpected challenges, it was time for a new adventure. A look back at what I learned, the people who made it worthwhile, and why I decided to return to Technical Project Management.