-
Continuous Delivery Office Hours Ep.12: The platform adoption shock
-
Continuous Delivery Office Hours Ep.11: Haute culture
-
Continuous Delivery Office Hours Ep.10: Modernizing legacy software
-
Continuous Delivery Office Hours Ep.9: The compliance ratchet
-
Let's not water down the terms Continuous Integration and Continuous Delivery
-
Continuous Delivery Office Hours Ep.8: AI efficiency and effectiveness
-
Continuous Delivery Office Hours Ep.7: Modern multi-tenancy
-
Code review isn't your bottleneck, even with AI
-
Continuous Delivery Office Hours Ep.6: Change approvals
-
Continuous Delivery Office Hours Ep.5: Delivering database changes
-
Continuous Delivery Office Hours Ep.4: Mono, micro, mesco
-
Continuous Delivery Office Hours Ep.3: Branching strategies
Steve Fenton (author) - Page 1
Related posts
DRY isn't just for application code
Reusable GitHub workflows solved our copy-paste pipeline problem, but raised new questions about versioning, testing changes, and what platform teams can actually see and control.
Continuous Delivery Office Hours Ep.12: The platform adoption shock
Discover what surprised us about our Future of Platform Engineering research in terms of adoption strategies.
From features to solutions
How to take a series of small features and build a solution