A Hacker News thread posted roughly 19 hours ago — "Ask HN: What is your (AI) dev tech stack / workflow?" — is generating candid discussion about what engineering actually looks like in mid-2026. The backdrop: Anthropic has stated that 80% of its code is now AI-produced. Across the community, the pattern is consistent. Agents are writing code. Agents are opening PRs. And the review infrastructure hasn't kept pace.
For teams working in a single repo, this is a volume problem. Annoying, manageable. For teams working across microservices, it's a different challenge entirely.
A single feature in a microservice architecture might require coordinated changes across an API gateway, two internal services, a shared library, and a frontend package — each in its own repository. An agent working on that feature can generate five or six PRs in one working session. A team of engineers each supervising one or two agents can have fifty PRs open across thirty repositories simultaneously. That's not hypothetical. That's the trajectory visible in community discussions right now.
The harder problem is cross-repo review context. Those PRs are not independent. A schema change in one service creates risk in every downstream consumer. An auth library update ripples into every service that imports it. Reviewing those changes in isolation — one tab, one repo at a time — means you're looking at fragments. The cross-service picture only emerges when you can see all of them together.
This is what the HN discussion keeps circling back to: the bottleneck in an agentic team is no longer writing code. It's understanding what the code does in context. Agents have solved the generation problem. The visibility and review problem remains squarely on humans.
Engineering leaders should resist the instinct to add more reviewers or stricter gates. The real investment is in visibility infrastructure — a single surface that shows what's open across every repo, with enough signal to prioritize what needs human attention first. If your team is shipping with agents across GitHub and GitLab repos and you're starting to feel the review surface expand faster than your oversight, Code Board surfaces all of it in one place — every PR, every repo, with risk scoring so the humans in the loop can actually stay there.
