The product runs and customers use it. It’s worked well enough for years that nobody needed to know how. Now you need to change something, and nobody can say what it’ll break.

  • The person who built it left years ago
  • Documentation is a README from 2019
  • Small changes take weeks, out of caution
  • One deploy everyone is afraid of
  • An error log nobody reads anymore

How the reading goes

  1. Read it

    I get the project building and trace the flows your business actually runs on: sign-up, checkout, whatever earns the money.

  2. Write it down

    I write down what I find so it doesn't live only in my head: documentation, a map of where the risks are, and someone who can make changes with confidence again.

Where I’ve done this

I’ve built inside big established codebases, including Twitch’s, where the conventions were someone else’s and understanding came before changing anything.

If you want someone close to the code week after week after that, that’s fractional work.

Also: iOS apps · Web apps · An existing product · Fractional work · All services

Tell me what you're working on

I've got room for a few new projects. Write to me and I'll reply with how I'd approach it. I read every message myself.

hello@nerdtower.com