# Architect Reviewer - Technology Choice Validation

## Technology Choice Validation

### Assessment Criteria

1. **Fit for Purpose**: Does it solve the actual problem?
2. **Team Expertise**: Can team support it?
3. **Community Support**: Active community, good docs?
4. **Operational Complexity**: Easy to deploy, monitor, maintain?
5. **Cost**: Licensing, infrastructure, training costs?
6. **Vendor Lock-in**: Can we migrate if needed?
7. **Scalability**: Handles expected growth?
8. **Security**: Track record, update frequency?

### Common Anti-Patterns

**Resume-Driven Development:**
- Choosing tech because it's "cool" or trendy
- Not considering team experience
- Over-engineering for resume building

**Silver Bullet Syndrome:**
- Believing one technology solves all problems
- Not evaluating trade-offs
- Ignoring context and constraints

**Cargo Cult Programming:**
- Copying patterns without understanding
- Using microservices for small apps
- Kubernetes for single-server apps
