Crafting Code Podcast

~/podcast

$ cd episodes/015-starting-over

~/podcast/episodes/015-starting-over $ ls -1a
. .. episode-summary.txt get-mp3.sh
~/podcast/episodes $ cat episode-summary.txt

Starting a new job can be a nerve-wracking experience. There's a lot to learn if you are going to be effective in your new position. Sometimes change is forced upon you, but there are reasons to voluntarily start over. It can be an important part of our personal or career journey.

Timestamps

[00:00:00] Host introductions. When starting a new job, seek to gain context. Give people the benefit of the doubt.

[00:07:16] Balance learning against your own experience - don't capsize the boat with too many changes all at once. Suppress your own ideas early on. Understanding is critical to applying patterns and Fearless Change.

[00:12:28] Why start over? Layoffs or getting fired. Career progress or a raise. Opportunity to learn and grow. People leave their boss.

[00:15:52] Burnout. Your mental state impacts your physical state. Burnout can be similar to a state of depression.

[00:19:52] Psychologically, perceived direction can be more important than the current position. It can be really exciting to be part of a big positive change.

[00:24:54] Developers tend to be more loyal to their company than the company is to them (or even deserves). ABQ = "always be quitting." Early in your career you should get experience to be exposed to many things.

[00:28:31] We need journeys of self discovery, much like in the Black Cauldron series. Learning and growth are painful. Hawthorn effect: environmental changes (might?) have a big effect.

[00:32:11] Lack of influence or impact can be a reason to start over. It is easier to have impact in a smaller business. Success usually leads to growth and therefore less impact.

[00:34:10] Summary & outro.

Books mentioned during this episode: ~/podcast $ cat copyright.txt

Copyright © 2022 - Crafting Code Podcast