Your developer asks: "What tech stack do you want?"
You have no idea what that means. Here's what you need to know.
What's a Technology Stack?
It's the combination of programming languages, frameworks, databases, and tools used to build your software.
Think of it like choosing materials for a building. Steel, concrete, and glass make sense for a skyscraper. Wood and stone for a cabin. The "stack" should match what you're building.
Why It Matters
The stack affects:
- Development speed: Some technologies are faster to build with
- Hiring: Some technologies have more available developers
- Cost: Some technologies require expensive infrastructure
- Scalability: Some technologies handle growth better
- Longevity: Some technologies are still evolving; others are dying
Choose wrong, and you'll pay for it in slower development, higher costs, or a system that can't grow with you.
What You Don't Need to Know
You don't need to understand the technical details. That's what you're hiring developers for.
You don't need to pick specific technologies. "Use React and PostgreSQL" is not your job.
You don't need to follow hype. The newest framework isn't automatically the best choice.
What You Should Ask
1. "Why this stack for our project?"
Good developers explain their choices in business terms:
- "We chose X because it's fast to develop with, which fits your timeline"
- "We chose Y because it scales well, which matters for your growth plans"
- "We chose Z because there's a large talent pool, which helps with long-term maintenance"
Bad answer: "It's what we know" (fine for small projects, risky for large ones) Worse answer: "It's the newest and best" (hype without reasoning)
2. "How easy is it to find developers for this?"
If they pick something obscure, you'll struggle to hire later. Check job boards — are companies hiring for these skills in your area?
3. "What's the long-term outlook?"
Technologies rise and fall. Is this stack:
- Actively maintained and improved?
- Backed by a stable company or community?
- Used by major companies (which means it won't disappear)?
4. "What are the trade-offs?"
Every choice has downsides. If they can't articulate any, they either don't understand or aren't being honest.
5. "Can I switch later if needed?"
Good architecture allows swapping components. If you're locked into one vendor or technology forever, that's a risk to understand upfront.
Red Flags
🚩 They're religious about technology — "X is always better than Y" is a sign of bias, not expertise
🚩 They can't explain it simply — If you don't understand their reasoning, either they're bad at communicating or their reasoning is weak
🚩 It's cutting-edge everything — New technology is less proven, has fewer developers, and more bugs
🚩 It's ancient everything — Old technology might mean they haven't kept learning
🚩 One technology for everything — Different problems need different tools
Green Flags
✅ They ask about your context first — Timeline, budget, team, growth plans
✅ They explain trade-offs — Every choice has pros and cons
✅ They consider maintenance — Who will work on this in 3 years?
✅ They're pragmatic — Best tool for the job, not favorite tool
Common Stacks (Simplified)
Web Applications:
- Frontend: React, Vue, or Angular (all solid choices)
- Backend: Node.js, Python, Ruby, Go, or .NET (depends on requirements)
- Database: PostgreSQL or MySQL for most cases
Mobile Apps:
- Native (Swift/Kotlin): Best performance, higher cost
- Cross-platform (React Native, Flutter): Build once for iOS and Android
- The choice depends on budget and performance needs
Enterprise/Internal Tools:
- Often .NET or Java ecosystems
- More emphasis on security, integration, compliance
The Question That Matters Most
Don't ask: "Is this the best technology?"
Ask: "Is this the right technology for what we're building, who will maintain it, and how we plan to grow?"
The answer should make sense even if you don't understand the technical details.
Bottom Line
You're not choosing the technology. You're choosing people who make good technology choices. Focus on:
- Can they explain their reasoning in plain language?
- Do they consider your business context?
- Are they making pragmatic choices, not ideological ones?
If yes, trust them. If not, keep looking.
Want technology decisions that make business sense? Let's talk