Code with Jason Jason Swett

On today's episode, Matthew Kaliara joins me for a conversation on his work with his startup Rescale Supply. We also discuss React, ViewComponent, system testing, looks vs usability in design, flat design, the value of convention in design, usability testing, the inseparability of good UI design and good code, the importance of appropriate names in core components, and how good code can help with hiring.Rescale.SupplyMatthew Kaliara on LinkedInMatthew Kaliara on TwitterKaliara.com

It must be both hot dogs and buns, not just the hot dogs themselves. Preparation (e.g. skipping meals beforehand) is allowed.Guests: Peter Cai, Brandon Casci.

On today's episode, Brad Pauly and I dig into the five causes (raised conditions, fixed time dependency, randomness, leaky state, and network or third party dependency) of flaky tests. We also discuss diagnosing flaky tests, common pitfalls of fixing flaky tests, and things that do work for fixing flaky tests.Brad Pauly on TwitterBrad Pauly on GitHub

On this episode, I talk with Verda Korzeniewski about going into programming straight out of high school. We also discuss Verda's experience in 3D printing, problems in modern manufacturing, and problem solving skills that transcend programming. Verda Korzeniewski on LinkedInVerda Korzeniewski on Instagram

On today's episode, Trae Robrock joins me for a discussion of his new Rails project Translated and his hotel management software Comfort.ly. We also talk about managing a hotel, investing in real estate, internationalizing a Rails app, investing in assets that give you income, investing in your personal brand, marketing Comfort.ly, connecting with potential clients in person, the importance of having a comfortable working environment, reading to enrich yourself, and taking care of...

On today's episode, Andrew Atkinson joins me once again for a recap of events at Sin City Ruby 2024. We also talk about Andrew's new Postgres consulting venture, his upcoming book High Performance PostgreSQL for Rails and what he learned in the process of writing the book, deciding how to communicate what you do as a consultant, naming things appropriately, how poor decision making in the early stages in the creation of an app can make it prohibitively expensive to fix later,&nbsp...