Ruby on Rails, every mention

mentionsepisodesper episode tap a year for its mentions

Verbatim, from the transcripts: the passages where Ruby on Rails comes up

loading…

▶ 2:16 Garry Tan Like, I mean, that's what the half a million lines of Rails code was for me.

▶ 15:15 Garry Tan Like, it passed it, you know, it passed end-to-end testing, it passed integration, it passed unit tests, but, like, at the end of the day, I still need to, you know, for Gary's list, it's like, pop open the Rails server and, like, you…

▶ 0:59 Garry Tan I built GStack to encode this three weeks ago, and now it has more GitHub stars than Ruby on Rails.

▶ 37:12 Garry Tan 30 minutes walk through the internals of Rails job, like the active job, like a couple thousand lines of code, like trying to debug what was happening, and it found the bug, actually. 2 times in the scene
▶ 41:42 Garry Tan I guess what's funny is I tried to use Codex just now, uh, for my Rails project, but the thing is like, it's kind of obvious that nobody at OpenAI cares about Rails, which is fine. 2 times in the scene

▶ 13:25 Tom Blomfield Partially in Ruby on Rails, mostly because I was familiar with it from when I used to be a professional developer, but I was blown away by the AI's performance, especially when it was writing Ruby on Rails code. 6 times in the scene

▶ 13:00 Harj Taggar Like I remember when rails first came out, there was just like a real sense of, oh, like, I don't know, like active record as a way to like interact with your database was seen as a great abstraction, but like there was still the same…
▶ 15:44 Garry Tan And then to your point about active record and rails, that battle was actually fought to a standstill because of course using active record or rails allowed you to go from zero to one very quickly. 3 times in the scene

▶ 18:52 Diana Hu Although a lot of other peers were telling him to go and use Ruby and Rails, and I think in 2015, Ruby and Rails were 10 times more popular by Google Trends, and that was fine. 2 times in the scene

▶ 2:12 Des Traynor It was a Ruby on rails based error handler and, uh, and it would like alert developers and notified them, Hey, this piece went wrong and here's who was affected.

▶ 14:44 Ammon Bartram So it's way more likely that a smaller company is going to say, we're using, you know, Ruby on Rails. 2 times in the scene

Turn any episode into a week of clips.