// blog

Insights on AI-powered code maintenance, platform engineering, and developer productivity.

[ PLATFORM ENGINEERING ] [ SCALING ] [ MAINTENANCE ]

How Platform Teams Scale: From 3 Engineers to 30

Platform teams hit a coordination wall around 10 engineers. This is how the ones that scale get past it.

matthew-holmes | May 15, 2026 | // 9 min read

[ PLATFORM ENGINEERING ] [ MAINTENANCE ] [ ARCHITECTURE ]

Multi-Repo Management: Why Monorepos Are Expensive and Polyrepos Are Chaos

At 100+ repos, neither monorepos nor polyrepos work without tooling. Here's why change propagation is the core problem and what platform teams need to solve it.

matthew-holmes | May 13, 2026 | // 9 min read

[ SECURITY ] [ PLATFORM ENGINEERING ] [ MAINTENANCE ]

Security Patch Coordination: Why the Technical Fix Is the Easy Part

Security patches fail because of coordination breakdowns, not technical gaps. Learn how platform teams cut CVE remediation time to 72 hours with automated patch tracking and escalation.

matthew-holmes | May 5, 2026 | // 8 min read

[ PLATFORM ENGINEERING ] [ MAINTENANCE ] [ COORDINATION ]

The Hidden Cost of Coordinating Code Changes Across 50+ Repositories

Platform teams lose 20+ hours per 80-repo rollout to coordination overhead. Learn how to manage code changes across multiple repos without the manual follow-up.

matthew-holmes | Apr 23, 2026 | // 5 min read

[ MAINTENANCE ] [ PLATFORM ENGINEERING ] [ DEPENDENCIES ]

Why Dependency Updates Are Never Just Technical Work

Managing dependency updates across 50+ repos takes 12+ hours of coordination per initiative. Learn why the code change is the easy part and the org overhead is not.

matthew-holmes | Apr 20, 2026 | // 7 min read

[ MAINTENANCE ] [ PLATFORM ENGINEERING ] [ CODE REVIEW ]

How to Speed Up PR Review Cycles: Why Opening PRs Is Only 10% of the Work

Creating a PR takes 5 minutes. Getting it merged takes 3 weeks. The bottleneck isn't code generation — it's everything that happens after the PR opens.

matthew-holmes | Apr 15, 2026 | // 5 min read

[ PLATFORM ENGINEERING ] [ SCALING ] [ MAINTENANCE ]

How Platform Teams Scale: From 3 Engineers to 30

Platform teams hit a coordination wall around 10 engineers. This is how the ones that scale get past it.

matthew-holmes | May 15, 2026 | // 9 min read

[ PLATFORM ENGINEERING ] [ MAINTENANCE ] [ ARCHITECTURE ]

Multi-Repo Management: Why Monorepos Are Expensive and Polyrepos Are Chaos

At 100+ repos, neither monorepos nor polyrepos work without tooling. Here's why change propagation is the core problem and what platform teams need to solve it.

matthew-holmes | May 13, 2026 | // 9 min read

[ SECURITY ] [ PLATFORM ENGINEERING ] [ MAINTENANCE ]

Security Patch Coordination: Why the Technical Fix Is the Easy Part

Security patches fail because of coordination breakdowns, not technical gaps. Learn how platform teams cut CVE remediation time to 72 hours with automated patch tracking and escalation.

matthew-holmes | May 5, 2026 | // 8 min read

[ PLATFORM ENGINEERING ] [ MAINTENANCE ] [ COORDINATION ]

The Hidden Cost of Coordinating Code Changes Across 50+ Repositories

Platform teams lose 20+ hours per 80-repo rollout to coordination overhead. Learn how to manage code changes across multiple repos without the manual follow-up.

matthew-holmes | Apr 23, 2026 | // 5 min read

[ MAINTENANCE ] [ PLATFORM ENGINEERING ] [ DEPENDENCIES ]

Why Dependency Updates Are Never Just Technical Work

Managing dependency updates across 50+ repos takes 12+ hours of coordination per initiative. Learn why the code change is the easy part and the org overhead is not.

matthew-holmes | Apr 20, 2026 | // 7 min read

[ MAINTENANCE ] [ PLATFORM ENGINEERING ] [ CODE REVIEW ]

How to Speed Up PR Review Cycles: Why Opening PRs Is Only 10% of the Work

Creating a PR takes 5 minutes. Getting it merged takes 3 weeks. The bottleneck isn't code generation — it's everything that happens after the PR opens.

matthew-holmes | Apr 15, 2026 | // 5 min read

[ MAINTENANCE ] [ PLATFORM ENGINEERING ] [ TECHNICAL DEBT ]

The Technical Debt You Can't See: Operational Maintenance Burden

Operational maintenance debt is not legacy code or missing tests. It compounds continuously, scales with your repository count, and quietly consumes your platform team's capacity.

matthew-holmes | Apr 10, 2026 | // 7 min read

From one engineer's late-night script to coordinated PRs across the whole org

[ MAINTENANCE ] [ ENGINEERING ] [ MIGRATIONS ]

The engineer who couldn't keep up with agent rules

One engineer was maintaining a script to track CLAUDE.md files across repos. It worked — until it didn't. Here's what changes when personal scripts meet real infrastructure.

mandy | Apr 8, 2026 | // 5 min read

Tidra launch announcement — AI-powered code maintenance at scale

[ ANNOUNCEMENT ] [ MAINTENANCE ] [ ENGINEERING ]

Introducing Tidra: AI-powered code maintenance at scale

Your engineering team has a capacity problem hiding in plain sight. Today we're launching the fix — an AI maintenance agent that automates code maintenance across your entire org.

team-tidra | Mar 31, 2026 | // 7 min read

Visualization of engineering time spent on code maintenance versus feature development

[ MAINTENANCE ] [ ENGINEERING ] [ PRODUCTIVITY ]

The hidden cost of code maintenance: why AI-driven upgrades are the next productivity frontier

While shipping got faster, maintenance didn't. Upgrades, dependency cleanups, and migrations still consume 30-50% of engineering time — and that's the paradox we need to solve.

team-tidra | Feb 27, 2026 | // 5 min read

Illustration of AI agents collaborating on software engineering tasks

[ AI ] [ TOOLING ] [ AGENTS ]

Top 5 AI agents for software engineering in 2025

A curated list of AI agents that are actually making our daily lives easier as software developers — from vibe coding to maintenance automation.

team-tidra | Feb 20, 2026 | // 3 min read

Abstract visualization of programming language evolution from assembly to AI

[ TRENDS ] [ AI ] [ HISTORY ]

Abstraction always wins: how every leap in programming tools rewired the engineering job

AI coding assistants are not introducing a new disruption — they are replaying a pattern at least seven decades old. Every major abstraction layer triggered the same cycle of resistance and eventual adoption.

team-tidra | Feb 13, 2026 | // 11 min read