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/2023/3/15/2/6a95d42f-bdc5-4b87-9f65-baa2ec36d27e_things_we_should_be_doing_but_you_know_reasons.mp3

As web developers, we&#39;re all high-functioning, motivated people. And, we certainly have a good sense of what we should be doing with our time (both personally and professionally). But, theory rarely survives contact with reality. And, on today&#39;s show, we talk about all that sweet, sweet stuff we ought to be doing and why we can&#39;t quite motivate to get any of it done! Topics including backing up computers; creating reproducible systems; reading educational books; upgrading all the things; learning analytics; and, meeting other hoomans!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>.

Read the show notes online: https://workingcode.dev/episodes/118-things-we-should-be-doing-but-you-know-reasons/

118: Things We Should Be Doing But, You Know... Reasons

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/3/7/4/67a4f7cb-5456-4e57-b8e5-1111c748c668_working_code_-_117_-_champions_of_truth.mp3

On <a href="https://workingcode.dev/episodes/114-carol-got-laid-off/" rel="nofollow">episode 114</a> of the show, in effort to balance out the somber tone of Carol&#39;s unfortunate layoff, we decided to have a little fun and play Two Truths and a Lie. On today&#39;s episode we review the listener submissions and crown the one winner who correctly selected all of our lies. And the prize goes to.... listen to 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>.

Read the show notes online: https://workingcode.dev/episodes/117-champions-of-truth/

117: Champions of Truth

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/2/28/0/229afc9e-6d5e-4f5e-83de-c80373e75d3b_te_of_developer_conferences_with_brian_rinaldi.mp3

<a href="https://www.linkedin.com/in/brianrinaldi/" rel="nofollow">Brian Rinaldi</a>, Developer Experience Engineer at LaunchDarkly and long time friend of the show, recently wrote a blog post that was picked up in the <a href="https://tldr.tech/" rel="nofollow">TL;DR newsletter</a>. His post, titled <a href="https://remotesynthesis.com/blog/developer-conferences/" rel="nofollow">The State of Developer Conferences</a>, shares a theory as to why both online and IRL (In Real Life) conferences are struggling to reach pre-pandemic attendance. Brian, who&#39;s been running conferences for 15-years, has a keen understanding of who attends events; and, why the demographics of attendees might be shifting. Conference organizers around the world are reading Brian&#39;s post and are nodding in strong agreement.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>.

Read the show notes online: https://workingcode.dev/episodes/116-the-state-of-developer-conferences-with-brian-rinaldi/

116: The State of Developer Conferences with Brian Rinaldi

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/2/20/17/9f3acaaa-32d8-4f72-a2e1-5357a1da224f_working_code_-_115_-_self-care_for_developers.mp3

After drinking close to 12 Mountain Dews in a single day, Adam started to wonder if — just maybe — he was using caffeine as a way to self-medicate. Upon discussing this with his doctor, Adam was diagnosed with ADHD (Attention-Deficit / Hyperactivity Disorder) - a condition very common in the world of programming (a fact that we inspect on the show). In light of these findings, we thought it would be nice to reflect on how we&#39;ve all changed during the pandemic; and, share the little things that we do in order to keep our wits about us.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>.

Read the show notes online: https://workingcode.dev/episodes/115-self-care-for-developers/

115: Self-Care For Developers

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/2/13/16/5f33c7d3-f366-4b8d-b437-d54c6b3b9eef_working_code_-_114_-_carol_got_laid_off.mp3

Amid the frenzy of industry lay-offs, we here at the Working Code podcast were devastated to hear that our very own Carol Weiler has been affected by a down-turning real estate market. A few weeks ago, while attending a virtual All Hands meeting, her Slack account was suddenly locked, momentarily followed by her computer. It turns out that she, along with a majority of her engineers, were part of an unexpected reduction in force (RIF). On today&#39;s show, Carol graciously and courageously joins us to talk about her experience, the ensuing emotional roller coaster, and some of the fascinating steps that she&#39;s taken to help improve her outcome.We love you Carol! You continue to inspire us - and our listeners - every week!To help lighten the mood of the episode, we close out by playing Two Truths and a Lie. If you can guess who&#39;s lying about what, Tim might just send you some free podcast merch! <a href="https://forms.gle/YLKNEPnp5wYEufCN8" rel="nofollow">Submit your guesses over on Google Forms</a>.Also, Adam finally finds <a href="https://www.microsoft.com/en-us/microsoft-365/microsoft-to-do-list-app" rel="nofollow">a ToDo list that he loves</a>; and - wait for it - it comes from Microsoft!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>.

Read the show notes online: https://workingcode.dev/episodes/114-carol-got-laid-off/

114: Carol Got Laid-Off

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/2/6/15/10ed4238-9f9e-461c-8a18-191b9b77382d_working_code_-_113_-_surviving_a_layoff.mp3

Lay-offs are trending in the technology world. And, it&#39;s not just the scrappy start-ups being hit - goliaths such as Amazon, Apple, Google, Facebook, and Microsoft have all recently announced large reductions in force (RIF). Getting laid-off can pose a serious financial burden on an individual; but, there&#39;s also the psychological burden of self-doubt: Why did this happen to me? Did I deserve this? Will I ever find another tech job? On today&#39;s show, we talk about the state of the industry, share tips on becoming more resilient in uncertain time, and talk about what do if and when the pink slip commeth.<blockquote>ASIDE: In this episode, Adam makes a few comments about what it means to take responsibility as a leader (<a href="https://mastodon.art/@threddyrex/109740877379490682" rel="nofollow">See comic by Threddy</a>). And, accidentally misspoke about a few CEOs not taking a pay-cut (which apparently they did).</blockquote>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>.

Read the show notes online: https://workingcode.dev/episodes/113-surviving-a-layoff/

113: Surviving A Layoff

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/1/30/12/90e92234-8e0f-4edc-94d9-a30f73f6498f_working_code_-_112_-_listener_questions.mp3

This week, we reach into <a href="https://workingcode.dev/ama" rel="nofollow">our bag of Listener Questions</a> and pontificate on such curiosities as: Who would we want to be and what skills would we want to learn if we could step into an alternate reality? Would Danny DeVito make an intriguing Wolverine? Which are the best programming-related movies and shows? And, we all laugh a little nervously as Tim shares just how much time he&#39;s clearly spent figuring out how to get rid of a dead body.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>.

Read the show notes online: https://workingcode.dev/episodes/112-listener-questions/

112: Listener Questions

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/1/24/3/c01460f0-5c8d-43c6-8957-976c08c65345_working_code_-_111_-_how_to_learn_stuff_good.mp3

Learning something new - whether it be a language, framework, or library - can be challenging. And, if you&#39;re already an expert in some ways, it can be both humbling and frustrating to suddenly feel like a novice in other ways. On top of that, our expectations are often distorted by time; and, we forget how long it took us to amass the understanding that we have today. This can lead to unrealistic expectations when it comes to learning something new. Not to mention that our strategies for learning might change in relation to our experience. On today&#39;s show, we share our respective approaches to learning from the ground up, including reading the manual, building applications from scratch, and everything in between.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>.

Read the show notes online: https://workingcode.dev/episodes/111-how-to-learn-stuff-good/

111: How To Learn Stuff Good

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/1/16/23/fbda4d42-e380-44a8-b385-6d4bbd9b2dd3_working_code_-_110_-_measuring_impact_at_work.mp3

Not all days are created equal. Some days, you show up and just crush it non-stop. Other days, it can feel challenging to even type good. On today&#39;s show, we look at what goes into making those good days &#34;good&#34; and those bad days &#34;bad&#34;. Getting into the zone, meetings, switching modes, interfacing with customers, responding to incidents (and other interruptions) - every little thing has the power to push the needle one way or the other.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>.

Read the show notes online: https://workingcode.dev/episodes/110-measuring-impact-at-work/

110: Measuring Impact At Work

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/1/9/20/0f108d41-d903-4d73-8b16-f54a10fcde10_working_code_-_109_-_best_of_2022.mp3

On today&#39;s show, <a href="https://mattcavender.com/" rel="nofollow">Matt Cavender</a> — the man who turns our incoherent babbling into meaningful thought — is gonna share a selection of his favorite clips from the past year (2022). Adam, Ben, Carol, and Tim are taking the week off to recover from our families and work off some of those food babies. But, fear not dear listeners, the team will be back next week to ring in 2023 - Working Code style. Here&#39;s hoping y&#39;all had a lovely holiday and a happy new year!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>.

Read the show notes online: https://workingcode.dev/episodes/109-best-of-2022/

109: Best of 2022

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2023/1/2/21/988bc182-2bf2-4af8-9e51-8f1ae7ec48ce_working_code_-_108_-_2022_year_in_review.mp3

Happy New Year! We did it! We survived 2022! This has been a rather hard year in many ways and a decent year in some ways. On this episode, the crew reflects on the past year in terms of fitness, technology, personal growth, and reading goals; and, celebrates some wins and laments some losses.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>.

Read the show notes online: https://workingcode.dev/episodes/108-2022-year-in-review/

108: 2022 Year In Review

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/12/27/3/e3895b5a-0925-41f5-ab65-e1f7b7bb8a8e_working_code_-_107_-_through_the_wormhole.mp3

<a href="https://www.youtube.com/watch?v=1njzgXSzA-A" rel="nofollow">Happy Festivus</a>, dear listeners! Welcome to our last show of 2022! Closing out &#34;No Effort December&#34;, we truly run the gamut this time: Ben talks about the crippling attachment he has to his own fingers (and why he won&#39;t work with wood); Adam talks about how excited he is for the v1.0 release of <a href="https://kit.svelte.dev/" rel="nofollow">Svelte Kit</a>; and, Tim reflects on the blinding speed with which people seem to be to making science and technology breakthroughs - I mean, we&#39;re talking some serious Sci-Fi-level stuff here!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>.

Read the show notes online: https://workingcode.dev/episodes/107-through-the-wormhole/

107: Through The Wormhole

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/12/19/16/c9cdc6e4-1559-4eb3-8c3d-d769b3316064_code_-_106_-_a_cascading_cataclysmic_christmas.mp3

This week, we continue to lean into &#34;No Effort December&#34;, talking about a hodgepodge of both tech and non-tech topics. Since we&#39;re heading into Christmas, we start off talking about how challenging it is to buy gifts, especially for the grown-ass adults in our lives. We also share some of our favorite Christmas movies; and, the movies which have absolutely nothing to do with Christmas, but which we love to watch in the winter anyway. We also dig into some modern CSS advances; including our fear that CSS selectors will quickly become more like Regular Expressions: fun to write but impossible to read!Links discussed in this episode:<ul><li><a href="https://dev.to/lissy93/super-useful-css-resources-1ba3" rel="nofollow">Super Useful CSS Resources</a></li></ul>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>.

Read the show notes online: https://workingcode.dev/episodes/106-a-cascading-cataclysmic-christmas/

106: A Cascading Cataclysmic Christmas

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/12/12/22/9139793d-12c8-42d6-bdf4-39ab6790b829_working_code_-_105_-_no_effort_december.mp3

Welcome to the start of No Effort December! That&#39;s the time of the year in which we gather &#39;round the mics and talk about whatever the heck comes to mind. We just passed two years on the Working Code podcast, it&#39;s the holidays, we&#39;ve been peopling super hard with our families, and we all need a little jolly relaxation. On today&#39;s show, Carol wonders if she can use Hackathons as a means to &#34;improve community outreach&#34; - one of her team&#39;s new OKR (Objectives and Key Results). And, Ben discusses the difference between deploying on Friday vs. deploying during the holiday (and why these are not the same thing).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>.

Read the show notes online: https://workingcode.dev/episodes/105-no-effort-december/

105: No Effort December

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/12/5/13/6a080dcb-2cf7-4c86-a2fa-92b57896c20c_ing_code_-_104_-_alexa_make_a_podcast_about_ai.mp3

Tim recently read that, &#34;1 in 10 AI (Artificial Intelligence) engineers think that AI will be the downfall of our civilization.&#34; But, it&#39;s not all doom-and-gloom; he&#39;s also been reading about some exciting advances in AI and Machine Learning (ML) such as Amazon Alexa being able to come up with novel bedtime stories for kids, Cosplay stars trying out new outfits using personalized &#34;generative art&#34;, and complex software modules being created from simple prompts.It seems that AI/ML is advancing at a breakneck speed, leveraging a rich Venture Capital (VC) space driven by a &#34;move fast and break things&#34; mentality. This can be really effective at creating change; but, we&#39;re also seeing lots of AI models becoming so big and so complex that no one really understand how they work. Which is problematic when such models take on the inherently biased tendencies of their creators and moderators.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>.

Read the show notes online: https://workingcode.dev/episodes/104-alexa-make-a-podcast-about-ai/

104: Alexa Make A Podcast About AI

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/11/28/13/1e227254-f419-4b4b-b0b7-f104b5e92a7f_working_code_-_103_-_birdsite_go_boom.mp3

Back in April, Elon Musk offered to buy Twitter for $44 Billion. He then spent months talking about how terrible Twitter was before finally taking control in October. Everyone knew it was going to be a landmark moment; but, no one quite knew how things were going to play out. With mass lay-offs, a voluntary exodus of talent, threats of &#34;extreme&#34; work hours, and a series of fraudulent accounts that created a swing in the stock market, it&#39;s safe to say that it&#39;s been a poop show. It&#39;s also pulled-back the curtain, revealing Elon Musk to be more &#34;toxic boss&#34; and less &#34;technology genius&#34;.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>.

Read the show notes online: https://workingcode.dev/episodes/103-birdsite-go-boom/

103: Birdsite Go Boom

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/11/21/15/574394c9-20de-4085-97dd-f7ed87075791_g_code_-_102_-_upgrading_mysql_for_poop_emojis.mp3

Migrating data is always complicated. And, the more data that you have to migrate, the more complex your migration process becomes. This week on the show, Adam shares the lessons that he learned while performing a <a href="https://adamtuttle.codes/blog/2022/lessons-learned-migrating-large-mysql-databases/" rel="nofollow">large, multi-client, multi-cluster, week-long database migration</a> for <a href="https://www.alumniq.com/" rel="nofollow">AlumnIQ</a>. This included moving roughly a dozen different databases from Amazon Aurora (MySQL 5) to Aurora 8. Late nights, indexes, and UTF-8 character encodings, oh my!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>.

Read the show notes online: https://workingcode.dev/episodes/102-upgrading-mysql-for-poop-emojis/

102: Upgrading MySQL For Poop Emojis

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/11/14/14/27e9097c-656d-4425-972d-169e52607fb0_g_code_-_101_-_error_error_message_not_helpful.mp3

Web application developers are notoriously bad about building resilient applications. All too often, we implement the &#34;happy path&#34; and then forget (or simply ignore) that many things can go wrong for any number of reasons. However, even if we do account for the &#34;sad path&#34;, and we do catch and handle errors, it&#39;s not always clear how those errors should be presented to the user. Luckily, Tim has some very practical guidance on the matter that he shares with us on this week&#39;s show:<blockquote>Error messages sent to the end user need to have an appropriate tone, be free of tech jargon and shouldn&#39;t pass the blame. They say what happened and why, provide reassurance, be empathetic, tell them how to fix it (if possible) and give them a course for remediation (customer service, support ticket).</blockquote>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>.

Read the show notes online: https://workingcode.dev/episodes/101-error-error-message-not-helpful/

101: Error - Error Message Not Helpful!

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/11/7/23/147d6aa0-656e-47f9-a9aa-01a7c8179254_working_code_-_100_-_the_spicetacular.mp3

View the video version on YouTube: https://www.youtube.com/watch?v=ykhX08w4yRIIt&#39;s hard to believe that we made it to episode 100! When we, four, started out on this journey almost two years ago, we were convinced that we&#39;d either get sick of each other or quickly run out of topics to discuss. But, here we are, still loving it and having a great time. And, to celebrate this milestone in the most masochistic way possible, we&#39;ve decided to ignite our guts and destroy our butts with a <a href="https://www.youtube.com/c/FirstWeFeast" rel="nofollow">Hot Ones</a>-inspired Spicetacular! Come for the AMA (Ask Me Anything) and stay for the <a href="https://www.merriam-webster.com/dictionary/schadenfreude" rel="nofollow">schadenfreude</a>!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>.

Read the show notes online:  https://workingcode.dev/episodes/100-the-spicetacular/

100: The Spicetacular!

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/11/1/0/ed731d03-635b-4f46-86ec-f77b2a575b5f_-_technical_debt_isnt_always_a_choice_or_is_it.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week, we&#39;re super excited to be getting the band back together! After several weeks of personal and professional obligations, Adam, Ben, Carol, and Tim are all back at it again. And today, we&#39;re talking about Technical debt. When engineers talk about technical debt in public, they often try to use financial metaphors; such as taking out a loan in order to buy a house.These financial metaphors romanticize the notion of technical debt, elevating it into the realm of calculated decision making. But, if we&#39;re being honest without ourselves, is any kind of calculation really taking place? Or, are we just trying to do the best that we can with the knowledge and experience that we have? In other words, isn&#39;t most technical debt really just the result of engineers writing janky code at the limit of our capabilities?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>.

Read the show notes online: https://workingcode.dev/episodes/099-technical-debt-isnt-always-a-choice-or-is-it/

099: Technical Debt Isn’t Always A Choice. Or Is It?

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/10/24/12/89bb5de7-9571-444d-9665-8eb10cb8cd89_-_in_defense_of_working_on_the_legacy_platform.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>If you&#39;ve listened to the Working Code podcast for any period of time, you&#39;ve no doubt heard Ben mention the fact that he works on maintaining a legacy platform at <a href="https://www.invisionapp.com/" rel="nofollow">InVision</a>. His role on the legacy team was originally focused on security, stability, and bug-related fixed. However, over the years, he&#39;s become increasingly aggressive about adding features and actively improving the legacy experience. This has caused no shortage of controversy both internally to the company, and more broadly within the <a href="https://workingcode.dev/discord/" rel="nofollow">Working Code community</a>. In this episode, Adam plays Devil&#39;s advocate and gets Ben to justify a mode over operation that seems to be - at times - in opposition to his company&#39;s larger goals.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>.

Read the show notes online: https://workingcode.dev/episodes/098-in-defense-of-working-on-the-legacy-platform/

098: In Defense Of Working On The Legacy Platform

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/10/17/12/18e49805-1f6d-47bf-b8af-0f39c38058ff_xpectations_of_professional_software_engineers.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, the crew reviews <a href="https://www.youtube.com/watch?v=cV5HArLYajE" rel="nofollow">Mike Acton&#39;s talk, &#34;Everyone Watching This Is Fired&#34;</a>, by way of <a href="https://adamj.eu/tech/2022/06/17/mike-actons-expectations-of-professional-software-engineers/" rel="nofollow">Adam Johnson&#39;s article, Expectations of Professional Software Engineers</a>. This talk outlines 50 characteristics - both technical and non-technical - that go into making you and your team fit for building products and dealing with customers. Some of these line-items makes us feel seen while others leave us feeling attacked. Listen to find out which ones are which!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>.

Read the show notes online: https://workingcode.dev/episodes/097-expectations-of-professional-software-engineers/

097: Expectations Of Professional Software Engineers

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/10/10/11/e5d8d23c-06a3-4ba3-9589-114ee8a8c3fb_working_code_-_096_-_why_do_you_write.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>A year ago, on Episode 36, we talked about <a href="https://workingcode.dev/episodes/036-blogs-and-digital-gardens/" rel="nofollow">blogs and digital gardens</a>. Today, Adam and Ben, our resident authors, dive deeper into how they got started writing, what keeps them writing today, and how the act of - and the engagement with - writing has changed over the years. The advent of Social Media, along with the doubling of new programmers every 5-years, has certainly created a contentious relationship with long-form content. And, is at times, antithetical to our hope of bringing readers along for the journey.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>.

Read the show notes online: https://workingcode.dev/episodes/096-why-do-you-write/

096: Why Do You Write?

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/10/3/14/716a6635-8cb3-4f4c-936d-614929d0fe44_e_-_095_-_potluck_6_unpopular_opinions_edition.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, we tip our hats to the <a href="https://changelog.com/gotime/" rel="nofollow">Go Time podcast</a> and have ourselves an Unpopular Opinion potluck. This means sharing ideas for which we feel strongly; but, which may not be so popular in the broader programming community. Topics include password rotation policies (which are dumb), relational databases (which are stupendous), the technical ability of an executive leadership team (which is important), the user experience (UX) of forms (which is often over-thought), automated deployments (which should be based on tags), and code duplication (which can certainly be the right approach).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>.

Read the show notes online: https://workingcode.dev/episodes/095-potluck-6-unpopular-opinions-edition/

095: Potluck #6 - Unpopular Opinions Edition

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/9/27/1/8a7a8c1f-b693-4f18-ad4c-79f51c57d516_working_code_-_094_-_disagree_and_commit.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>People don&#39;t burn out because they have too much work to do, they burn out because they feel powerless. And, for Ben, feeling powerless correlates strongly with doing work that he doesn&#39;t believe in. Which is why he&#39;s never understood the notion of, &#34;Disagree and commit&#34;. After all, in order to quell the feelings of dissent, he has to numb a fundamental part of who he is; and, he&#39;s convinced that such a technique can&#39;t be good for the overall creative process.To quote Elie Wiesel:<blockquote>The opposite of love is not hate, it&#39;s indifference. The opposite of art is not ugliness, it&#39;s indifference. The opposite of faith is not heresy, it&#39;s indifference. And the opposite of life is not death, it&#39;s indifference.</blockquote>So what is the opposite of disagreement? Is it agreement? Or, is it indifference?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>.

Read the show notes online: https://workingcode.dev/episodes/094-disagree-and-commit/

094: Disagree And Commit

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/9/19/14/19de08dd-c6c4-41e6-a939-d75c8dbc5728_working_code_-_093_-_sounds_easy_sure_isnt.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>On Adam&#39;s team, whenever anyone uses the phrase &#34;just&#34; to describe a level-of-effort, everyone jumps in and echoes &#34;just&#34; using air-quotes. Because, as many of us have learned over the years, nothing is ever as simple as it seems, especially in the world of web development. On this week&#39;s show, we talk about some of those tasks that end up being way more complicated than they should have been. Topics include: vertically aligning content, using JavaScript in 2022, logging data with sufficient context, tracking who made changes to a database, and storing notification flags for users that may never come back to your application.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>.

Read the show notes online: https://workingcode.dev/episodes/093-sounds-easy-sure-isnt/

093: Sounds Easy! Sure Isn't

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/9/12/15/abda2be7-3e83-430a-a7d2-30f3afcd83fa_working_code_-_092_-_the_power_of_no.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, the crew talks about the Power of No. For many of us, saying &#34;No&#34; is usually a challenge. Saying &#34;Yes&#34;, on the other hand, is usually the path of lease resistance. Saying &#34;Yes&#34; also feels good. In fact, saying &#34;Yes&#34; has so much appeal that we often rush into saying &#34;Yes&#34; to work before we even understand what that work entails or how urgent that work actually is. And, in many cases, that eager &#34;Yes&#34; ends up leading to a future failure. Which is why getting to &#34;No&#34; - or &#34;No, But&#34; - can help us maintain both our sanity and our professional relationships.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>.

Read the show notes online: https://workingcode.dev/episodes/092-the-power-of-no/

092: The Power of No

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/9/6/0/d7e7f0f9-41b3-4735-9ed1-2395217e81e4_working_code_-_091_-_side_project_therapy.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>On last week&#39;s show, we talked about &#34;Side Hustles&#34; - those extracurricular activities that we do in order to earn a little extra income. On this week&#39;s show, we want to talk about the flip-side to that coin: the coding that we do on the side because we freakin&#39; love coding! Carol celebrates the WordPress site that she&#39;s built and now maintains for her son&#39;s band, including the ability to accept payments and donations. And, Ben talks about trying to build a feature flag system using Lucee CFML and Angular. He also confesses that his blog has historically had a negative impact on his resolution to do more exploratory work. We also get to argue a bit about just how sexy TypeScript actually is.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>.

Read the show notes online: https://workingcode.dev/episodes/091-side-project-therapy/

091: Side Project Therapy

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/8/29/10/d39df941-fc5d-4faf-93c0-6fdf2bf76b40_passion_projects_and_beer_money_-_side_hustles.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, the crew talks about side hustles: the very American desire to be making money on the side. While many people in this world need side hustles in order to make ends meet, those in our industry (technology) often incur side hustles as a voluntary affliction. Of course, there&#39;s a fixed number of hours in each day; so, you&#39;re either earning passive income; or, your taking time away from your other interests (and commitments). This isn&#39;t always healthy. Nor should it be seen as a rite of passage - we on the show have a lot of respect for people that are simply content and can live their lives without grinding themselves down to a nub.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>.

Read the show notes online: https://workingcode.dev/episodes/090-passion-projects-and-beer-money-side-hustles/

090: Passion Projects and Beer Money - Side Hustles

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/8/22/10/7f9d5a1b-4111-4e85-bb1a-60bb47764fde_working_code_-_089_-_what_makes_a_good_roadmap.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>Like Michelangelo with a block of marble, we engineers often like to dive right into the code and let the application reveal itself to us. And while this may work on a very small scale, this extreme bias-towards-action isn&#39;t prudent for larger teams or companies with a growing client-base. Mature companies have roadmaps. They weigh the benefits of building one feature against the opportunity cost of not building another feature. Mature companies get buy-in both internally and externally. They then evolve their vision based on that feedback when it make sense; or, they apply grit when it is required.Or, at least that&#39;s the hope. Because, in reality, building a roadmap isn&#39;t easy. There are so many competing interests and such a limited amount of time. And then, there are Black Swan events like Covid-19, that force us all to stop and completely re-evaluate everything.This week on the show, the crew talks about what goes into a good roadmap; how we can avoid certain pitfalls; and, we question how far into the future a company should be looking on their roadmap.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>.

Read the show notes online: https://workingcode.dev/episodes/089-what-makes-a-good-roadmap/

089: What Makes a Good Roadmap?

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/8/15/9/c751d13c-a1f9-4160-b5e3-27bcbfa649f3_working_code_-_088_-_todo_documentation.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, the crew talks about documentation. Yay! As developers, there&#39;s no doubt that we all love consuming great documentation - especially for APIs. But, nary a one of us enjoys the process of creating documentation. Except maybe Adam, who&#39;s oddly passionate about communication. For the rest of us, however, documenting our choices and our subsequent outcomes feels a bit of a slog. It&#39;s never clear when we should be writing documentation; it&#39;s never clear what we should be documenting; and, it&#39;s never clear just how much detail we need to include. Sometimes, ironically, it seems that the more thoroughly we document a topic, the more likely it is to be misunderstood. So, that&#39;s awesome!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>.

Read the show notes online: https://workingcode.dev/episodes/088-todo-documentation/

088: //todo: documentation

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/8/8/10/ce11f396-4865-4334-8d88-1a4285648389_working_code_-_087_-_note_to_self_v0-2-0.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>On today&#39;s episode, we get to pull up the floor boards and once again peer into the dark recesses of Ben&#39;s brain: all the random and, frankly, sometimes incoherent chit-cat that Ben has with himself. Listen to him call B.S. on flaky tests; shake his first at overly-specific CSS selectors; preen about GulpJS build scripts; pontificate on the ROI (return on investment) of personal growth; and, theorize that building - not buying - can sometimes be the smarter (and less bureaucratic) move to make.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>.

Read the show notes online: https://workingcode.dev/episodes/087-note-to-self-v0-2-0/

087: Note To Self v0.2.0

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/8/1/12/c96c0506-8978-41f8-ac27-f08eacd6b524_working_code_-_086_-_the_working_code_test.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>Twenty-two years ago, <a href="https://www.joelonsoftware.com/" rel="nofollow">Joel Spolsky</a> wrote an article titled, <a href="https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/" rel="nofollow">The Joel Test</a>, which outlines 12-steps for evaluating the quality of a software team. At the time, Joel was working with Microsoft, building products that were delivered on CD-ROM. As such, his day-to-day workflow was somewhat different than the kind of work many of us are used to doing today. That said, much of what he had in his 12-point litmus test still holds true! Which I believe is a testament to how fundamental his insights were. This week on the show, the crew reviews Joel&#39;s list, gives each item our personal Yay or Nay, and then adds a few requirements of our own.Also, if you want a quick run-down of what we discussed, Adam summarized much of what we talked about in <a href="https://adamtuttle.codes/blog/2022/the-working-code-test/" rel="nofollow">The Working Code Test</a> over on his blog.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>.

Read the show notes online: https://workingcode.dev/episodes/086-the-working-code-test/

086: The Working Code Test

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/7/25/9/6433e260-2d62-4c4e-b2bb-e4ec8102454b_working_code_-_085_-_shipping_complexity.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>The less code you write, the easier it is for people to review, the less likely it is to contain bugs, and the more likely it is to merge cleanly into your main integration branch. The converse of this tends to also be true: the more code you write - particularly within a long-lived feature branch - the harder it is to review and the more likely it is to contain bugs that cause production issues. We all basically hold this to be true; however, that doesn&#39;t mean that we can simply choose to do the former. Shipping less complexity is a byproduct of both team and technology constraints. This week on the show, the crew talks about how they try to reduce the complexity of their code shipping process.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>.

Read the show notes online: https://workingcode.dev/episodes/085-shipping-complexity/

085: Shipping Complexity

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/7/18/12/eefc775f-0afb-4ffe-abf1-6c520820ccca_rchitectural_support_team_with_jason_henriksen.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, we interview <a href="https://www.linkedin.com/in/jason-henriksen-60b5b22/" rel="nofollow">Jason Henriksen</a> who works alongside Carol as a Software Architect at Clear Capital. According to Jason, every engineer does some degree of architecture, whether they know it or not. In fact, there&#39;s a lot of overlap between what Jason does and what your average web developer does. Which is why he calls his team the &#34;Architecture Support&#34; team. Their goal isn&#39;t to hand down edicts and pass out proclamations. Instead, Jason&#39;s goal is to build bridges between teams, help identify common pain points, propagate best practices, and lovingly guide the company in the right technical direction.Also, special thanks to Tim for only asking great questions!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>.

Read the show notes online: https://workingcode.dev/episodes/084-the-architectural-support-team-with-jason-henriksen/

084: The Architectural Support Team with Jason Henriksen

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/7/12/3/c67a9018-4c77-44ca-915d-fab869882d93_working_code_-_083_-_alternate_timelines.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>We all love writing code. Honestly, here on the show, it&#39;s hard for us to imagine doing anything other than building beautiful digital products for our beloved customers. But, as a thought experiment - in these post-pandemic times - the crew wanted to share some of the other professions that could have been. From ice cream truck driver to organic chef to movie theater entrepreneur, we dive into the untapped world of alternate realities.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>.

Read the show notes online: https://workingcode.dev/episodes/083-alternate-timelines/

083: Alternate Timelines

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/7/4/15/9901c39b-7c7d-4fc5-9635-45f1d8b4252f_ing_code_-_082_-_github_copilot_is_it_worth_it.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, the crew talks about <a href="https://github.com/features/copilot" rel="nofollow">GitHub Copilot</a>. After being in private beta for several months, this &#34;AI pair programmer&#34; is now generally available as a paid product for $10/month or $100/year. But is this something people want to pay for? Will a price put the kibosh on grassroots adoption? Are there pros-and-cons to different pricing models? And, is there ever going to be a world in which Ben can get past his own fanatical formatting tendencies?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>.

Read the show notes online: https://workingcode.dev/episodes/082-github-copilot-is-it-worth-it/

082: GitHub Copilot - Is It Worth It?

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/6/27/15/c059c6aa-79f3-4719-ab92-196fba1299b0_working_code_-_081_-_total_randos.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, the crew shares some of the random stuff that they&#39;ve been dealing with at work. Carol is about to submit a PR (Pull Request) that accounts for 8-weeks worth of commits; and, she&#39;s already warning her engineers that it&#39;s gonna be beefy! Ben wonders if he&#39;s been fooling himself into his love of Lucee CFML&#39;s &#34;Tag Islands&#34;; or, if there&#39;s something fundamentally more enjoyable about the developer ergonomics of the <code>CFQuery</code> tag. And, Tim&#39;s been working on remaining PCI (Payment Card Industry) compliant by scrubbing credit card numbers out of his customer&#39;s &#34;name&#34; fields; because, as it turns out, customers will jam a credit card number in just about any form field that they find!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>.

Read the show notes online: https://workingcode.dev/episodes/081-total-randos/

081: Total Randos

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/6/20/13/8c355aee-0700-4360-9a45-618254e59ee8_working_code_-_080_-_other_duties_as_assigned.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>In each role, there are the responsibilities that get listed on the job board; and then, there&#39;s all the random stuff that they ask you do to once you show up. On today&#39;s show, the crew discusses the latter: those strange and wondrous &#34;extras&#34; that sometimes get rolled-up into an honest day&#39;s work. Topics include: buying nipple cream, picking up cigarette butts, cleaning bathrooms, taking out trash, driving to remote server locations, restocking photocopiers, and - perhaps worst of all - getting pushed into Sales.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>.

Read the show notes online: https://workingcode.dev/episodes/080-other-duties-as-assigned/

080: Other Duties As Assigned

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/6/13/15/2272e7aa-0efd-4b60-9b54-9695d3492a8d_working_code_-_079_-_potluck_5.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, Adam and Ben examine a variety of random topics: Adam loves watching conference videos on YouTube; Ben is feeling terribly insecure about falling behind in the field of web development; neither of us can believe that Elon Musk is forcing his employees back into the office; and, how is it possible that some people seem have so much free time - what the heck is their secret?!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>.

Read the show notes online: https://workingcode.dev/episodes/079-potluck-5/

079: Potluck #5

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/6/6/16/07a070a3-6326-4b54-a12b-e9ed0426ff82_078_-_ux_pushing_users_into_the_pit_of_success.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, Adam and Ben talk about the &#34;unhappy paths&#34; in software design. An unhappy path - also known as a &#34;sad path&#34; - is anything that can go wrong during the consumption of a product. Some unhappy paths are nothing more than unanticipated edge-cases in the code while other unhappy paths are caused by poorly designed user interfaces (UI) that lack necessary constraints and affordances. But of course, it doesn&#39;t much matter why something is breaking, if our customers are unhappy, it is our job to fix it.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>.

Read the show notes online: https://workingcode.dev/episodes/078-ux-pushing-users-into-the-pit-of-success/

078: UX - Pushing Users Into The Pit of Success

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/5/30/14/9483b82f-a071-4c63-a228-92a9e1b0f025_working_code_-_077_-_mid-manager_blues.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week, on the show, we check-in with Carol to see how she&#39;s adjusting to her new role. Carol was recently promoted to a position in which she is a Manager some of the time and an individual contributor (IC) the rest of the time. This setup has a lot of advantages; but, it is not without its challenges. Just last week, she was deep in the coding zone, on the cusp of solving a hard problem, when she had to stop what she was doing and jump into a meeting. This left her with a residue of resentment (in the moment), especially when the first few minutes of the meeting were nothing more than water cooler banter. To be clear, Carol absolutely loves what she is doing; and, she loves being a force-multiplier for her company; but, she&#39;s still in the process of finding a comfortable equilibrium.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>.

Read the show notes online: https://workingcode.dev/episodes/077-mid-manager-blues/

077: Mid-Manager Blues

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/5/17/0/74f1fbe3-32d4-45fa-b825-6a327951ee77_working_code_-_076_-_ben_needs_a_minute.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>If Ben crushes it in the woods, and no one is there to see it, is he truly crushing it? Such are the philosophical questions that go through Ben&#39;s brain as he continues to pour his heart and soul into a legacy product that no one else at the company cares about. That is, except for the customers that still log into the legacy platform on a daily basis. Don&#39;t those customers deserve something? Ultimately, Ben just wants to hear that he&#39;s doing a good job.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>.

Read the show notes online: https://workingcode.dev/episodes/076-ben-needs-a-minute/

076: Ben Needs A Minute

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/5/17/0/4b4bba73-e878-4d96-8a20-b5d8e09013d6_king_code_-_075_-_what_problem_does_this_solve.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>Carol - who has recently stepped into a managerial role - is facing an interesting situation: her company wants to start implementing process changes across the board. However, Carol&#39;s own team is kicking ass and taking names; and, she can&#39;t understand how any of the proposed changes will actually make her team more effective. In fact, she believes that some of the changes will be counterproductive for her team. So, the question becomes: how does she push-back against the proposed changes without looking like an antagonist or a contrarian?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>.

Read the show notes online: https://workingcode.dev/episodes/075-what-problem-does-this-solve/

075: What Problem Does This Solve?

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/5/9/23/ae5adc12-a072-4bca-b4ca-cef9c10970ec_working_code_-_074_-_what_s_on_your_workbench.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, the crew talks about what they&#39;ve been working on recently. Adam is exploring the use of AWS (Amazon Web Services) message queues and S3 in order to manage nightly data processing in a way that won&#39;t crush his application servers. Tim has been approved to use the national &#34;Do Not Call&#34; list and is now working to integrate this list into his communications workflow. Ben is dealing with post-deployment depression, which is often what happens when he&#39;s at the end of his R.O.P.E. And, Carol is de-scoping a massive project down into an MVP (Minimum Viable Product) that can be shipped within a single sprint in order to demonstrate the value-add of the concept!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>.

Read the show notes online: https://workingcode.dev/episodes/074-whats-on-your-workbench/

074: What's On Your Workbench?

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/5/2/16/5d17a3ef-766d-4a72-a2a7-65efa7c9dbe3_working_code_-_073_-_our_golden_parachute.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>In the 20+ years of Ben&#39;s career, he can&#39;t remember ever seeing a person in a leadership position get fired. He&#39;s seen plenty of people leave a company to &#34;explore other opportunities&#34;, typically accompanied by much praise and congratulations. He assumes that at least some of these people were actually fired; but, were allowed to depart under friendly terms. He poses this question to the crew: assuming that his assumption is valid, is suppressing this information healthy for the company (perhaps an effort to keep morale high)? Or, is it a form of <a href="https://en.wikipedia.org/wiki/Gaslighting" rel="nofollow">gaslighting</a> that creates confusion and dissent within the organization?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>.

Read the show notes online: https://workingcode.dev/episodes/073-our-golden-parachute/

073: Our Golden Parachute

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/4/25/13/ee947696-efd3-4b26-b352-11a1354a9752_working_code_-_072_-_too_many_hats.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, the crew discusses a topic submitted by <a href="https://mingo.nl/" rel="nofollow">Mingo Hagen</a>: Do developers wear too many hats, do they spread themselves too thin, and does the work suffer because of it? There are clears benefits and drawbacks to wearing a lot of hats. Knowing a little bit about a lot of things can cut down on communication overhead and enable teams to move faster. But, without specialization, solutions will almost certainly be sub-optimal; and, &#34;best practices&#34; may not even be known to the engineer. Ideally, a team should consistent of both generalists and subject-matter experts. This kind of balance creates a &#34;healthy tension&#34; that tempers perfectionism with pragmatism and keeps everyone moving forward at the right pace.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>.

Read the show notes online: https://workingcode.dev/episodes/072-too-many-hats/

072: Too Many Hats

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/4/18/13/263e4a48-2dcf-4259-b4c1-e6d7847b697c_working_code_-_071_-_potluck_4.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, the crew discusses a potluck of tasty topics. Ben is trying to figure out what project he wants to use as his vehicle for learning Docker and container-based deployments. Adam wants to completely overhaul his data synchronization workflow, but is having a lot of trouble getting excited about the work (despite all of the exciting ingredients). Carol is being worn-down by the analysis phase of a project and just wants to start doing the work and accruing some wins for her team! And, Tim just can&#39;t wrap his head around Functional Programming (FP) - I mean, how the heck can you possibly program anything without <code>IF</code>-statements?!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>.

Read the show notes online: https://workingcode.dev/episodes/071-potluck-4/

071: Potluck #4

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/4/10/2/351eef32-1133-4013-8533-2b72ad57d72c_working_code_-_070_-_self_reflections.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week on the show, the crew looks back on the first 70 episodes of Working Code and reflects on what&#39;s working, what&#39;s not working, and what we&#39;d like to see in the future. I think we all agree that we&#39;ve made it a lot farther than we thought we would. And, thanks to <a href="https://www.zcross.media/" rel="nofollow">Matt at Z-Cross Media</a>, we always end up sounding totes profesh&#39; on tape even when we sounded like bunch of monkeys in the recording studio. We&#39;ve also been super thrilled to see our Discord community become such a lively and diverse forum, even if half of it is just people mocking Ben for not having any tests. We&#39;re all excited to see how the show evolves; and, we hope you come on this adventure with us!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>.

Read the show notes online: https://workingcode.dev/episodes/070-self-reflections/

070: Self Reflections

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2022/4/5/16/e5b0859f-60f9-4689-9450-41109461686b_working_code_-_069_-_now_i_m_catching_events.mp3

Sponsors<ul><li><a href="https://workingcode.dev/audible" rel="nofollow">Audible</a> - get a free audiobook from Audible with no strings attached at <a href="https://workingcode.dev/audible" rel="nofollow">https://workingcode.dev/audible</a></li></ul>This week, Carol talks to us about how her Support team manages communication with their customers. And, how she&#39;d love to find an easy way for one Support engineer to know that another Support engineer is currently working on a given ticket. She&#39;s been exploring the use of WebSockets and &#34;presence channels&#34; as a means to provide feedback within the Support platform. And, more generally, she&#39;s been looking into the concept of Publish and Subscribe (often referred to as Pub/Sub) as a means to push information from one service to another. We talk a lot about <a href="https://pusher.com/" rel="nofollow">Pusher</a> - a fully-managed WebSocket SaaS offering; and, consider other techniques that might be helpful.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>.

Read the show notes online: https://workingcode.dev/episodes/069-now-im-catching-events/

069: Now I'm Catching Events

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.