Invisible engineering teams: why DevOps and platform teams get blame but no credit
rseroter · x · 2026-11-18
Anton Zaides writes on Manager.dev about the engineering "visibility spectrum."
Key points
- Every team has a default visibility level based on its work: the CEO's pet project is 10/10; DevOps/security/platform teams are nearly invisible (2/10).
- Visibility shifts over time — a quarter on a "foundational but low business impact" project drops your standing.
Symptoms of low visibility
- No credit, lots of blame: supporting every big project but forgotten at award time, always the fault line when things break.
The AI angle
- Engineers' AI work is invisible to managers — you see PRs, not the process — making it hard to coach better AI usage (more planning/verification for some, less babysitting for others).
- The post is sponsored by Weave, which claims to surface per-engineer prompt quality, one-shot success, and code quality metrics.
More from coding & agent
- GPT-6.2 Astra hands-on: upgrades million-line legacy app, all tests green in 6 hours — thesaraharminta · 2026-11-18
- Dev runs a fleet of coding agents from his iPhone at a conference via FrankenTerm — doodlestein · 2026-11-18
- Runner calling an old copy breaks the fix—absolute launchd script paths solved it — petrusenko_max · 2026-11-18
- Amazon's CompoundingKernel: 1000+ agents write GPU kernels from scratch, tops 3 SOL-ExecBench boards — dair_ai · 2026-11-18
- Using Opus-4.6 as an LLM frontend to translate other models' output into human-readable form — MilesCranmer · 2026-11-18
- Replit CEO hails Missions for bringing iOS-quality gestures to the web — amasad · 2026-11-18