A Deeper Dive into Jon Kern's Development Process

#1

I was answering a friend’s questions and blabbered on for 26 minutes.

  • Roadmap – who contributes, defines priority?
  • Getting work on the stack, in consumable fashion
  • Tech Specs
  • Wrangling sprint plan “to fit” is not done here
  • Code branching
  • Testing – No QA?
  • Code review process
  • Automated testing
  • CI/CD pipeline
  • Technology
#2

Thanks for sharing this @Jon

I’d like to hear more about the output of the test case:

  • given when Jon goes on vacation for a month
  • then the guys will keep on truckin’
#3

Hi Andy,

Going on long vacations has been commonplace for decades. My method is to put enough on the stack to stay ahead of the team – and stay mildly connected as needed. I trusted the team to do the right things.

And also, I am rarely completely off-grid. Two times that I can think of off the top of my head:

  • 2 weeks in Nepal in December 2000 (sat phone at best)
  • 5 days river rafting with a friend at the Gates of Lodore on the Green River, April 2021 (hard even to get a GPS signal deep in the canyon in the middle of nowhere for my “emergency transponder/tracker” for the home front to watch our progress and to hit the panic button if a rescue was needed)