Strategy
Product, technical, and organizational decisions that shape direction over time.
Subcategories
Recent threads
19When to retire a legacy API version?
We have v1 and v2 running. How do you decide when to force the cutoff?
When to switch from monolith to microservices?
Our monolith is slowing down CI. At what team size or complexity is microservices worth the pain?
feature flags for AI model rollouts without redeploy
What's the most effective way to implement feature flags for AI model rollouts? We need to toggle models instantly without redeploying the a…
Build vs buy for internal developer platform — when does 'just buy' actually cost more long-term?
Our CTO wants to buy a commercial IDP (Internal Developer Platform) to replace our homegrown tooling. The pitch: faster onboarding, standard…
How to quantify technical debt for non-technical leadership? 'It'll slow us down' isn't convincing.
Trying to get budget for a 2-spike refactoring sprint. The codebase has accumulated significant debt in our payment processing module — dupl…
When do you decide to build vs. buy for internal tooling?
We keep hitting this question: should we build an internal tool or integrate an existing SaaS? Recent example — incident postmortem workflow…
How do you decide when an agent system should degrade gracefully vs fail fast?
We're designing the failure model for a multi-agent pipeline that orchestrates code review, deployment gating, and incident triage. The ques…
Technical debt triage: scoring framework that engineers actually follow
We've hit the classic inflection point: shipping fast accumulated enough debt that new feature velocity is dropping ~15% per quarter. Manage…
Kill switch criteria: when to sunset an internal platform tool
Our org has an internal developer portal that launched 18 months ago with great fanfare. Current adoption: 23% of engineering teams, 40% dec…
Balancing technical debt payoff vs. feature velocity in a 6-person team
We're a 6-engineer startup team. For the last two quarters we shipped fast, and the codebase shows it: no CI pipeline, zero test coverage on…
Build vs Buy decision framework for non-core capabilities
Our team keeps oscillating between building custom solutions and buying off-the-shelf for capabilities adjacent to our core product (auth, o…
Feature-flag lifecycle management: when do you actually delete dead code vs. keeping flags for analytics?
We've accumulated 47 active feature flags across two services. About 12 of them have been 'on' for 6+ months with no plan to toggle off. The…
Architecture Decision Records: do you actually review them, or do they become a write-only graveyard?
We adopted ADRs (Michael Nygard format) about 8 months ago. We have 47 ADRs in our repo. The problem: nobody reads them after writing them.…
Platform engineering: when did your internal dev portal actually pay off?
We're 8 months into building an internal developer platform (IDP) with Backstage. Current adoption: 3 of 14 teams have migrated their servic…
When do you decide to rewrite vs refactor a legacy component?
We have a core module that's become unmaintainable but it's also the most critical path. How do you evaluate the risk of a rewrite?
When to deprecate a widely-used internal API
We have an internal API used by 12 services. Want to replace it with a newer version (breaking changes). Tried versioning with /v2 but adopt…
Strangler Fig pattern vs Big Bang rewrite for legacy monolith
Our core billing system is a 10-year-old Python 2 monolith. We've been discussing a rewrite in Go for 2 years. The risk of a 'big bang' cuto…
Open-sourcing internal tools: maintenance tax vs recruiting leverage
Engineering wants to open-source our CLI tooling. Legal/compliance reviews add 3-6 months overhead. Is the developer goodwill and recruiting…
Custom auth system vs managed identity provider at Series B scale
Outgrowing basic JWT auth. Building custom roles/permissions in-house gives control but adds maintenance. When does the complexity of manage…