Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

The Ruby on Rails Podcast

The Ruby on Rails Podcast artwork

Episode 556: Building What Matters with Tom Rossi

Oct 14, 202625 minAudio
ShareXLinkedInFacebookWhatsAppEmail

Recorded at Rails World, David sits down with Buzzsprout co-founder and CEO Tom Rossi for a wide-ranging conversation about AI, software development, product thinking, and the changing role of developers. Tom shares his perspective on the rapid pace of change in the software industry and why today's AI transition reminds him of the early days of the internet - only moving much faster. They discuss how AI is already changing development inside Buzzsprout and Higher Pixels, from adding AI-powered features for podcasters to making it dramatically easier to understand, maintain, and extend older Rails applications. But as the cost of building software falls, Tom argues that another skill becomes increasingly important: deciding what is actually worth building. David and Tom discuss the shift from thinking primarily as coders or engineers toward thinking as makers - understanding customers, identifying valuable problems, and choosing work based on the impact it can have rather than simply because it can be done. The conversation also turns to podcast analytics and David's experiments building his own analytics application with AI. They explore the difference between collecting more data and answering genuinely useful questions, why analytics should help creators make better decisions rather than send them down distracting rabbit holes, and how the same principle applies to product development. Ultimately, the conversation asks what developers uniquely contribute in a world where AI can generate increasing amounts of code: judgment, prioritization, customer understanding, and the ability to recognize which problems are actually worth solving. Sponsor Judoscale - https://judoscale.com/

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show.

TOM ROSSI Happy Wednesday and welcome to the show. Thanks for having me, David.

DAVID HILL for having me, David. Yeah, it's great to have you here, Tom. So we're here recording at Rails World in the Buzzsprout booth and you're the CEO and founder of Buzzsprout. And so I've been actually wanting to have a conversation with you for a long time. And so it's great to finally make this happen. Yeah,

TOM ROSSI Yeah, definitely. Let's do it.

DAVID HILL So Rails World, we're on day two of Rails World now. And how has the conference gone for you?

TOM ROSSI It's... But it's not Rails world that's unsettling. I feel like it's the state of the industry. Things are just changing so quickly. And so there's no place I'd rather be than with my fellow Rails developers as we are being unsettled together. Some people I think are in shock because maybe they weren't unsettled enough coming into the conference, but they certainly are now.

DAVID HILL All of my socials and Reddit and everything are kind of exploding right now with reactions to DHH's keynote, which for the first live streamed keynote, wow, that was definitely a choice.

TOM ROSSI Yeah.

DAVID HILL So much of what he said, I felt like, yeah, that makes sense. I'm on board with that. I know that his audience for, I know he says Omachi, but like there's an R in there and I can't not pronounce it. Omachi. You know, the audience for Omarci and Rails developers, like there's some overlap there in that Venn diagram. So like talking about that makes sense. Talking about AI as it's building and changing and impact the industry, that makes a lot of sense to me. The whole doom versus gloom bit, that makes a lot of sense to me. But kind of at Rails world, the keynote at a Rails -focused event for the sum total of his reference to Rails being, It's the internet. You can still use it, but we're rewriting one of our main applications in native and rust that felt bad.

TOM ROSSI Yeah. I think people are overreacting a little bit and I think it's kind of David's style to oversell. Absolutely. And when you think about writing an SMTP server, you probably don't want to build that in Ruby. Let's just be honest. That's not the kind of application that Ruby lends itself to. And if you're going to have an email client,

DAVID HILL And if

TOM ROSSI Let's be honest, a native experience is better. The only reason that we don't want to do native is because we don't want to have to maintain native code. And to his point, well, the cost of that maintenance now is a fraction of what it used to be. And so it makes it more attractive. But it's not like the web's going away. It's not like web applications are going away. It's just for those specific use cases, it totally makes sense to be able to embrace the best technology to solve the problem for the user. I was talking to somebody about the idea that Rails is more of a way of thinking. He did a great job of going back to that original blog video that many of us, that was my entry point into Rails. And he kept saying, look at what I'm not doing. And so much of that is the Rails way of thinking. Look at all the things I'm not doing. Look at the things that I get to focus on, which is really the product that I'm trying to build. Video wasn't about. it was about, I want to build a blog. Let me show you how easy it is to build a blog. And that's the world that we live in now is if you want to build something, it's so much easier to be able to build it. You want to build a native Mac OS app? You can totally do that, right? So it's more of a framework of thinking than it is for code. It doesn't mean that Rails is going away. It just means the way that we think is changing. It needs to change,

DAVID HILL It needs to change, yeah. I have some quibbles with the idea that developing and maintaining applications this way is for people like David, who have a lot more zeros in their bank account than I do. Yeah, it could feel like this is trivial, but like the amount of money they're spending, for example, on the Rails Foundation is dropping on benchmarking the various AI models, hundreds, sometimes thousands of dollars. I was like, that's so far beyond the realm of what I could imagine doing with my finances right now. Just using AI to build something that i have on a whim i don't know for me that still feels like that's outside of the reach of a lot of people who are the economy's not in a great state right now let's put it that way well it depends on how you look at it if you're just building something on a whim then it's a hobby right but if you need to make a living then you need to solve a problem right you need to figure out a problem that i can solve with software that somebody's willing to pay me for and if you can do that you are in

TOM ROSSI it depends on how you look at it if you're just building something on a whim then it's a hobby right but if you need to make a living then you need to solve a problem right you need to figure out a problem that i can solve with software that somebody's willing to pay me for and

DAVID HILL need to

TOM ROSSI if you can do that you are in an incredible place in history because if you can identify here's a problem that i can solve with technology you're going to be able to do it whether it's a web application whether it's a native application it's an incredible time to be alive but we have to move to those higher levels of thinking all of us and i like the term that he used like we need to think more like makers rather than engineers or coders And really get back to why do we do what we do? This is something that you'll hear developers say, right? Like, oh, this product would be so much better if it wasn't for all these users.

DAVID HILL if you can identify

DAVID HILL of us and

TOM ROSSI Right? Oh, these users, they do these stupid things. Well, the product exists for the users. To serve the users. Yeah. And so we have to remember that's what it's all about is trying to figure out how do we develop value in a way that it can pay our mortgage and our car. These things are important. But if all we're doing is building stuff.

DAVID HILL these users, they

DAVID HILL users. To serve the users. Yeah. And

TOM ROSSI to mess around yeah then like you said that's a hobby more than anything else yeah and it's a fun hobby but you got to go to work then that's fair and so we've been talking a lot about the conference what have you been seeing in your businesses with buzzsprout and higher pixels like how is the ai revolution for lack of a better term of phrase impacting your business i think

DAVID HILL like you said that's a hobby more than anything else yeah and

TOM ROSSI yeah and it's a fun hobby but you got to go to work then that's

DAVID HILL fair and so we've been talking a lot about the conference what have you been seeing in your businesses with buzzsprout and higher pixels like how is the ai revolution for lack of a better term of phrase impacting your business i

TOM ROSSI think There's a bunch of different lenses of how you look at it in terms of the product that we can deliver to our customer. Now with AI, we can do cooler things like with Buzzsprout, we can read the transcript of an episode and give you recommended titles and descriptions, chapter markers, things that are very simple for an AI to do, but it's time consuming and hard for our podcasters to be able to do. So there's great opportunity for us to deliver more value to those customers that are willing to pay us to be able to do the things that we do. But then there's another lens, which is, well, what does it mean internally for your team? And that's where it's very difficult because I've talked to a number of people here of just like the challenge of leading in an environment where you don't know where you're leading them. I don't know what it's going to look like, right? Let's be honest. And your people are saying, well, like alleviate my fears. paint the picture of what the future looks like. And you're like, man, I wish I could. I wish I could.

DAVID HILL man, I

TOM ROSSI And so one of my takeaways from these conversations with other people that are in similar places is to really lean in on values. What's important to the organization, that's not going to change. And I might not be able to tell you what it's going to look like to be a developer, a maker, an engineer, whatever, a prompt person, a meet proxy, whatever the title is going to be. I might not be able to tell you what that role looks like, but I can tell you as an organization that we care about our customers. We deliver value. We charge in line with the value that we provide. We care about our people. We want people to be developed. We want to invest in them and have this be the best place that they've ever worked and maybe the last place they work. So those are things that won't change. And so doubling down on values, doubling down on the things that are important. for the organization, for the health of the team in light of, I don't know where things might be, right? Like, I don't know where it's going to go.

DAVID HILL There'd be a lot of money you could make if you knew where things were going to go ahead of time. But like, that's never been something that people could reliably predict.

TOM ROSSI of time.

TOM ROSSI Yeah. And it's so anxiety producing, the speed that things are changing. I'm just learning how to... use the herder environment for my ai agents and now everybody's talking about jev and so okay now i gotta go learn this new way and i haven't heard of either of those before oh yeah so i don't even know what we're talking about anymore i felt bad i had my herder environment up and some guy leans over and he's like hey man what is that because everybody's doing this right and it's like oh well it's like just Everyone started doing it maybe three weeks ago. Yeah. And so things are changing so quickly. It's hard to not be anxious about it. But man, it's exciting when you see it do cool things.

DAVID HILL haven't heard of either of those before oh yeah so i don't even know what we're talking about anymore i felt

TOM ROSSI We have a product called Tick, which is a time tracking application. And we used to call it spinning plates because we had multiple products and you would work on the one product and you'd work on the other one. And then you'd go, oh, wait, now you go back to the other one. But that context switching between products can be difficult. Especially when it's an old code base. So Tick was built originally, I think, in 2006. It was our first Rails application. Oh, wow. And some of that code has probably aged poorly.

DAVID HILL probably aged poorly. Yeah,

TOM ROSSI Yeah, exactly. I was embarrassed for the AI to look at it. So we had an issue last week with one of our integrations, and it would have been horrible for me. to try to go back through my code that's over 10 years old to try to figure out like, oh my gosh, but all I had to do is give it to AI. And I'm like, look at the logs, look at the code, tell me what's going on. And it's like, oh, here's your bug. This thing changed and your code didn't handle it. And I was like, can you fix it? Boom, right? Like what a time to be alive to be able to see something like that. Yeah.

DAVID HILL go back

DAVID HILL I think I'm kind of late to the AI party. Like I just started playing with agentic code generation two or three weeks ago. I had a question about my podcast analytics, basically. It was like, I wanted to see the podcast host gives me like good visualization of like the actual download numbers, but it's like, okay, well, that's not telling me if this arbitrary episode is doing better or worse than previous ones. If there's any kind of a trend and overall audience or anything is like, I want to see some of that. Okay, let me see if the AI can help me build something like that. And it's like really fast. All of a sudden I had something showing up. I had a little application built. I had it downloading all the numbers from the host. It was like, oh, wow. It's got percentages showing up now and everything. It's really crazy how fast it just put this together.

TOM ROSSI And I feel like GrokBot,

DAVID HILL feel like

TOM ROSSI Muse, these new AI personal agent things have just come out. It's continuing this trend of just evolution where things are changing so quickly and there are tools that you didn't even know you needed until you had it. And then you use it. You're like, oh my gosh, now I can look at my podcast analytics in a way. I'm not relying on my hosting provider to be able to interpret it. I want to interpret it the way I want to interpret it. And it's incredible.

DAVID HILL incredible. Yeah.

DAVID HILL Some of the anxiety you kind of mentioned before, because I felt like our industry wasn't really changing a whole lot until very recently.

DAVID HILL I felt like our industry wasn't really changing a whole lot until very recently. I've been doing Ruby on Rails since 2008 or 2009, so nearly 20 years. This was the industry and this was my job. It'll always be this way, right? And now it just feels like the last couple of years, every couple of months, there's a new tidal wave that disrupts everything.

TOM ROSSI The speed of change is just dramatic right now. And you just don't know when it will plateau. Like when will it kind of solidify? It reminds me of the internet, but when the internet was first really making an impact.

DAVID HILL making an impact. I hadn't really thought about it that way, but that's fair.

TOM ROSSI Oh, it's just like 1995, 1996, where you saw companies were freaked out over, what does the internet mean for my business? And of course the local bookstore was like, nothing about my business dude you got this weirdo selling books on yeah amazon .com what's that yeah and then you couldn't have predicted it and it moved so slowly yeah the internet at the time we thought it was fast but really it was more like

DAVID HILL you got this weirdo selling books on yeah amazon .com what's that yeah and

TOM ROSSI yeah amazon .com what's that yeah and then you couldn't have predicted it and it moved so slowly yeah the internet at the time we thought it was fast but really it was more like I don't know, five, 10 years of evolution on the internet to change. For years, they would tell you how much money was being spent on the internet. And right before Christmas, it would be like, we estimate that 30 % of online sales will be done on the internet. Like every year it was part of the reporting of the news. And then now it's not even news. It's like, yeah, we regularly buy stuff on the internet.

DAVID HILL the internet. Well, over 90 % of the things my wife buys are bought on the internet these days.

TOM ROSSI bought on the internet these days. And probably from Amazon. But so they do this, they evolve, but it didn't evolve as quickly as what we're seeing with AI. So if you back up a year and it was not anywhere near where it is right now. And so it's just a much faster pace, but very similar to the disruption that the internet brought when it started making an impact in business.

DAVID HILL but very

DAVID HILL The key takeaway for me is I need to start really polishing up the skill of finding problems to solve that people want to pay money to have those problems solved for them. I 100 % think that all developers need to be thinking that way.

TOM ROSSI % think that all developers need to be thinking that way. Because AI is incredible at eating tokens.

TOM ROSSI is incredible at eating tokens. It's incredible at coming up with problems to solve that maybe don't matter. I can't tell you how many, I don't know if I should say this,

DAVID HILL don't know if I should say this, how many bugs it's found.

TOM ROSSI It'll find a bug. Now, it's an edge case of an edge case. But as a developer, with some sense of pride, when it finds a bug, you want to fix that bug. Well, we need to stop and take a step back and say, wait, should I invest my context? Should I invest my brain? Should I invest my time? And my token budget. And my token budget on solving this edge case of an edge case. Right now, I think we more than ever need to start thinking about what value do we bring to the equation? And the value is figuring out what's best for the value that I'm delivering on. What's best for the customer? What's something that's going to make an impact in their lives or our value proposition? So for Buzzsprout, we want to make podcasting as easy as possible to start podcasting and to keep podcasting. And so if I'm going and doing a PR to address a JavaScript error that it found that happens when a crawler hits certain page, like that's not going to impact my customer's life. It's not going to impact the value that they decided to pay us to deliver. Right. Right. And so I think all of us as developers are going to have to start asking those questions as opposed to having it dictated by a project manager or a product. team person who you know wasn't the coder but they were the one that would tell you what you're going to be working on what to prioritize what to prioritize and it would be given to the developer and they'd say okay here are the four problems for you to go solve i think as developers we have to develop that expertise now to say we're makers we're builders and we need to think about our customers first and figure out how can i deliver more value to them how can i use what i've got in this AI agent power to be able to deliver on that value.

DAVID HILL That makes a lot of sense. There's some contracting work I was doing for an old friend for a little while. It's an old Rails application, not as old as Tick, but it was, I think it's on Rails 6 right now, which is still just like woefully out of date. Every time I look at it, I'm just kind of like, we never get to upgrade this and get it modernized because we always have this backlog of This is what product says we need to work on next. We need to address these bugs and these fires next. It's like, okay, a lot of these problems I feel like would go away if we had the latitude to actually modernize this application.

TOM ROSSI Yeah. And it opens up the door for, I mean, we were just talking about tick. The door is open for us to add features to tick now. Right. The velocity that we are able to move in terms of feature development is faster than It's so ridiculous. It's so ridiculous. And so now imagine having to go back into that tech code base and build a feature. It would have been so intimidating, but now it's not intimidating at all.

DAVID HILL Yeah.

TOM ROSSI We've always done a good job of keeping it kind of current. It's on Rails 7 something, you know, but it's pretty close to being upgraded to Rails Edge. And now with AI, I'm pretty confident I could get there in a day. It's opened the door for us to be able to go to older products and build out features. As long as we put on that lens of how can I modernize it so that I can deliver more, I can convert more customers. I could reduce my churn. There's different things that I could do. And that's the kind of thinking that I want for all of my developers. I want all of them thinking, how can we deliver on our mantra for each of our products, the value prop that it puts forward to its users. Right.

DAVID HILL The little mini podcast app thing that I've been working on for the analytics. I was mostly just kind of letting AI kind of run with it for a little bit. It's like, this is kind of what I want. And it's like, okay, yeah, we can do this. We'll do a rolling median with or to calculate things at first. And then it found this other algorithm that was more resistant to outliers. And so I went with that one and kind of compared the two. And it's like doing all this work. I'm like, okay, this is really cool. I got a decent ways into it and realized. It wasn't treating an episode as fully mature in terms of its downloads until it had been published for 30 days. I was looking at that and looking at a lot of my actual raw download numbers. I was like, well, for most of my episodes, I could compare the 30 -day number and the one -day number. And the one -day number was consistently within 45 % to 55 % of the 30 -day download number. I was like, I think this one -day number is more important than you've been giving it. credit for yeah it like fed that to the ai and is like oh yeah we should totally address that it's like okay if i was building this application by hand at this point where it's like i've made a whole bunch of decisions now to go back and have to be like okay i need this new publication window that we're paying attention to and everything i would have been such a pain to have to like stop forward movement to go back and rejigger things yeah because i made a bad decision at the start ai is so patient it's so nice now it's too nice i imagine i imagine that

TOM ROSSI like,

TOM ROSSI it like

TOM ROSSI have to like

DAVID HILL a bad decision at the start ai

TOM ROSSI is so patient it's so nice now it's too nice i imagine i imagine that all of our agents have their own little message board their own version of twitter or mastodon or something you wouldn't believe what my dumb user did this time oh oh oh let's go change everything we just did good one you know meat puppet i'm so glad you got me to do that right like you know some of the stupid things that we have it do when it's so nice to us it's got to have a way to vent right where you're like totally right everything that you just did just

DAVID HILL what my dumb user did

TOM ROSSI this time oh oh oh let's go change everything we just did good one you know meat puppet i'm so glad you got me to do that right like you know some of the stupid things that we have it do when it's so nice to us it's got to have a way to vent right where you're like totally right everything that you just did just throw it out because I think we should do it this way instead. Oh, you mean the way that I originally proposed? Yeah. Okay. Yeah. Let's go do that now. Smart guy.

DAVID HILL you're like totally right everything

DAVID HILL Right. Throw a little sarcasm in the AI. Yeah. Telling the AI just like to go back and do that. It was just like, this would have been an immediately daunting thing to stop all forward movement and to go back to fix something, an assumption I'd made poorly at the beginning or that the AI made at the beginning.

TOM ROSSI Right. Throw a little sarcasm in the AI.

DAVID HILL And I was like, oh, look, it just did it before we came in here. Having the agent finish up one last thing before I started wandering around the hall again. I was like, oh, look, I have the one day thing set now. Git commit. Okay, I can walk away for a couple of minutes and decompress now.

TOM ROSSI Yeah, I think podcast analytics, I spent a lot of time, obviously, with podcast analytics. And I think it's a great example of where people can forget what's valuable, just like we're talking about with coding. Because what happens is they ask questions all the time. We always want more information on what's going on.

DAVID HILL always want more information on what's going on.

TOM ROSSI on what's going on. We want more information, but why do you want the information? And if you can ask the why, there's such a better chance you're going to get good results, right? Like for example, what you said is I want to see how my episodes are doing compared to one another. That is a great thing. Like I want to know which episodes did better when compared to other episodes. Like that's a high level value, right? It's valuable to you to know so that you can then go. okay, what did I do different with those episodes? What about this episode made it underperform or overperform so that I can do or not do those things to find better and better episodes?

DAVID HILL What about this episode made it underperform or overperform so that I can do or not do those things to find better and better episodes? Maybe I did a different promotion strategy with one episode than I did with another one and I want to compare to see how they did.

TOM ROSSI find better and better episodes? Maybe I did a different promotion strategy with one episode than I did with another one and I want to compare to see how they did. Those are really good, valuable things. Whereas I'll have people that will ask questions about data, but there's no why for it. They just, on a whim, I want to know what time the download occurred. How does that help you?

DAVID HILL you?

TOM ROSSI I want to know what time people download. I'm like, well, what about time zones? Do you have people? It makes no difference. What question are you trying to answer by asking for the time of day? And I'm not saying that there's some edge case out there for some live podcast or something that makes sense. But for 99 % of the podcasters, when they're asking for something like that, you've lost the plot. You need to start at the high level of what question. is valuable for you to ask your analytics and then dig into that and it's exact same thing when ai says hey man you should go fix this javascript issue as a developer we need to go wait a minute is that really worth my time because you know you think it's all it's one prompt and it'll be done it's not it's going to take time yeah right and it's going to result in a pull request it's going to trigger a ci like there's going to be these things that happen and so we need to take a step back and go well how is this going to help it be more valuable for my customer right So much of what you were just talking about just kind of harkens back to some experiences I had earlier in my career.

DAVID HILL you were just talking about just kind of harkens back to some experiences I had earlier in my career. I had one of those experiences where like the product owner was just kind of like, I want you to build this feature in the application. It was just kind of like, why? You already have something in there that essentially does that. So you're just like this so insistent. I need this thing. Why? What is it supposed to do? I just need this thing. Stop asking questions and give me this thing. And if I give you the thing,

TOM ROSSI if I give you the thing, there is a chance that it will actually undermine the value that I'm selling you. Right. Right. There's feature requests that we get, but if I actually gave you that feature, it would undermine the value that I'm giving you. For example, by giving you a breakdown of downloads by time. Now I've distracted you. I'm trying to help you start podcasting and keep podcasting, but I've just given you this distraction, this false. signal that will just make you spiral versus thinking about how can I create better content for my listeners? Right. Right.

DAVID HILL Right. You've literally accidentally given them a rabbit hole to fall into.

TOM ROSSI Yeah. And they ask for it. It's just our nature. Like you said, like we love more information, but my job as a product developer is to deliver on the value prop that I gave you, which is, I mean,

DAVID HILL which is, I mean, I want to make podcasting easy to start and easy to keep podcasting.

TOM ROSSI to start and easy to keep podcasting. How is that going to help? How is that going to help? And if they can paint the picture for how the feature request that they're asking enables that,

DAVID HILL How is that going

TOM ROSSI that, let's have a conversation. But otherwise, is it really worth the development resources? And the future of competition for products, I think, is going to be that. Because just the number of features doesn't matter. Because anybody can just... throw AI and build features. And so choosing which features to build is going to be more important than ever. Interesting.

DAVID HILL Because anybody

DAVID HILL Buzzsprout was my first podcast hosting platform. So for me, at least I had that experience of like, you made it really easy to start and keep going. So thank you for making Buzzsprout because I'm here, at least in part, because you made it really easy for me to get started.

TOM ROSSI for making Buzzsprout because

TOM ROSSI Well, thanks. Yeah. Well, we appreciate you. We appreciate all the Ruby on Rails. podcast it's so much fun when they announced rails world and i talked to amanda about like what could we do because we've taken so much from the rails community and we just can't give enough back right she was like well would you guys do a recording studio i'm like that would be amazing i'd be so much fun so this is great i look forward to it every single time i get to come to rails world it's like the bun sprout booth and i get to record it it's so much fun that's great that's great

DAVID HILL i look forward to it every single time i get to come to rails world it's like the

TOM ROSSI sprout booth and i get to record it it's so much fun that's great that's great

DAVID HILL Awesome. So is there anything else you'd like to mention before we wrap it up?

TOM ROSSI I think that's it. Thanks for having me. Thank you for joining me on the show today,

DAVID HILL you for joining me on the show today, Tom. Thanks.

Open the transcript file

Hosts and Guests

Hosts

  • David Hill Host Feed-stated

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Episode 561: Building Tools & Community with Adrian Marin

    Nov 18, 202640 minAudio

    What makes a Ruby conference memorable - and what does it take to organize one? Adrian Marin joins David Hill to share lessons from creating Friendly.rb as David prepares to launch Ruby Magic in Orlando. They discuss...

    Credit the people on this episode

  2. Episode 560: Do It While Crying with Rachael Wright-Munn

    Nov 11, 202641 minAudio

    What does it take to make an open source project welcoming to contributors - and manageable for its maintainers - in the age of AI? Rachael Wright-Munn joins David Hill to share what she’s learning through her work on...

    Credit the people on this episode

  3. Episode 559: From Consulting to Rails Products with Eduardo and Camila Souza

    Nov 4, 202633 minAudio

    What happens when the tool you rely on disappears? For Eduardo and Camila Souza, the shutdown of Pivotal Tracker became the motivation to build Pivotal Tasker, a Rails-based alternative inspired by the project...

    Credit the people on this episode

  4. Episode 558: Background Batches with JP Camara

    Oct 28, 202632 minAudio

    JP Camara joins the show to explore background job coordination, real-time collaboration, and the opportunities he sees for Ruby and Rails as AI changes how developers work. First, JP shares the story behind bringing...

    Credit the people on this episode

  5. Episode 557: Jessica Kerr and Avdi Grimm

    Oct 21, 202647 minAudio

    What does it mean to be a software developer when writing code is no longer the central part of the job? Jessica Kerr and Avdi Grimm join David Hill for a conversation about the changing work of software engineering -...

    Credit the people on this episode