Coaching for tech dads who want to stop repeating their parents' errors and start writing better code for the next generation.
You wouldn't ship code without debugging it. Why ship parenting responses without doing the same?
Identify the exact moments you react instead of respond. Map the triggers. Name them precisely, the way you'd name a failing test.
Trace your reactions back to their origin. Your parents' code is still running in your head. Time to read the source.
Write new patterns. Conscious, deliberate responses that replace inherited defaults. Better architecture for the moments that matter most.
Practice in real life. With real kids. With support between sessions via Slack and email. Because parenting doesn't have a staging environment.
Justin Moore spent 20+ years as a software architect before realizing the hardest system he'd ever debug was himself as a father.
Three kids later (ages 5, 2, and a newborn), he built a coaching practice that speaks the language engineers actually think in. Not therapy. Not self-help platitudes. A framework that works because you already know how to use it.
This is coaching for any dad willing to look honestly at his patterns. Trauma optional. Curiosity required.
The patterns your parents ran don't have to be the patterns you pass down. Refactoring starts with one honest look at the stack trace.