The "help yourself before helping others" framing is key and often gets overlooked when platform teams rush to deliver features. I've seen this play out where a team built tooling for others but used totally different CI/CD internally, which created blind spots when dev teams hit bottlenecks the platform team never experienced firsthand. One thing I'd add: picking the same language as the org makes onboarding way smoother, but it can also trap you in legacy tech debt if the org is stuck on older stacks. Ran into this when a shop was heaviy Java 8 and the platform team had to balance modern frameworks vs compatibility headaches.
Appreciate all the good work in 2025. It’s nice reading all the content. See you in 2026 and have a nice vacation!
Thanks Adler! Same for you!
The "help yourself before helping others" framing is key and often gets overlooked when platform teams rush to deliver features. I've seen this play out where a team built tooling for others but used totally different CI/CD internally, which created blind spots when dev teams hit bottlenecks the platform team never experienced firsthand. One thing I'd add: picking the same language as the org makes onboarding way smoother, but it can also trap you in legacy tech debt if the org is stuck on older stacks. Ran into this when a shop was heaviy Java 8 and the platform team had to balance modern frameworks vs compatibility headaches.
Thanks for sharing!
You are right, if the stack is legacy or old, picking up the same could be a real problem.