Skip to content

ci-cd

17 posts

ci-cd
Slow Down to Speed Up

Rushing feels fast but creates rework, bugs, and firefighting. Why pausing for refactoring, tests, and CI upkeep is an investment in speed, not lost speed.

technical-debt · testing · ci-cd +2

Bruno API Collections in Git: A Workflow Shift, Not Free Postman

Committing Bruno .bru files to the repo keeps the API contract in the same PR and history as the code. The only real tax is a deliberate secrets boundary.

testing · ci-cd · developer-experience +1

GitHub Actions Triggers: push vs pull_request vs Merge Queue vs Release

Each git event deserves a different GitHub Actions job: what to run on push, pull_request, the merge queue, and tag/release, and why routing protects lead time.

ci-cd · github-actions · devops +1

How to Reduce Lead Time from Commit to Production

How high-performing teams shrink the lead time from code-complete to live in production, without trading away security or code quality. A guide for tech leads.

ci-cd · devops · dora-metrics +2

Shift-Left Security: Removing the Review-Queue Bottleneck

How high-performing teams keep security review from becoming a lead-time bottleneck: shift-left automation, risk-based gates, a paved road, dependency cadence.

ci-cd · devops · security +3

GitHub Environments: Manual Approval Gates for Deployments

Production deploys need a real approval gate: use GitHub Environments with native protection rules and scoped secrets, not workflow if: hacks or marketplace actions.

github-actions · ci-cd · devops +2

Set Up Claude as a PR Reviewer with the Official GitHub Action

A hardened, paste-ready setup for adding Anthropic's claude-code-action to a GitHub repo, with the security and cost knobs spelled out for production use.

claude · github-actions · code-review +3

Org-Level Reusable GitHub Actions Workflows: Architecture, Security, and Adoption

A practical guide to building an org-level shared GitHub Actions platform: architecture decisions, security governance, adoption, and 7 costly mistakes.

github-actions · ci-cd · devops +5

LaunchDarkly vs Unleash vs AWS AppConfig: Feature Flags at Scale

A production guide to feature flags in distributed systems, comparing LaunchDarkly, Unleash, and AWS AppConfig with examples for rollouts and A/B testing.

feature-flags · devops · ci-cd +5

Playwright vs Cypress: E2E Testing Strategies for Modern Web Apps

Build reliable, maintainable E2E suites with Playwright and Cypress: framework selection, flaky-test prevention, CI/CD integration, and optimization.

testing · ci-cd · automation +2

Mozilla SOPS: Encrypting Secrets in Git for GitOps

A practical guide to Mozilla SOPS for encrypting secrets in Git: age encryption, AWS CDK and Lambda patterns, and production-ready serverless security.

secrets-management · ci-cd · terraform +7

Contract Testing with Pact - Ensuring API Compatibility in Microservices

A practical guide to consumer-driven contract testing with Pact in TypeScript microservices, catching breaking API changes before deployment.

testing · microservices · api-design +3

Testing Serverless Applications: A Practical Strategy Guide

Build a testing strategy for AWS Lambda, API Gateway, DynamoDB, and Step Functions with practical patterns for fast feedback and reliability.

lambda · testing · serverless +8

GitHub Spec Kit: A Guide to Spec-Driven AI Development

How GitHub's Spec Kit turns loose AI code generation into structured, maintainable output through a four-phase specify-plan-tasks-implement loop.

ci-cd · ai-tools · code-quality +4

Building Ephemeral Preview Environments with AWS CDK and Serverless

Learn to build automated preview environments using AWS CDK, Lambda, and GitHub Actions for seamless PR testing and review workflows

aws-cdk · serverless · ci-cd +5

AI Code Review vs Human Review: What Each Catches

Where AI-assisted code review catches what humans miss, where humans still excel, and how to build effective human-AI collaboration in your review process.

code-review · ci-cd · security +7

Git Branching Strategies: Real-World Lessons for Different Teams and Products

Git branching strategies mapped to team size, product type, and release cadence. GitHub Flow is the default; here is when another model earns its overhead.

ci-cd · lessons-learned · team-management +3