I still pore over every piece of delivered work. What's changed is the size of the loop I'm reviewing: same hands on the wheel — much longer laps. This is the machinery that lets Claude work an entire feature while I'm out running trails.
Software quality thrives not on excelling in one area but on maintaining competence across multiple layers of delivery. Each layer acts as a filter, removing around two thirds of defects. Focusing solely on one element, like exhaustive testing, leads to diminishing returns. Collaborative approaches across testing, CI/CD, and requirements prevent issues effectively.
I'm going to put my most controversial opinion right out there and wave it around, because I am sick of internal development teams blindly trusting code reviews performed on pull requests. Don't get me wrong. I think there are some very clever UI's provided by most providers (GitHub, Azure DevOps, Bitbucket, etc.) but no matter … Continue reading Code Reviews Without Pull Requests
I get so frustrated when I see perfectly talented DevOps engineers building pipelines which drive big bang thinking, and calling it CI/CD. Can you all please stop? Continuous integration and continuous deployment are two very special principals which drive high quality, prevent bugs reaching production, and generally help things get delivered quicker. Automation alone does … Continue reading CI/CD
Quickly configure Azure DevOps to deploy your new application into AWS.
Navigating the huge complexity of CI/CD with Forgerock Access Manager 6.5.1.
At the time of writing this post, I am 41 years old, I've been in the business of writing software for over 20 years, and I have never ever experienced a release weekend. Until now. It's now nearly 1 pm. I've been here since 7 am. There are a dozen or so different applications which … Continue reading My First Release Weekend
Coding Daddy Dobbs 