In this episode we cover two articles for the price of one in our attempt to answer the question - does software quality even matter?

First up, "Are bugs and slow delivery ok?". This may be a thinly veiled advertisement for a consultant but it does pose some soul-search-worth questions. We reflect on them through a response article full of rage and resignation - "Responding to “Are bugs and slow delivery ok?”: The blog post that I’ve hated the most, ever".

Evan is failing to learn how to estimate tasks better, and Joe is improving in Japanese!

In this episode, we cover "Thoughts from “Meet Safari for Spatial Computing” by Jim Nielsen. If you haven't seen Apple Vision Pro yet, it's the future of dystopian wearables. The big question is how does this 3D AR/VR website view and interact with the 2D internet? For the answer to that question you'll have to listen to the episode. Here's a teaser - to enable the future we need to look back 30 years....

Joe and Evan both pronounce regex weird (or right depending on the audience), we have our sound effects back, and Joe nitpicks a listener for leaving a comment in the "wrong" place because he's a real nerd.

Links:

- Joe's Password game

- Swedish Wood City

- Regex learning website

TOTALLY not a clickbait title to drum up listeners....

In this episode, we dive deep into "Imaginary Problems Are the Root of Bad Software". It starts off small - why is there such a difference between acceptance criteria and deliverables? Why is it we tend to solve X when we're asked to build Y? It goes bigger and bigger from there and eventually asks the question, do any of our jobs even matter? This is hopefully a cathartic listen for all you devs out there. If not, yell at us over at Runtime Rundown.

Joe is learning how to hack passwords, Evan is forever learning accessibility (and making flashcards like the old man he is), and we lost our sound effects so this one is a bit weird. Enjoy!

In this episode we cover "Hands on with the Node.js test runner" By Phil Nash. Joe and Evan take a hard look at the now stable release of the Node.js native test runner. We talk about what it can do, what it can't do, and how it stacks up against the biggest player in the space...Jest.

Evan is learning wayyy too much about making espresso, and Joe is finally back on track and learning via HackAttic.

In this episode, we cover "The Cognitive Load Developer's Handbook" by Artem Zakirullin (and contributors). This is a practical episode on making your code as easy to read and follow as possible. We give tips for reducing complexity and being kind to the next developer to work where you left off.

Joe once again weasels out of learning (this is the last one or he's fired), Evan is getting lost on purpose, and our good news gets a little weird.

Go to our suggestions page and tell Joe to learn something.

In this episode, we cover "The JavaScript Ecosystem Is Delightfully Weird" by Sam Ruby on Fly.io blog. This article and episode are a loose continuation of last week's episode "Did The Web Go Too Far" where we yelled at the internet for going too far with Javascript and how there is an endless stream of new things to keep up with. This time we look back at the same progression of the web, but ask "what if that endless stream of innovation is a good thing"?

Joe learned one thing, and Evan is learning more things that you almost definitely don't care about.

Go to RuntimeRundown.com and leave us a suggestion if there is a topic you want covered!

In this episode, we cover "The Web I Want" by Chris James. This article is an excoriating take on what's wrong with the modern web. Spoiler alert: it's too much Javascript (according to Chris). As a couple of certified old guys™ and current JS devs, Joe and I are uniquely qualified to talk about where we are in the evolution of the web and where, if at all, we all went wrong.

Get ready for some hot takes including a classic TS downvote-fest by Evan.

Joe is learning how to implement DNS in a weekend while Evan goes deep on horticulture and learns about grass seed for different climates and sun exposures. You're welcome.

Check out RuntimeRundown.com for all your commenting and suggestion needs and don't forget to rate us in your favorite podcast player!

Music by ⁠Hina⁠ and ⁠Kevin MacLeod⁠

In this episode, we cover "Ups and Downs of A Side Project" by Jereme Greze. We cover some of the things you should and shouldn't do when starting and sustaining a long-term side project. Should you build something super specific, or cover a wide use-case? Should you build "quick-and-dirty", or start with scalability in mind? Check out the episode for a full breakdown.

Evan is still learning accessibility, Joe is somehow learning something nerdier than "bloom filters", and we have some faith-restoring good news.

Go to our suggestions page to drop us a note with feedback, suggestions, grievances, praise (we love that) , or just to say hey. We will shout you out in an episode!

We're switching it up again - this time with a grab bag where we cover a trio of topics.

We start with a listener request and get deep into our feelings on SCSS in 2023. Spoiler alert, it's serious. Then we move on to "Just Simply" and cover all the words you shouldn't use in your technical communication. Finally, we round it out with "Writing Tips for Improving Your Pull Requests" and give our two cents on the importance of crafting a great pull request (with some tips).

Links from the show:

• Natali Vlatko - Documenting the (Ancient) History of your Project

• Dan Abramov's Preact Signals bug report comment

As always, head on over to RuntimeRundown.com and let us know what you think of the new episodes with the suggestion box.

Music by ⁠Hina⁠ and ⁠Kevin MacLeod⁠

In this episode we cover "How to Lead a Project - as a Software Engineer" by Gergely Orosz. This is a practical, step-by-step guide on crushing the soft-skills portion of a project. We cover how to set a good foundation of communication, how to effectively manage risk, best practices for updates, and a whole lot more.

No matter what level you are in your career, following this guide for your next project (big or small) will definitely set you apart as an effective leader.

We get back to our roots and deliver some new learning and some great news to sail away on. Also, we are still tinkering with our into and outtro...so we're sorry about that.

As always, visit Runtime Rundown to drop us a suggestion, listen, and comment on episodes. Thanks for listening!