I frequently find myself in conversations about Scaled Agile Framework (SAFe) and its utility or lack thereof.
Continuous delivery can be a frustrating topic. Those of us who use this workflow will never go back to legacy ways of working.
A “deepity” is a statement that sounds profound but isn’t.
I was recently in a conversation on social media about the role of a software engineer.
I’m frequently asked what resources I’ve found most useful on my learning journey.
Continuous Delivery requires an entirely different mindset from classical artisanal delivery.
When starting on the journey to agility, the most common path is for an organization to hire a Certified Agile Consultant™ and learn about the Manifesto for Agile Software Development followed by Scrum.
Continuous delivery is a powerful tool for delivering changes safely, reliably, and more frequently with less toil and burnout.
I’ve been a developer for a while. I’ve delivered using every industry fad that management has bought into.
There are many common three-letter acronyms (TLAs) used in the software industry; TDD (Test Driven Development), BDD (Behavior Driven Development), DDD (Domain Driven Design), etc.