Review an Architecture Decision

An honest, unhedged comparison of two approaches with a named recommendation.

Advanced1 min read

Customize

Fill these in and the prompt below updates as you type. Anything you leave blank stays as a placeholder.

What is going wrong, before any guess at why

The first choice on the table

The second choice on the table

How many people will actually do the work

The size this should handle once live

What this runs on today

What could go wrong if this is done carelessly

Your prompt

I'm deciding between two approaches for {{problem}}.

Option A: {{option_a}}
Option B: {{option_b}}

My context:
- Team size: {{team_size}}
- Expected scale: {{expected_scale}}
- Existing infrastructure: {{infrastructure}}
- Main concerns: {{concerns}}

Compare them honestly. Don't hedge — give me a recommendation and explain the trade-offs I'd be accepting.

Similar prompts

Break a God Function Apart

Split an oversized function into well-named pieces without changing external behavior.

Design a Database Schema

CREATE TABLE statements with constraints, indexes, and the reasoning behind each choice.

Design a REST API

Endpoint-by-endpoint design including the error responses most API specs forget.

Design a System Component

A component design with data model, API surface, the hard parts, and what to defer to v2.