Menu
Sign In Search Podcasts Charts People & Topics Add Podcast API Blog Pricing
Podcast Image

Ruby Rogues

Exploring Tech Choices and Team Dynamics with Jesse Spivak - RUBY 669

24 Jan 2025

Transcription

Full Episode

5.52 - 14.142 David Camira

Hey, everyone. Welcome to another episode of Ruby Rogues. I'm David Kumira. And today on our panel, we have Luke Sutters. Hi. And we have John Epperson.

0

14.563 - 15.083 John Epperson

Hello, everybody.

0

15.463 - 26.546 David Camira

And today we have a special guest, Jesse Spivak. Great to be here. So, Jesse, would you mind explaining just a bit about who you are, some of the things that you're doing, who you work for and why you're famous and all that good stuff? Sure.

0

27.95 - 52.331 Jesse Spivak

Yeah, absolutely. So my name is Justin Spivak. I'm a senior engineer at a company called Ibotta, which is a cashback for shopping app based in Denver, Colorado. I've been working there for about three and a half years. We are doing some hiring, so check out our careers page. I guess I'm famous, as it were, because I gave a talk at the first remote RailsConf this past May.

0

53.157 - 57.319 Jesse Spivak

And I talked about kind of how crummy of a developer I am. Yeah.

57.739 - 77.51 David Camira

I think we can all relate to that on a daily basis sometimes. So would you mind giving a bit of a, you know, highlight talk about what you covered at the conference and stuff, so we can just kind of pick it up from there. We'll link to the, in the show notes, a link to the conference, but just for those who maybe didn't see it. Sure.

77.57 - 105.034 Jesse Spivak

And, and there, there's no substitute for actually watching this fantastic talk. But more seriously, the talk is really about my experience as a tech lead at Ibotta working on a pretty critical project over the course of about six months or so. And over that time, I made four very big mistakes that put the project in jeopardy.

105.695 - 131.15 Jesse Spivak

And hopefully they're mistakes that I will learn from and not make again as I continue to lead projects that I've got in the future. And my hope is that by Sort of articulating these mistakes and what I learned from them, other folks can benefit. And so the four mistakes that I made are, first, we picked the wrong technology. We can get more into that. We also, as a team, we siloed work.

131.19 - 146.893 Jesse Spivak

So work was divided up in not the best way. We fell into the premature optimization trap. And then maybe worst of all, we made way too many changes at one time. So I can go into detail on any of those.

Comments

There are no comments yet.

Please log in to write the first comment.