Water-cooler conversation about web-development. We want to entertain, inspire, and motivate you -- or to put it another way, make your coding career more enjoyable.

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/4/22/16/879c80ee-0416-4723-b76f-9dffe9cd5464_uild_times_overcompensating_mentoring_and_more.mp3

On today&#39;s show, we cover a variety of topics. Ben talks about overcompensation at work; and, how we often swing way too hard in one direction as the first signs of a challenge. Carol talks about how her current task got away from her; and, how she suddenly founder herself creating a Pull Request with 84 files in it. Tim talks about the generation smoking ban going into effect in England. And Adam talks about the challenges of mentoring junior developers; and, how hard it is to have enough &#34;right sized&#34; tasks ready for them to work on.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/175-build-times-overcompensating-mentoring-and-more/" rel="nofollow">here</a>.

On today's show, we cover a variety of topics. Ben talks about overcompensation at work; and, how we often swing way too hard in one direction as the first signs of a challenge. Carol talks about how her current task got away from her; and, how she suddenly founder herself creating a Pull Request with 84 files in it. Tim talks about the generation smoking ban going into effect in England. And Adam talks about the challenges of mentoring junior developers; and, how hard it is to have enough "right sized" tasks ready for them to work on.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/175-build-times-overcompensating-mentoring-and-more/

175: Build Times, Overcompensating, Mentoring and More

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/4/16/4/669225e2-c7fe-49da-8b7f-439e912719a5_e_has_a_terrible_horrible_no_good_very_bad_day.mp3

On today&#39;s show, we talk about incidents and outages at work. Incidents are a fact of life. If you depend on a file system or a database or a third party vendor, at some point, something will break and your service will be degraded. Customers freak out (rightly so); and, it becomes a cross-team effort to try and find the problem, fix it, and effectively communicate updates back to your customers. There&#39;s no right way to do this. But, one could argue that there are definitely wrong ways to do this.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/174-when-your-software-has-a-terrible-horrible-no-good-very-bad-day/" rel="nofollow">here</a>.

On today's show, we talk about incidents and outages at work. Incidents are a fact of life. If you depend on a file system or a database or a third party vendor, at some point, something will break and your service will be degraded. Customers freak out (rightly so); and, it becomes a cross-team effort to try and find the problem, fix it, and effectively communicate updates back to your customers. There's no right way to do this. But, one could argue that there are definitely wrong ways to do this.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/174-when-your-software-has-a-terrible-horrible-no-good-very-bad-day/

174: When Your Software Has a Terrible, Horrible, No Good, Very Bad Day

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/4/10/3/65db08fa-bc32-4e9f-b5b8-745f4b4737e7_for_solutions_payments_and_compliance_auditing.mp3

Adam picks Tim&#39;s brain searching for the perfect solution for payments and compliance auditing.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/173-shopping-for-solutions-payments-and-compliance-auditing/" rel="nofollow">here</a>.

Adam picks Tim's brain searching for the perfect solution for payments and compliance auditing.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/173-shopping-for-solutions-payments-and-compliance-auditing/

173: Shopping for Solutions - Payments and Compliance Auditing

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/4/1/9/539d43e0-48cc-4fe7-8f4e-530040b19c54_ode_-_172_-_building_your_own_standard_library.mp3

In a world where many programmers instinctively reach for an existing solution in &#34;user land&#34;, Ben poses the question: is there value in building out and maintaining your own standard library? This would be the collection of commonly-used functions and classes that you enjoy using; and, which are tailored to your use-cases and programming paradigms. Doing so would be a vibrant mixture of pragmatism, vanity, ego, efficiency, and compensation. But, would it ultimately be a net befit?Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/172-building-your-own-standard-library/" rel="nofollow">here</a>.

In a world where many programmers instinctively reach for an existing solution in "user land", Ben poses the question: is there value in building out and maintaining your own standard library? This would be the collection of commonly-used functions and classes that you enjoy using; and, which are tailored to your use-cases and programming paradigms. Doing so would be a vibrant mixture of pragmatism, vanity, ego, efficiency, and compensation. But, would it ultimately be a net befit?

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/172-building-your-own-standard-library/

172: Building Your Own Standard Library

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/3/25/10/596da75b-a37a-4bbc-a9f5-751634b27fd8_working_code_-_171_-_from_tactics_to_strategy.mp3

Tim just completed his quarterly strategy review meeting at work. As such, he&#39;s in the perfect head space to teach Adam and Ben what strategy is; how strategy differs from tactics; and, how OKRs (Objectives and Key Results) can be used in order to ensure that the work to be done actually rolls-up to one of the company&#39;s core strategies. In the end, Ben still has no idea what&#39;s going on (as per usual); but, Adam is down to clown.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/171-from-tactics-to-strategy/" rel="nofollow">here</a>.

Tim just completed his quarterly strategy review meeting at work. As such, he's in the perfect head space to teach Adam and Ben what strategy is; how strategy differs from tactics; and, how OKRs (Objectives and Key Results) can be used in order to ensure that the work to be done actually rolls-up to one of the company's core strategies. In the end, Ben still has no idea what's going on (as per usual); but, Adam is down to clown.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/171-from-tactics-to-strategy/

171: From Tactics to Strategy

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/3/19/21/855d6049-6645-467d-a0ce-019364eedd05_ng_code_-_170_-_thinking_in_ux_with_thelma_van.mp3

On today&#39;s show, we talk to <a href="https://www.linkedin.com/in/thelmavan/" rel="nofollow">Thelma Van</a> about integrating design into the product development workflow. This includes User Experience (UX) design, User Interface (UI) design, scope negotiation, and user validation through interviews. It turns out, even if you can only <a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/" rel="nofollow">talk to five of your customers</a>, having this amount of feedback can have a massively out-sized impact on your overall design and development trajectory.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/169-buffer-overflow-tabs-vs-spaces/" rel="nofollow">here</a>.

On today's show, we talk to Thelma Van about integrating design into the product development workflow. This includes User Experience (UX) design, User Interface (UI) design, scope negotiation, and user validation through interviews. It turns out, even if you can only talk to five of your customers, having this amount of feedback can have a massively out-sized impact on your overall design and development trajectory.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/170-thinking-in-ux-with-thelma-van/

170: Thinking in UX with Thelma Van

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/3/14/2/39444871-c96b-4938-a009-818925e164a3_ng_code_-_169_-_buffer_overflow_tabs_vs_spaces.mp3

Several years ago, Stack Overflow noticed a small but surprising <a href="https://stackoverflow.blog/2017/06/15/developers-use-spaces-make-money-use-tabs/" rel="nofollow">trend within their 2017 Developer Survey data</a>. Even when attempting to adjust for several factors, it seems that the programmers who indent their code with spaces (as opposed to with tabs) have a higher earning potential. As an example of programmers who love using tabs, the hosts of the show offer up theories about this strange finding.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/169-buffer-overflow-tabs-vs-spaces/" rel="nofollow">here</a>.

Several years ago, Stack Overflow noticed a small but surprising trend within their 2017 Developer Survey data. Even when attempting to adjust for several factors, it seems that the programmers who indent their code with spaces (as opposed to with tabs) have a higher earning potential. As an example of programmers who love using tabs, the hosts of the show offer up theories about this strange finding.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/169-buffer-overflow-tabs-vs-spaces/

169: Buffer Overflow, Tabs vs Spaces

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/3/5/15/e0e99ed6-b0e1-4228-a482-cce8b99ae0e8_working_code_-_168_-_memory_safety_mandate.mp3

On today&#39;s show, we talk about two major announcements relating to the technology world. First, the government released a report calling on programmers to start using memory safe languages (see: <a href="https://www.whitehouse.gov/oncd/briefing-room/2024/02/26/press-release-technical-report/" rel="nofollow">Future Software Should Be Memory Safe</a>). Second, Apple announced that it will halt work on Titan, its autonomous electric vehicle project. We also talk about the pros-and-cons of a Computer Science degree in relation to the web development industry.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/168-memory-safety-mandate/" rel="nofollow">here</a>.

On today's show, we talk about two major announcements relating to the technology world. First, the government released a report calling on programmers to start using memory safe languages (see: Future Software Should Be Memory Safe). Second, Apple announced that it will halt work on Titan, its autonomous electric vehicle project. We also talk about the pros-and-cons of a Computer Science degree in relation to the web development industry.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/168-memory-safety-mandate/

168: Memory Safety Mandate

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/2/27/6/8c082c75-da4f-43e7-8a98-077a0c4decec_ng_code_-_167_-_everyone_likes_their_own_brand.mp3

<blockquote>The first duty in life is to assume a pose. What the second is, no one has yet discovered. - Oscar Wilde</blockquote>You may never think about it or even be aware of it; but, you have a personal brand. A brand is not something you can opt into or out of. It simply exists. The only choice that you have is how you manage - or choose not to manage - your brand in relation to other people. On today&#39;s show, we talk about our own personal brands; how they can help us; how they sometimes hurt us; and, how the goals of brand-building can change over time.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/167-everyone-likes-their-own-brand/" rel="nofollow">here</a>.

The first duty in life is to assume a pose. What the second is, no one has yet discovered. - Oscar Wilde
You may never think about it or even be aware of it; but, you have a personal brand. A brand is not something you can opt into or out of. It simply exists. The only choice that you have is how you manage - or choose not to manage - your brand in relation to other people. On today's show, we talk about our own personal brands; how they can help us; how they sometimes hurt us; and, how the goals of brand-building can change over time.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/167-everyone-likes-their-own-brand/

167: Everyone Likes Their Own Brand

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/2/20/15/3d3ea530-cc12-4a1c-ac11-355b1f61e1ae_working_code_-_166_-_whats_onboarded_to_you.mp3

On today&#39;s show, we respond to a listener question from Kamil Maraz:<blockquote>I have started a Developer experience initiative in our company. We started with a survey, which led to many 1-on-1 meetings; and, one thing that came up a few times was onboarding. Long story short: it&#39;s not ideal. I was wondering if this topic could be an inspiration for one of the episodes. For example what is an onboarded colleague to you?; do you care about time to first commit?; what does the onboarding process in your company look like? And so on. As I say often, in our company we love our users, and our developers should get the same treatment. Often the journey starts with onboarding. Thank you for hearing me out.</blockquote>We love the fact that Kamil is taking an iterative product mindset; and, is trying to apply those same principles to the company, treating engineers as the recipients of the product experience.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/166-whats-onboarded-to-you/" rel="nofollow">here</a>.

On today's show, we respond to a listener question from Kamil Maraz:

I have started a Developer experience initiative in our company. We started with a survey, which led to many 1-on-1 meetings; and, one thing that came up a few times was onboarding. Long story short: it's not ideal. I was wondering if this topic could be an inspiration for one of the episodes. For example what is an onboarded colleague to you?; do you care about time to first commit?; what does the onboarding process in your company look like? And so on. As I say often, in our company we love our users, and our developers should get the same treatment. Often the journey starts with onboarding. Thank you for hearing me out.
We love the fact that Kamil is taking an iterative product mindset; and, is trying to apply those same principles to the company, treating engineers as the recipients of the product experience.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/166-whats-onboarded-to-you/

166: What's "Onboarded" to You?

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/2/5/12/28c2aefc-b973-443a-8ccf-832872de0626_de_-_165_-_agile_methodology_with_brian_sadler.mp3

For the most part, software engineers like the concept of Agile methodology; and, they have a sense that agile development practices are the best way of getting work done. But, that doesn&#39;t mean we know how to put these agile practices in place (especially at scale). Today, we talk to <a href="https://www.linkedin.com/in/wbsadler/" rel="nofollow">Brian Sadler</a> (<a href="https://twitter.com/brian_sadler" rel="nofollow">@brian_sadler</a>) - a seasoned software developer and Agile coach - about what Agile is, what parts of it work the best, and where teams often go wrong in their interpretation of best practices.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/165-agile-methodology-with-brian-sadler/" rel="nofollow">here</a>.

For the most part, software engineers like the concept of Agile methodology; and, they have a sense that agile development practices are the best way of getting work done. But, that doesn't mean we know how to put these agile practices in place (especially at scale). Today, we talk to Brian Sadler (@brian_sadler) - a seasoned software developer and Agile coach - about what Agile is, what parts of it work the best, and where teams often go wrong in their interpretation of best practices.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/165-agile-methodology-with-brian-sadler/

165: Agile Methodology with Brian Sadler

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/1/29/11/cafff59f-75a0-4a41-afc9-53108ed0da9f_rogramming_chrome_monoculture_and_more_potluck.mp3

On this week&#39;s show, we explore a variety of topics. Ben wants to perform a mini retrospective on his desire to support the legacy platform at work. Carol is feeling isolated as the only engineer on her team - her dog is a good listener, but isn&#39;t very helpful when it comes to brainstorming. And, Adam wants to talk about the browser landscape; and see which browser(s) everyone is currently using.Also, Ben offers up some high praise for <a href="https://www.lennyspodcast.com/" rel="nofollow">Lenny&#39;s Podcast</a> - a show in which Lenny Rachitsky interviews top Product and Marketing leaders in our industry. This show is absolutely dripping in value!Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/164-solo-programming-chrome-monoculture-and-more-potluck/" rel="nofollow">here</a>.

On this week's show, we explore a variety of topics. Ben wants to perform a mini retrospective on his desire to support the legacy platform at work. Carol is feeling isolated as the only engineer on her team - her dog is a good listener, but isn't very helpful when it comes to brainstorming. And, Adam wants to talk about the browser landscape; and see which browser(s) everyone is currently using.

Also, Ben offers up some high praise for Lenny's Podcast - a show in which Lenny Rachitsky interviews top Product and Marketing leaders in our industry. This show is absolutely dripping in value!

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/164-solo-programming-chrome-monoculture-and-more-potluck/

164: Solo Programming, Chrome Monoculture and More - Potluck

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/1/22/16/d0f94ed2-3026-452f-a135-210954bd3d06_ing_code_-_163_-_exposing_yourself_to_new_tech.mp3

In web development, we tend to hold learning as a virtuous activity that&#39;s worthy of our spare time. In fact, there can be a lot of pressure on us to always be learning; and, to some degree, those of us who don&#39;t ride the wave of cutting-edge tech are &#34;othered&#34;. But, is dabbling in new technology really moving the needle? Does learning a little of this and little of that really make for a more robust engineer? Or, is there more value to be gained from depth of understanding? And, at the end of the day, does the biggest impact on what we know actually come from switching jobs and joining new teams?Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/163-exposing-yourself-to-new-tech/" rel="nofollow">here</a>.

In web development, we tend to hold learning as a virtuous activity that's worthy of our spare time. In fact, there can be a lot of pressure on us to always be learning; and, to some degree, those of us who don't ride the wave of cutting-edge tech are "othered". But, is dabbling in new technology really moving the needle? Does learning a little of this and little of that really make for a more robust engineer? Or, is there more value to be gained from depth of understanding? And, at the end of the day, does the biggest impact on what we know actually come from switching jobs and joining new teams?

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/163-exposing-yourself-to-new-tech/

163: Exposing Yourself, to New Tech

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/1/15/22/6bd879f9-c989-4e66-af4f-b1195edd8600_working_code_-_162_-_a_question_of_time.mp3

Ben never has enough time to accomplish everything that he wants to accomplish. On its own, this isn&#39;t necessarily a &#34;bad thing&#34;. But, it can quickly lead to feelings of guilt: is he not good enough, is he not effective enough, is he letting everyone down? So much of this angst is emotional. And he knows this. But, he doesn&#39;t have the wherewithal that he needs to evolve his own perspective. The crew tries to help him out.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/162-a-question-of-time/" rel="nofollow">here</a>.

Ben never has enough time to accomplish everything that he wants to accomplish. On its own, this isn't necessarily a "bad thing". But, it can quickly lead to feelings of guilt: is he not good enough, is he not effective enough, is he letting everyone down? So much of this angst is emotional. And he knows this. But, he doesn't have the wherewithal that he needs to evolve his own perspective. The crew tries to help him out.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/162-a-question-of-time/

162: A Question of Time

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/1/9/17/6ce052ba-8fe7-48ad-a749-a01f51e487b0_working_code_-_161_-_2024_goals.mp3

As we jump into the new year, the crew talks about their new year&#39;s goals—both for the podcast and for themselves. We strongly believe in the power of &#34;learning in public&#34;. And, to that end, we&#39;ve created a Google Form in which you can <a href="https://forms.gle/dVEBchG5RVAapFjaA" rel="nofollow">submit suggestions</a> on how to improve the show: what do you like, what do you not like, what can we be doing better? No suggestion is off limits, so long as no people or animals are harmed!Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/161-2024-goals/" rel="nofollow">here</a>.

As we jump into the new year, the crew talks about their new year's goals—both for the podcast and for themselves. We strongly believe in the power of "learning in public". And, to that end, we've created a Google Form in which you can submit suggestions on how to improve the show: what do you like, what do you not like, what can we be doing better? No suggestion is off limits, so long as no people or animals are harmed!

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

Full show notes and transcript here: https://workingcode.dev/episodes/161-2024-goals/

161: 2024 Goals

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/1/2/17/0d61e1ba-a765-4f39-8050-39b0386ef2f2_e_-_160_-_design_systems_and_coding_philosophy.mp3

Happy New Year! This week, we ease into 2024 with a variety of topics. Adam is building a new design system at work using Svelte and Tailwind CSS. Ben wonders if there&#39;s any way to create an &#34;Overview Effect&#34; in the world of programming. And Tim discusses a few philosophical fallacies in a work context: planning fallacy, overconfidence effect, automation bias, and plan continuation bias (aka, the sunk cost fallacy).Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/160-design-systems-and-coding-philosophy/" rel="nofollow">here</a>.

Happy New Year! This week, we ease into 2024 with a variety of topics. Adam is building a new design system at work using Svelte and Tailwind CSS. Ben wonders if there's any way to create an "Overview Effect" in the world of programming. And Tim discusses a few philosophical fallacies in a work context: planning fallacy, overconfidence effect, automation bias, and plan continuation bias (aka, the sunk cost fallacy).

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/160-design-systems-and-coding-philosophy/

160: Design Systems and Coding Philosophy

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/12/26/21/a657ecdc-37c6-41c4-b88f-7c8431278a67_orking_code_-_159_-_no_effort_december_returns.mp3

After a stressful year, we happily ease into another round of &#34;No Effort December&#34; in which the conversations flow without concern or constraint. Carol is excited to go ice skating for the first time in her life. Tim is trying to teach his kids about financial literacy. Ben shares his limited ability to fantasize. And Adam wonders why his computer gets so sticky.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/159-no-effort-december-returns/" rel="nofollow">here</a>.

After a stressful year, we happily ease into another round of "No Effort December" in which the conversations flow without concern or constraint. Carol is excited to go ice skating for the first time in her life. Tim is trying to teach his kids about financial literacy. Ben shares his limited ability to fantasize. And Adam wonders why his computer gets so sticky.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/159-no-effort-december-returns/

159: No Effort December Returns

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/12/18/15/97722977-f41a-4dd5-8d71-7f6b017bf64f_working_code_-_158_-_the_premortem_premortem.mp3

In <a href="https://workingcode.dev/episodes/154-what-could-go-wrong-premortems-and-log-levels/" rel="nofollow">episode 154</a>, we discussed the concept of a project premortem. That discussion inspired Carol to schedule her own premortem for a new 2-year project that her company is about to undertake. Given the fact that her team&#39;s work won&#39;t be sharable for at least 18-months, she&#39;s wants to make sure that her premortem is as effective as it can be. As such, we&#39;re going to have ourselves a little premortem premortem discussion on the show.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/158-the-premortem-premortem/" rel="nofollow">here</a>.

In episode 154, we discussed the concept of a project premortem. That discussion inspired Carol to schedule her own premortem for a new 2-year project that her company is about to undertake. Given the fact that her team's work won't be sharable for at least 18-months, she's wants to make sure that her premortem is as effective as it can be. As such, we're going to have ourselves a little premortem premortem discussion on the show.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/158-the-premortem-premortem/

158: The Premortem Premortem

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/12/11/16/932a140f-0394-4934-9ede-fe12d28be314_-_dead_mans_snitch_deep_dive_with_adam_cameron.mp3

On this week&#39;s show, Adam Tuttle and friend-of-the-show, <a href="https://blog.adamcameron.me/" rel="nofollow">Adam Cameron</a>, go in depth on <a href="https://deadmanssnitch.com/" rel="nofollow">Dead Man&#39;s Snitch</a> - a software service that triggers an alarm if your application doesn&#39;t &#34;check in&#34; with high enough frequency.Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod157-dead-mans-snitch-deep-dive-with-adam-cameron.md" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/157-dead-mans-snitch-deep-dive-with-adam-cameron/" rel="nofollow">here.</a>

On this week's show, Adam Tuttle and friend-of-the-show, Adam Cameron, go in depth on Dead Man's Snitch - a software service that triggers an alarm if your application doesn't "check in" with high enough frequency.

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/157-dead-mans-snitch-deep-dive-with-adam-cameron/

157: Dead Man's Snitch Deep Dive with Adam Cameron

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/12/5/14/13a57e63-210d-46a1-9623-5bf97b7782fa_e_-_156_-_json_stackoverflow_testing_hot_takes.mp3

On today&#39;s show, we cast off the social filters and lay down some hot takes! This journey of spice serves up the separation of concerns, the future of StackOverflow, the value of comments, the necessity of testing, the role of extracurricular coding, the beauty of clean code, the meh of JSON, and the challenge of building truly great products.Some of these hot takes are clearly wrong; but, I&#39;ll never tell!Follow the show and be sure to <a href="https://workingcode.dev/discord/" rel="nofollow">join the discussion on Discord</a>! Our website is <a href="https://workingcode.dev/" rel="nofollow">workingcode.dev</a> and we&#39;re <a href="https://twitter.com/WorkingCodePod" rel="nofollow">@WorkingCodePod on Twitter</a> and <a href="https://www.instagram.com/workingcodepod/" rel="nofollow">Instagram</a>. New episodes drop weekly on Wednesday.And, if you&#39;re feeling the love, <a href="https://www.patreon.com/workingcodepod" rel="nofollow">support us on Patreon</a>.With audio editing and engineering by <a href="https://www.zcross.media/" rel="nofollow">ZCross Media</a>.Full show notes and transcript <a href="https://workingcode.dev/episodes/156-json-stackoverflow-testing-hot-takes/" rel="nofollow">here</a>.

On today's show, we cast off the social filters and lay down some hot takes! This journey of spice serves up the separation of concerns, the future of StackOverflow, the value of comments, the necessity of testing, the role of extracurricular coding, the beauty of clean code, the meh of JSON, and the challenge of building truly great products.

Some of these hot takes are clearly wrong; but, I'll never tell!

Follow the show and be sure to join the discussion on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.

And, if you're feeling the love, support us on Patreon.

With audio editing and engineering by ZCross Media.

Full show notes and transcript here: https://workingcode.dev/episodes/156-json-stackoverflow-testing-hot-takes/

156: JSON, StackOverflow, Testing - Hot Takes

Your weekly conference hallway track

Working Code is a technology podcast unlike all others. Instead of diving deep into specific technologies to learn them better, or focusing on soft-skills, this one is like hanging out together at the water cooler or in the hallway at a technical conference. Working Code celebrates the triumphs and fails of working as a developer, and aims to make your career in coding more enjoyable.