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/7/25/3/ec9a6bb9-b843-45f9-a910-4573c58349b7_8_-_yeeting_changes_to_production_code_reviews.mp3

In this week&#39;s episode, Tim returns to the podcast for a discussion on code reviews, touching on the importance of providing constructive feedback, tailoring reviews based on the developer&#39;s experience level, and discussing the merits and drawbacks of tools like GitHub.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/188-yeeting-changes-to-production-code-reviews/" rel="nofollow">here</a>.

In this week's episode, Tim returns to the podcast for a discussion on code reviews, touching on the importance of providing constructive feedback, tailoring reviews based on the developer's experience level, and discussing the merits and drawbacks of tools like GitHub.

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/188-yeeting-changes-to-production-code-reviews/

188: Yeeting Changes to Production - Code Reviews

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/7/17/8/69097c50-025c-4210-9022-d57fb711e08f__is_it_possible_to_be_a_solo_developer_in_2024.mp3

In this week&#39;s episode, Adam and Ben talk about the feasibility of being a solo developer in 2024, considering industry pressures, tools, and personal strategies for balancing simplicity and complexity in the development 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>.Full show notes and transcript <a href="https://workingcode.dev/episodes/187-is-it-possible-to-be-a-solo-developer-in-2024/" rel="nofollow">here</a>.

In this week's episode, Adam and Ben talk about the feasibility of being a solo developer in 2024, considering industry pressures, tools, and personal strategies for balancing simplicity and complexity in the development process.

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/187-is-it-possible-to-be-a-solo-developer-in-2024/

187: Is it Possible to be a Solo Developer in 2024?

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/7/9/21/0993f678-b51a-4626-a32d-35d4568be7de_186_-_warm_blankies_for_your_work_insecurities.mp3

In this week&#39;s episode Ben and Carol delve into their personal and professional insecurities. The discussion includes feeling the need to justify one&#39;s value at work, struggles with validations. They also talk about the emotional impact of customer interactions and the importance of human connections. The conversation highlights broader issues regarding job promotions, industry expectations, and the myth of constant innovation.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/186-warm-blankies-for-your-work-insecurities/" rel="nofollow">here</a>.

In this week's episode Ben and Carol delve into their personal and professional insecurities. The discussion includes feeling the need to justify one's value at work, struggles with validations. They also talk about the emotional impact of customer interactions and the importance of human connections. The conversation highlights broader issues regarding job promotions, industry expectations, and the myth of constant innovation.

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/186-warm-blankies-for-your-work-insecurities/

186: Warm Blankies For Your Work Insecurities

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/7/3/22/7efc1e52-76aa-486a-a929-e5b9890adcd7_working_code_-_185_-_adam_s_ab_testing_mvp.mp3

On this week&#39;s show, Adam and Ben explore the complexities of implementing AB testing in email campaigns.The hosts tackle the challenge of integrating AB testing into existing systems without causing disruptions and examine methods for experimenting with various elements like subject lines, calls-to-action, and email contents. They also discuss strategies for automating the selection of winning variants based on metrics such as opens and clicks.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/185-adams-ab-testing-mvp/" rel="nofollow">here</a>.

On this week's show, Adam and Ben explore the complexities of implementing AB testing in email campaigns.

The hosts tackle the challenge of integrating AB testing into existing systems without causing disruptions and examine methods for experimenting with various elements like subject lines, calls-to-action, and email contents. They also discuss strategies for automating the selection of winning variants based on metrics such as opens and clicks.

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/185-adams-ab-testing-mvp/

185: Adam's A/B Testing MVP

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/6/26/5/6f0e1f1c-7e13-4591-8d68-55ca7cde414a_-_184_-_solving_world_peace_with_code_comments.mp3

On today&#39;s show, Adam and Ben talk about their respective strategies for leaving comments within code. Each of them inhabits a different end of the spectrum, with Ben erring on the side of viewing comments as an inherent value-add; and, Adam believing that the urge to add a comment is more akin to a &#34;code smell&#34;, indicating a need to refactor the underlying code structure. They disagree on a lot in this conversation; but, it turns out, they actually agree on more than you might expect.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/184-solving-world-peace-with-code-comments/" rel="nofollow">here</a>.

In this week's show, Ben and Adam discuss the aesthetics and functionality of code comments.

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/184-solving-world-peace-with-code-comments/

184: Solving World Peace with Code Comments

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/6/19/17/8e2ff260-1edf-4c52-a962-3bbdb58a90db_-_183_-_whos_got_the_beans_carol_s_new_project.mp3

In this episode, the team discusses various aspects of starting new projects, dealing with both personal and professional challenges, and the excitement and fears around initiating new work.Carol shares her idea for a new web application to help organize event contributions, and the group explores initial steps and considerations for starting such a project. They touch on security, data management, and different frameworks and platforms for developmentFollow 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/183-whos-got-the-beans-carols-new-project/" rel="nofollow">here</a>.

In this episode, the team discusses various aspects of starting new projects, dealing with both personal and professional challenges, and the excitement and fears around initiating new work.

Carol shares her idea for a new web application to help organize event contributions, and the group explores initial steps and considerations for starting such a project. They touch on security, data management, and different frameworks and platforms for development

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/183-whos-got-the-beans-carols-new-project/

183: Who's Got the Beans? Carol's New Project

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/6/12/4/83b79936-9926-4d8a-82e8-cfa1d398190f_rking_code_-_182_-_coffee_talk_and_catching_up.mp3

On today&#39;s show, Tim and Carol share personal updates while Adam and Ben are away. Carol discusses her challenging workday involving a difficult rebase and adjusting to a new routine after moving to Texas.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/182-coffee-talk-and-catching-up/" rel="nofollow">here</a>.

On today's show, Tim and Carol share personal updates while Adam and Ben are away. Carol discusses her challenging workday involving a difficult rebase and adjusting to a new routine after moving to Texas.

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/182-coffee-talk-and-catching-up/

182: Coffee Talk and Catching Up

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/6/3/23/b8599da4-7545-4f12-9521-6e4d33ec56c4_working_code_-_181_-_more_laws_of_software.mp3

On today&#39;s show, we continue our discussion of the entries outlined on the website, the <a href="https://www.laws-of-software.com/" rel="nofollow">Laws of Software</a>. Topics include McKinley&#39;s law on boring technologies, Doerr&#39;s law on aligning team vision, and Fitt&#39;s law on target touchability.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/181-more-laws-of-software/" rel="nofollow">here</a>.

On today's show, we continue our discussion of the entries outlined on the website, the Laws of Software. Topics include McKinley's law on boring technologies, Doerr's law on aligning team vision, and Fitt's law on target touchability.

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/181-more-laws-of-software/

181: More Laws of Software

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/5/27/19/bdb445b9-397e-42e5-a3eb-0923a693bae2_working_code_-_180_-_the_laws_of_software.mp3

On today&#39;s show, we discuss a few of the entries outlined on the website, the <a href="https://www.laws-of-software.com/" rel="nofollow">Laws of Software</a>. Topics include Atwood&#39;s Law on JavaScript, Cunningham&#39;s Law on getting answers, Parkinson&#39;s Law on getting things done, Goodhart&#39;s Law on taking measurements, Hofstadter&#39;s Law on inevitable failure, and the Peter Principle.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/180-the-laws-of-software/" rel="nofollow">here</a>.

On today's show, we discuss a few of the entries outlined on the website, the Laws of Software. Topics include Atwood's Law on JavaScript, Cunningham's Law on getting answers, Parkinson's Law on getting things done, Goodhart's Law on taking measurements, Hofstadter's Law on inevitable failure, and the Peter Principle.

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/180-the-laws-of-software/

180: The Laws of Software

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/5/20/10/72e59d38-543f-4223-9499-f337cc5d44d2_working_code_-_179_-_ai_sells_you_on_ai.mp3

On today&#39;s show, Tim gears-up for a farm insurance conference out in Nashville where he&#39;s hoping to educate farmers on the pros and cons of artificial intelligence (AI). But, ahead of his talk, he&#39;ll be using AI voice technology to call the conference attendees and convince them to attend his presentation. And then, hopefully, weave statistics and sentiment analysis insights—from these automated calls—back into his slide deck.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/179-ai-sells-you-on-ai/" rel="nofollow">here</a>.

On today's show, Tim gears-up for a farm insurance conference out in Nashville where he's hoping to educate farmers on the pros and cons of artificial intelligence (AI). But, ahead of his talk, he'll be using AI voice technology to call the conference attendees and convince them to attend his presentation. And then, hopefully, weave statistics and sentiment analysis insights—from these automated calls—back into his slide deck.

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/179-ai-sells-you-on-ai/

179: AI Sells You on AI

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/5/13/6/d20877f6-00d5-403c-b677-af0b1d190d76_working_code_-_178_-_upgrading_from_node_0-10.mp3

This week on the podcast, we touch on a variety of topics. Ben has been incrementally building a data export feature for his customers; and, he&#39;s gotten to a point in which he can see a viable light at the end of the tunnel. Carol has discovered that if she doodles circles with her non-dominant hand, it occupies the ADHD portion of her brain and frees her up to focus on reading. Tim is continuing to improve his AI voice-agent, using a listener-suggested approach to loading Spanish language voice models on demand. And, Adam is battling some pretty steamy code rot; and is attempting to upgrade a series of interconnected Node.js Lambda functions from v0.10—released in 2013—to v20.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/178-upgrading-from-node-010/" rel="nofollow">here</a>.

This week on the podcast, we touch on a variety of topics. Ben has been incrementally building a data export feature for his customers; and, he's gotten to a point in which he can see a viable light at the end of the tunnel. Carol has discovered that if she doodles circles with her non-dominant hand, it occupies the ADHD portion of her brain and frees her up to focus on reading. Tim is continuing to improve his AI voice-agent, using a listener-suggested approach to loading Spanish language voice models on demand. And, Adam is battling some pretty steamy code rot; and is attempting to upgrade a series of interconnected Node.js Lambda functions from v0.10—released in 2013—to v20.

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/178-upgrading-from-node-010/

178: Upgrading From Node 0.10

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/5/7/16/6c1666d2-7075-4398-b0d6-be80fed62d13_ing_code_-_177_-_infinite_invisibility_timeout.mp3

Adam uses the new CSS color functions for HSL (Hue, Saturation, Lightness) in order to <a href="https://stackoverflow.com/a/27263918/751" rel="nofollow">create a heatmap</a> for the number of dollars raised by his platform. Ben dives into the <a href="https://www.algolia.com/" rel="nofollow">Algolia search service</a> as a way to provide a search feature on his blog. Carol is trying to alleviate performance concerns around an N+1 SQL problem using an ORM (Object-Relational Mapper) that has decided to use an N+1 selection strategy as &#34;the way&#34; with no escape hatch. And, Tim is getting some great feedback regarding his AI-powered call system that will alert customers to upcoming renewal dates.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/177-infinite-invisibility-timeout/" rel="nofollow">here</a>.

Adam uses the new CSS color functions for HSL (Hue, Saturation, Lightness) in order to create a heatmap for the number of dollars raised by his platform. Ben dives into the Algolia search service as a way to provide a search feature on his blog. Carol is trying to alleviate performance concerns around an N+1 SQL problem using an ORM (Object-Relational Mapper) that has decided to use an N+1 selection strategy as "the way" with no escape hatch. And, Tim is getting some great feedback regarding his AI-powered call system that will alert customers to upcoming renewal dates.

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/177-infinite-invisibility-timeout/

177: Infinite Invisibility Timeout

https://s3.us-east-2.amazonaws.com/pod-public-media-files/2024/4/29/9/b7756f9a-460a-4bd6-accd-6f061160b6e2_rking_code_-_176_-_triumph_and_fail_safe_space.mp3

On today&#39;s show, we cover a variety of topics. Tim was suffering from a &#34;carding&#34; attack (aka, a &#34;credit card stuffing&#34; attack) and had to build an internal CAPTCHA system in order to protect his web-based payment forms from bad actors. Adam created an open-source JavaScript library for mocking ES modules (see <a href="https://github.com/atuttle/mockable" rel="nofollow">Mockable</a>) that makes it possible to swap implementation details at runtime. And Ben falls back in love with ColdFusion—again—continuing to find that even the small language details bring him great joy.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/176-triumph-and-fail-safe-space/" rel="nofollow">here</a>.

On today's show, we cover a variety of topics. Tim was suffering from a "carding" attack (aka, a "credit card stuffing" attack) and had to build an internal CAPTCHA system in order to protect his web-based payment forms from bad actors. Adam created an open-source JavaScript library for mocking ES modules (see Mockable) that makes it possible to swap implementation details at runtime. And Ben falls back in love with ColdFusion—again—continuing to find that even the small language details bring him great joy.

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/176-triumph-and-fail-safe-space/

176: Triumph and Fail Safe Space

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

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.