Popular Blog Posts

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 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.

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

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

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 our first two posts, we explored why measuring Agile maturity matters and walked through the five maturity levels teams progress through—from Fully Supported to Self-Organized. But how do you actually measure where a team stands?

For the past three years, I've had the privilege (and occasional headache) of working at Codeplay as an Agile Coach. It’s been a wild, challenging, and incredibly rewarding journey — full of ups, downs, and the occasional "wh...