We're back! After almost 3 months of paternity leave, Runtime Rundown is kicking off our 4th season with everyone's favorite topic - performance reviews. We're just getting back in the saddle, so this is a free-form episode without an article. We cover the pros and cons of peer reviews, tech incentive structures and more.

In this episode we cover "Why I'm skeptical of rewriting javascript tools in faster languages" by Nolan Lawson. This is an interesting intersection between tech problems and people problems. There's been a recent wave of venerable JS-based tools being re-written in Rust, Go, Zig, etc. They come out "faster", but are we better or worse off for it?

In this episode, we cover "Pair Programming" written by the inimitable Matt Hamlin. We talk about what pair programming is, why you might do it, and when you maybe shouldn't.

In other news, Joe forgets how to intro the show and Evan drank too much coffee before recording.

In this episode we cover "The T Shaped Engineer" by Alex Kondov, and make a few references to Adam Savage's video How to Ask for a Job (Without Asking). As usual we go off on many tangents and eventually circle back around to the article.

Have an idea for an article we should cover? Head on over to https://runtimerundown.com/suggestionshttps://runtimerundown.com/suggestions and drop us a line!

In this episode we dive into another awesome article from Abi Noda, Using AI to encourage best practices in the code review process. This article covers a recent research paper released from Google outlining the performance, pitfalls, and process of their in-house AI code review bot. We talk about the role of AI in code reviews, our personal views on what code review is all about, and get existential on AI taking our jobs (again). Despite the AI title, this one is just as much about code review in general as it is about AI so if you're sick of AI content - there's still something here for you.

In this week's episode we cover "Using your own product is a superpower" on the PostHog engineering blog. Using your own software, AKA "dogfooding", is one of those topics thrown around by engineers all the way up to CEOS. We talk about what dogfooding looks like, why you would want to implement it (if you can), and some pitfalls of working it into your day-to-day.

In this follow-up to our Speed-running Projects episode, we talk about our ongoing effort to speed-run building a SaaS business from the ground up! We cover what we're building, how we approached it, and what we've learned along the way. We also dive into some of our technical choices and pivots.

Get ready for a knock-drown, drag-out brawl! Just kidding. Joe and I calmly debate the merits of Vim vs No Vim development and Joe nearly converts me.