← Feed

Posts

• Post #4193440

  Is Conway's Law just a hunch? Or is it a law? Conway didn't include a proof in 1968. However, decades later, research from the automotive/aerospace industries and the software industry tells a different story. If organisations are misaligned with the product architecture, they will have quality problems and decision latency. Part 2 of "Beyond the Shades of Conway's Law" is out now: Validation: The Research and Reality Check #ConwaysLaw #SystemsThin...

• Post #4193439

  We're having a kind of heat wave .... First time I hear my MacBook Pro M1 fan kicking in since five years, while no particular heavy computational things are going on (Teams meeting 🤷 )

• Post #4193438

  Non-Blocking Code Reviews at #AgileOnTheBeach2026 The slides are available online. Thank you all for the lovely feedback. It’s been delightful ☺️ https://thinkinglabs.io/talks/2024/02/06/non-blocking-continuous-code-reviews-a-case-study.html

• Post #1707908

  I'm starting a new series on Conway's Law 🙈 Published: Beyond the Shades of Conway's Law What started as merely note-taking in the form of "Shades of Conway's Law" evolved into a talk, with additional reading, research, and more connections. This series represents an expansion of those ideas and a reflection on the journey. This is work in progress 😅 https://thinkinglabs.io/articles/2026/04/24/beyond-the-shades-of-conways-law.html

• Post #1108989

  WTF is this UK ETA shit?!? 19 EURs, really??? You really don't want anyone to come to the UK, do you?

• Post #1108983

  An article was shared on one of my clients’ Slack about AI and testing: how about approaching testing when AI is changing the code all the time, kind of. The people are enthusiastic about the article coz it kind of confirms their not-so-performant testing strategy. I violently disagree with the article because it confirms bad habits. So, want to write an article about it, but referencing the article feels like shaming the author. How to avoid that? How should I move forward?

• Post #1108982

  Comprehension Debt in the context of AI notes from Denali Lumma via the DORA community That was a bit of my worry, that people no longer make the effort to understand and internalise. There have been more posts about that: there is an upcoming reasoning deficit. We have seen this with Stackoverflow to some extent (nothing bad about SO, great tool, it has been very helpful). Now it risks being exacerbated. https://gist.github.com/rossdm/080959eb58a5f72bcc297925b0a5be36

• Post #1103586

  Published: Don’t Let AI Invert The Testing Pyramid Lately, I encountered a specific article titled "Quality Engineering with AI". I have seen it shared with a dangerous level of enthusiasm within organisations. To the untrained eye, the article appears to validate a so-called "modern" testing strategy; to anyone who understands software economics and the mechanics of software delivery, it is plain disconcerting. https://thinkinglabs.io/articles/2026/04/12/d...

• Post #953681

  Published: What is Continuous Delivery? Over the years, I have interviewed and observed a decent number of technology organisations. Many shared that they have Continuous Delivery in place. But, only a few really practised Continuous Delivery. There is a lot of misunderstanding about what Continuous Delivery actually is and what it entails. It takes nine principles, one heuristic, three foundations, one pattern and three practices to practice truly Continuous Delivery. https://thinkinglabs.io...

• Post #612714

  Apparently, according to tech conferences, IT delivery is no longer a topic. From my humble experience, screening orgs for due diligence and through consulting activities, delivery is like the exact number one problem orgs have. But I guess, attendees do not want to be confronted with this harsh truth 🤔 🤷 Anyway, let's continue burning money on AI to fix the non-bottlenecks ... 🙄