Skip to main content

Architecture Before Code

warning

The use of Atomic Bomb here is purely metaphorical. I'm using it here as a reference to a tool or framework that emphasizes architectural design before code generation.

Most code generators create files. Atomic Bomb creates architecture. This distinction is important. Traditional generators focus on components:

Atomic Bomb focuses on system structure:

Instead of immediately generating code, Atomic Bomb first establishes architectural boundaries.

This dramatically reduces variability in AI-generated solutions.

Mini Exercise​

Choose a feature such as order tracking or invoice management.

Before thinking about code, list the architecture you would want to exist first:

  • domain
  • subdomain
  • core assets
  • UI levels

Example​

For invoice management:

  • domain: Billing
  • subdomain: Invoice Management
  • core assets: InvoiceModel, InvoiceService, InvoiceState, InvoiceApi, InvoiceEvents
  • UI levels: InvoiceRow, InvoiceFilter, InvoiceTable, InvoiceOverview, InvoiceTemplate, InvoicePage