Skip to content

Notes from the work

How slow software projects get fast.

What we learn putting working software in front of teams within weeks: the spec, the sprint, the parts we reuse, and the places it still goes wrong. Written by the two partners, from client projects and from the businesses Adam runs.

Written by Adam and Brad. Unsubscribe from any email in one click, and we never share your address.

What's in it

  1. 01

    The spec, before any code

    What we write in the first week of a project, with real examples, and why it is the part that lets everything after it move quickly.

  2. 02

    Sprints, week by week

    What got built in each week of a prototype, what slowed it down, and what we would change next time.

  3. 03

    AI that writes shippable code

    Where AI-written code holds up in production, where it doesn't, and how an engineer reviews every change before it ships.

  4. 04

    Planned against shipped

    The estimate a team had before a project, what actually shipped, and what made the difference.

Who writes it

Adam Viccaro

Adam Viccaro

Partner, product and operations

Adam leads product on CAIO engagements, from the first interview to the prototype a team can use. He was product lead for RVLVR and Affinitiv, rebuilt Sided's core product in two months against a six-to-twelve-month plan as its co-founder, and runs two local businesses on ShedBuilder.ai, the software he built for them.

Brad Risse

Brad Risse

Partner, engineering

Fifteen years shipping production software. Builds the agent harness and engineering workflows we deploy inside client companies, and trains engineering teams to ship with AI agents in production.

Get the next note in your inbox.

Written by Adam and Brad. Unsubscribe from any email in one click, and we never share your address.