-
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
-
Why Octopus invests in developer experience
-
Continuous Delivery Office Hours Ep.2: Remaining deployable at all times
-
Continuous Delivery Office Hours Ep.1: Continuous Delivery should be your top priority
-
Developer Productivity in the Age of AI: Why Your Past Predicts Your Future
Steve Fenton (author) - Page 1
Related posts
Let's not water down the terms Continuous Integration and Continuous Delivery
Find out why CI/CD aren't vague buzzwords. Here's what Continuous Integration and Continuous Delivery actually mean, and the common misconceptions worth correcting
Octopus Easy Mode - Runbook Webhooks
Learn how to create runbook webhook triggers
Debunking the hotfix pipeline myth
Why it is more important to making the default pipelines as fast and as efficient as possible over hotfix pipelines.