Runtime Rundown - JavaScript and Web Development Joe Boyle and Evan Cooper

In this episode we cover "How to talk about deadlines at work" by Wes Kao. This is is a super practical guide for two sides of the same coin - missing deadlines. We cover the perspective of IC's and how we can best communicate deadline misses, and we also cover the manager perspective on setting the right culture around deadlines. We've got scripts for you to use, tactical tips, and personal advice so make sure to listen to the end!

In this episode we use "Engineers Are Not A Commodity" by the Stay SaaSy blog to jump into a range of topics including Agile (and how we disagree on estimates), what good managers look like, and why you can't just swap us out like cogs in a machine. This is a bit rant-y, but packed with good information and hot takes!

In this episode, we cover the tc39 Signals standards proposal written by a powerhouse group of influential figures in the JavaScript community and key contributors from various popular frameworks. This is a short but sweet breakdown of what Signals are, what it might mean to the industry, and what we think about the tech and the proposal itself.



Links:

JS Party episode 305 with Daniel Ehrenberg

In this episode, we cover Getting Things Done In A Chaotic Environment by the Stay SaaSy blog. This is a practical guide on how to move fast and get things done using Teenage Mutant Ninja Turtles as a metaphor.

We cover 4 pitfalls to avoid when trying to get things checked off your list and add a bunch of tips from our experience fighting Shredder (AKA corporate bull$%^&).

In this episode, we cover a few points from "Shipping to Production" by the excellent Pragmatic Engineer blog. This article outlines the many different ways code makes it into "production". We cover the extremes of too much and too little verifications, and everything in between. The article is long and we only cover a portion of it so give this episode a listen then read the source article for practical advice on your own deployment processes.

In this episode we cover "New GitHub Copilot Research Finds 'Downward Pressure on Code Quality'" by Visual Studio Magazine. This is a summary of a research paper put out by GitClear that looked at 153 million lines of code over 4 years to assess the impact of AI usage on code quality. The paper concluded that Copilot usage is steadily reducing code quality overall, and it looks like it's only going to get worse. We discuss the strengths and weaknesses of the paper, our own personal feelings on this, and Evan gets a little too existential.



References from the episode:

- Why I'm No Longer Using Copilot by Dreams of Code on YouTube

- The Primeagen's reaction video