Working Code Adam Tuttle, Ben Nadel, Carol Hamilton, Tim Cunningham

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/

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/

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/

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/

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/

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/