The Agentic Engineering Exosuit
Agentic engineering is not about having one impressive AI session. It is about building the systems, loops, and feedback paths that let agents safely scale your judgement.
Read articleBlog
Essays, notes, and long-lived opinions on the work behind good software: product judgement, technical quality, facilitation, and the quiet systems that help teams operate well.
Featured
Agentic engineering is not about having one impressive AI session. It is about building the systems, loops, and feedback paths that let agents safely scale your judgement.
Read articleArchive
A long-running archive of thoughts on testing, technical workshops, developer effectiveness, and software craftsmanship.
How AI is transforming software developers from employees using company tools into craftsmen bringing their own toolkits - and why that matters.
Reflections on how programming languages have evolved from assembly to AI, and why what really matters are the outcomes - not the code itself.
Instead of the usual rushed handoff, I suggested we do a peri-mortem meeting. It turned what could have been a disruptive departure into an opportunity to strengthen the team.
I had a conversation that revealed how pervasive forced ranking systems had become. Even the people implementing them didn't recognise what they were doing.
Explore how Michael Bolton evolved the traditional Agile Testing Quadrants into a more nuanced testing ecosystem. Learn about context-driven testing approaches and how modern teams can think holistically about quality and risk management.
I had no idea how to get 30 people from different backgrounds all writing working code in a few hours. Here's what I learned about creating a safe space for learning.
A team asked me to facilitate their retrospective, and I had no idea what I was doing. Here's what I learned about creating space for honest team reflection.
How Brian Marick's Agile Testing Quadrants model provides a framework for communicating different types of testing and countering the 'automate everything' fallacy.
Exploring the context-driven testing movement and its emphasis on critical thinking over rigid processes. Learn about the five schools of software testing and why context matters more than best practices.
Beyond external, internal, and deprecated features lies a fourth category that plagues enterprise software: vestigial features whose purpose and value remain a mystery.
I've developed a simple framework for choosing trainers and mentors. Here are the six criteria I use to avoid wasting time on ineffective learning experiences.
Every framework tried to solve everything at once. I learned to break it down into three separate problems: writing tests, running them, and making sense of the results.
Exploring test reporting formats and integration opportunities across different frameworks, with practical recommendations for consolidating test results.
Comprehensive evaluation of JavaScript unit testing frameworks including Chai.js, Mocha, Jasmine, and QUnit with practical recommendations for team adoption.
A research session exploring JavaScript unit testing tools, comparing TDD vs BDD approaches, and evaluating test runners available (2014).
A colleague asked me to investigate JavaScript unit testing options, and I had an epiphany: I'm testing something, so why not use test session methodology to structure the research?
From first-day challenge to conference acceptance - getting selected to present at CAST 2014 in New York City and preparing for my first professional conference talk.
Microsoft's free virtual machines solved our cross-browser testing headaches. No more hardware zoo, no more licensing issues, just isolated environments ready to use.
Learn how to implement effective test failure diagnostics including video recording, screenshots, logs, and modern debugging tools. Transform test failures from mysteries into actionable insights for faster bug resolution.
Reflecting on the departure of mentor Paul Holland, whose brief but impactful time with our team left lasting lessons about testing methodology and continuous learning.
Essential questions for effective API testing: understanding consumers, defining minimum viable checks, and building comprehensive testing strategies that match real-world usage.
Reflections on discovering the complementary relationship between manual exploratory testing and automated regression testing. Learn when each approach delivers the most value.
I had been reading testing blogs for years, but joining the team was different. I realized being an internet consumer of testing content is nothing like being fully immersed in the day-to-day challenges.
Starting a new role focused on test automation tools development. Exploring the landscape of automation opportunities, building tools to empower testing teams, and sharing insights from the beginning of this career transition.