Navigating the Writing and Publishing Process

We’re super excited to have Kelsey back on the show! Our last conversation was around his incredible career journey - from working at McDonald’s after school to starting his own computer store, to hacking on python infrastructure with the core developers, to meeting Satya Nadella for an interview.

In part two of this conversation, we dive deep into Kelsey’s experiences learning in public and writing “Kubernetes: Up and Running”:

• The biggest barrier to getting started with learning in public and a step-by-step guide to overcome it

• Cautionary tale of the “JavaScript sucks” guy

• Developing the skill of crafting good analogies

• The business and economics of writing a book

• Much more

[0:01:12] Writing and learning in public.

[0:10:58] Writing "Kubernetes: Up and Running."

[0:16:05] The business and economics of writing a book.

[0:21:27] Why your first book should not exceed 100 pages.

[0:23:36] What prevented Kelsey from giving up on the book.

[0:26:15] Being intentional about building an audience and the cautionary tale of the "JavaScript sucks" guy.

[0:36:44] Authenticity does not guarantee success.

[0:39:09] Developing the skill of crafting effective analogies.

[0:47:47] Advice for engineers to leverage their technical skills outside of the nine-to-five.

• Kelsey on twitter: https://twitter.com/kelseyhightower

• Our previous conversation with Kelsey about retiring as Distinguished Engineer from Google at 42: https://softwaremisadventures.com/p/kelsey-hightower-on-retiring-as-distinguished-057

👋 Make Ronak’s day by leaving us a review and let us know who we should talk to next! hello@softwaremisadventures.com