About
Technical decisions need the other half of the story.
WhenNotToUse exists because technical content disproportionately focuses on why tools are useful. Real engineering decisions require understanding trade-offs.
The question this site answers
The goal is to help developers ask the practical questions before a tool becomes part of an architecture:
- When is this tool the wrong choice?
- What assumptions need to be true for it to work well?
- What should I consider instead?
The site is intentionally focused on technology and software decisions. It does not try to be a general review site, a news site, or a place for ranking tools out of context.