Beyond Coding Lead Software Engineer: Why You Can Write the Code in a Day but Ship in a Month
Mar 4, 2026
Bas de Groot, tech lead focused on developer experience and platform engineering, shares sharp takes on avoiding over-engineering and treating opinions as testable hypotheses. Short, punchy conversations cover removing friction in CI/CD, when dedicated DevEx makes sense, measuring developer pain with surveys, and realistic expectations for AI in production.
AI Snips
Chapters
Transcript
Episode notes
Start DevEx When Teams Outgrow Adhoc
- Invest in DevEx once team scale makes ad-hoc interactions painful, roughly ~50 engineers upward.
- Bas notes big wins start to compound at ~200+ engineers but estimates a flip point around 50.
Measure Friction With Surveys Then Interview
- Use surveys to surface prioritized friction: ask sentiment and let engineers rank importance.
- Then follow with technical interviews to diagnose root causes where needed, leveraging DevEx technical knowledge.
Benchmark DevEx With Standard Frameworks
- Use established DX frameworks or tooling (e.g., SPACE, DX) to design surveys and benchmark against peers.
- Bas praises tools that provide percentile comparisons so you know if a score is normal or problematic.