Agents can write and push code in seconds, but CI still takes minutes to give them feedback. That mismatch is the biggest bottleneck in agentic engineering today, and it's why CI needed to be rebuilt from scratch.

Offload the scavenger-hunt grunt work to agents, log the useful bits (also with an agent) so the problem is discoverable next time, and spit out the day's support recap in seconds.

I used an LLM to refactor a 1500-line mess into clean, organized code. I realized months later that agents were the only ones working in it. They didn't need the clean code. They didn't need my empathy. My intuitions as an engineer just don't work anymore.

AI can help write your feature in 20 minutes. But if your CI pipeline also takes 20 minutes, you've just traded one bottleneck for another. The bottleneck in software development has shifted from writing code to integrating it, and our workflows haven't caught up.

I pegged every CPU in our ClickHouse cluster during my second week. The fix was quick, but it triggered the three fears that actually make engineering suck: looking dumb, underperforming, and wasting people's time.

Learn how support shapes the product at Depot and how we've improved our self-service support experience.

I thought I understood slow builds until I broke our docs and spent an hour fixing what should've taken 10 minutes. That's when I finally got it.

Technical writers at startups touch every part of the organization, building relationships across engineering, support, and marketing to shape how the company thinks about content from the ground up.

Git's fetch operation shows off the best of its design: simple request-response exchanges and packfiles that sync repos efficiently. Here's how it works and why modern development needs more.

AI has become incredibly powerful for engineering work, but treating it as an autopilot without providing a ton of context can lead to messy, unmaintainable code. Here's how I use AI as a copilot instead to accelerate my work while keeping control over architecture, patterns, and code quality.

Monorepos promise faster development and better visibility across your stack. But they also introduce scaling problems most teams do not see coming. This post breaks down the tradeoffs, the tooling challenges, and when a monorepo actually makes sense.

Self hosting CI runners sounds great. You get control, flexibility, and the promise of lower cost. But most teams that try it end up burned out and buried in maintenance. Between flaky APIs, surprise cloud bills, and endless patching, the tradeoffs add up fast. Here's what actually happens when you go it alone and why some teams decide not to.

Why did our CI costs spike 40% this quarter?" It's the dreaded question that makes every DevOps engineer's heart sink. This post will help you translate technical realities into financial terms, positioning yourself as a strategic partner instead of just another cost center asking for more budget.

New data shows 71% of platform engineering teams are prioritizing CI/CD optimization. Mid-sized orgs lead the charge, and for good reason, slow builds are still one of the biggest blockers to developer productivity.

Self-hosting GitHub Actions runners isn't the "set it and forget it" option that folks may think it is. In this post, we will dive into why that is the case, and what the hidden costs are.

Staff Software Engineer Iris Scholten shares what it's like onboarding to a technical product, and how to implement and measure the impact of team-level Developer Experience initiatives.

Senior Software Engineer Dan Davidson reflects on breaking the programmer mold, embracing iterative workflows and DevEx frameworks, and navigating productivity, collaboration, and efficiency.

Let's break down how optimizing your builds with Depot will ultimately lower your CI spend by half.

Platform Engineer Annabelle Thomas Taylor shares her journey from software developer to DevOps engineer, exploring the shared and distinct DevEx challenges in both roles, from reducing friction in CI/CD to fostering flow and resilience during high-stress incidents.

Staff Engineer Nic Pegg shares his journey from navigating poor DevEx to spearheading initiatives that reduce friction, foster collaboration, and empower developers to thrive — both technically and emotionally.

Our thoughts on the origins of DevEx, the current state of affairs, and where DevEx research and practice might be headed.

We're excited to announce our new Developer Experience function, led by our Head of Developer Experience, Kristen Foster-Marks.

Overmind leverages Dev Containers to manage and roll out a standard set of development tools and configurations to their engineering team. They switched to Depot to build their multi-platform Dev Container images 10x faster.

Windmill.dev switched to Depot for their native Intel & Arm Docker image builds, making them 13x faster inside of GitHub Actions.