The hottest Continuous Delivery Substack posts right now

And their main takeaways
Category
Top Technology Topics

Everything New Has Bugs

Fish Food for Thought • 23 implied HN points • 03 Dec 25
🕹 Technology Continuous Delivery
  1. When you speed up releases or adopt new systems, bugs and incidents will usually rise at first — it’s a natural tradeoff between velocity and stability.
  2. Give teams slack and real ownership so they can fix problems, learn, and improve quality instead of just reacting to fires.
  3. Invest in supporting systems and feedback loops like CI/CD, observability, error budgets, and postmortems so you can absorb turbulence and restore quality faster.

Think Slow, Act Fast

burkhardstubert • 99 implied HN points • 08 Sep 23
🕹 Technology Continuous Delivery
  1. Thinking slowly helps you plan better before jumping into action on projects. It's important to take the time to think through complexities and potential issues.
  2. Projects often fail when teams rush into coding without adequate planning. This can lead to messy products that are hard to maintain and costly to fix.
  3. Effective planning should involve experimentation and iteration, similar to how Pixar develops movies. This approach helps to refine ideas early and reduce risks down the line.

Episode 33: Better Built By Burkhard

burkhardstubert • 99 implied HN points • 01 Jan 23
🕹 Technology Continuous Delivery
  1. Test-Driven Development (TDD) helps developers get quick feedback while coding, improving overall project quality. This means fewer mistakes and less time spent fixing problems later.
  2. Using TDD can reduce the complexity of code by breaking down problems into smaller parts, making it easier to manage and understand.
  3. TDD encourages a culture of continuous improvement and teamwork, allowing all developers to take responsibility for the code they write. This leads to better collaboration and a more successful project.

Episode 32: Better Built By Burkhard

burkhardstubert • 79 implied HN points • 15 Dec 22
💼 Business Continuous Delivery
  1. Continuous Delivery can greatly improve software development efficiency. It reduces the time for building and testing, leading to faster and more reliable integrations.
  2. Organizations should focus on both technical and social aspects to optimize their performance. The way teams are structured influences how the software is developed, so it's key to align team setups with software architecture.
  3. Successful change in organizations is best achieved by starting with willing participants. Using principles like attraction and scarcity can help create interested teams who want to improve rather than forcing everyone to follow new practices.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

Episode 38: Better Built By Burkhard

burkhardstubert • 19 implied HN points • 16 Mar 23
🕹 Technology Continuous Delivery
  1. Continuous Delivery (CD) means making software ready for users quickly and consistently. It's important for teams to measure their progress with metrics to see how well they are doing.
  2. High-performance teams benefit from focusing on both stability and throughput to deliver great software. Balancing these two areas helps reduce bugs while keeping updates frequent.
  3. Setting clear goals for deployment and recovery times can lead to better software and happier customers. Fast response to issues helps retain customer trust and satisfaction.

Episode 36: Better Built By Burkhard

burkhardstubert • 19 implied HN points • 15 Feb 23
🕹 Technology Continuous Delivery
  1. A Continuous Delivery pipeline helps keep software always ready for release by quickly identifying problems at various stages.
  2. The workflow consists of three main stages: Commit Stage, Acceptance Stage, and System Stage, with each stage increasing confidence in the software's reliability.
  3. It's best to start building your CD pipeline now, even if it's simple, and improve it step by step as you learn.