
Sign up to save your podcasts
Or
01:50 - Jess’s Superpower: Being a Property of a Situation
Karl Popper
04:25 - The Interpretation of Luck and the Psychology of Scarcity
08:17 - Physics; Physics and Software
12:06 - Conference Speaking
15:53 - Undervaluing Code
22:13 - Defining ‘Done’ in Software Development
We don’t want to define “done.” In an ongoing system, a symmathesy, there is no “done” except death.
Instead, define “better.” Then you can know you accomplished something.
Email is like laundry. There is no such thing as "done."
My job is not to do the laundry, it is to keep the laundry moving.
Nor to answer all the email, but to keep some correspondence flowing.
25:51 - TDD, the notion that “Coding is easy!”, and Resilience to Failure
Smart Kid Syndrome
Pairing with Bunny
42:04 - Learning While Teaching Others Programming
Avdi and Jess stumble through modern web development
JessiTRONica on Twitch
Aikido
Reflections:
Jamey: Things never being “the end”.
Finite and Infinite Games (print)
Finite and Infinite Games (pdf)
Sam: There might be an ending for you, specifically, but it’s not really an ending for anyone else.
Jacob: Figuring out problems by vocalizing them.
Jessica: Check out recent works from Karl Popper.
This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode.
To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well.
Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks!
Special Guest: Jacob Stoebel.
Support Greater Than Code
4.8
4242 ratings
01:50 - Jess’s Superpower: Being a Property of a Situation
Karl Popper
04:25 - The Interpretation of Luck and the Psychology of Scarcity
08:17 - Physics; Physics and Software
12:06 - Conference Speaking
15:53 - Undervaluing Code
22:13 - Defining ‘Done’ in Software Development
We don’t want to define “done.” In an ongoing system, a symmathesy, there is no “done” except death.
Instead, define “better.” Then you can know you accomplished something.
Email is like laundry. There is no such thing as "done."
My job is not to do the laundry, it is to keep the laundry moving.
Nor to answer all the email, but to keep some correspondence flowing.
25:51 - TDD, the notion that “Coding is easy!”, and Resilience to Failure
Smart Kid Syndrome
Pairing with Bunny
42:04 - Learning While Teaching Others Programming
Avdi and Jess stumble through modern web development
JessiTRONica on Twitch
Aikido
Reflections:
Jamey: Things never being “the end”.
Finite and Infinite Games (print)
Finite and Infinite Games (pdf)
Sam: There might be an ending for you, specifically, but it’s not really an ending for anyone else.
Jacob: Figuring out problems by vocalizing them.
Jessica: Check out recent works from Karl Popper.
This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode.
To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well.
Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks!
Special Guest: Jacob Stoebel.
Support Greater Than Code