TRANSKRYPCJA 🔗
WEBVTT
0:00:15.589 --> 0:00:18.711
Hey everybody,
0:00:20.331 --> 0:00:24.769
So, 99
0:00:25.410 --> 0:01:26.820
Episodes ago, we covered Ruby back in 2015. If any of you kind of heard that episode, you might have been sort of shaking your fist in the car or at the stereo. You know, Patrick and I have done a little bit of Ruby. You know, we did our best to do it justice, but I'm so thankful that here we are almost 100 episodes later. The podcast has really kind of come a long way. I'm really, it's kind of wild just thinking about it, but we have two amazing folks who know Ruby way better than Patrick and I will probably ever know in our whole lives. So we have Mike D'Alessio, Engineering Director at Shopify, and we have Evan Phoenix, longtime Rubyist on the show to talk about Ruby, also talk about Ruby Shield, Ruby Central, how Ruby plays a big role at Shopify and plenty of other companies, and really just dive deep into where the language has gone. So thanks so much, both of you for coming on the show.
0:01:27.420 --> 0:01:31.080
It's great to be here. Thanks for having us. Absolutely. Happy to be here.
0:01:31.820 --> 0:01:49.920
Cool. So maybe we'll jump in just with a couple of backgrounds. Maybe Mike, you want to go first and tell us sort of, you know, what your journey has been like, what your experience with Ruby has been over the years, and what kind of is the journey, the path that took you to Shopify?
0:01:49.920 --> 0:03:08.080
Guess my journey to Ruby starts before I used Ruby. When I started my career, I was working in physics and then later financial services using Fortran and C, which are two of the least user-friendly languages you can imagine. And so by the time I hit like mid-career, you know, mid-2000s at this point, let's call it 2005, 2006, I started to use Ruby for a couple of hobby projects, and it just, it made sense to me, like something clicked, like Ruby is just, it's very easy to use. And you can tell that one of the principles behind the language from the creator, Mats, is to make developers happy. Like it definitely made me happy and something clicked in my brain and it became my primary language for writing like one-off scripts or even for doing bigger projects. I tried as hard as I could to use it for my next full-time job, which I did. And it's kind of been downhill ever since. I even got my start in open source with Ruby as well. I started contributing back upstream and some very friendly people in the Ruby community were very encouraging, and it was painless. And I said, I guess I'll do this some more. And so now I've been using Ruby for something like 16 years and showing no signs of going back to Fortran at this point.
0:03:08.420 --> 0:03:40.536
Nice. So like, that's a really interesting thing. You fell in love with Ruby and then you said, you know, I would like to find a career where I can do Ruby. And so my impression is that might be challenging in something like physics. And so you probably have to switch
Load full transcript
disciplines, right? So what was that like? And it must be a, must be a really interesting sort of a set of calculus there to say, okay, I really love Ruby. I love physics. I can't really do both of these. I'm going to pick Ruby. And how did that whole thing go?
0:03:40.857 --> 0:04:54.320
For me, I had already left financial services where you're expected to use C or C++ or, you know, on a bad day Fortran. And I was already working at a small startup where I had the opportunity to play around with Python and PHP and Ruby. And like Ruby is kind of what I really liked, I really rocked it and I really understood it well, and it resonated with me. So then my next job was at a small startup with a friend from college. And we had the opportunity to build a new app essentially for, for let's call it energy trading. It wasn't really trading, but it was, you know, a company that owns some power plants. You need to bid your energy into the market and do some light trading. And I was like, I'm going to write this in Rails and it's going to be great. And it all came together in about three weeks. I had built a replacement for their previous system that looked almost identical. And like, that was the opportunity for me was to kind of put a bunch of my skills together and write this new Greenfield thing in Ruby at a new job at a startup where we had a lot of flexibility around the tech stack. I think that was, that was the key bit for me is Ruby was not a common language in 2007. And so I had to make my own opportunities in a way. We've come a long way since then. I think Ruby is very much enterprise at this point in time for a lot of companies.
0:04:55.460 --> 0:05:38.860
Yeah, that makes a ton of sense. We talked to a gentleman earlier who worked a lot with Dask and said something similar where, you know, they really wanted to use Dask and they found the only place at least local to them was a startup. And so it does seem like startups are a good place to have sort of more Greenfield, which is kind of counterintuitive, right? You would think like big companies with zillions of dollars to burn would be the place to go to experiment with new languages. But in practice, you find that, you know, they've built all the infrastructure around C and so everyone's using C. And if you want to use Ruby, you're going to have to fight through like 17 layers of the organization or something.
0:05:39.920 --> 0:06:12.760
Yeah, I think that you're right on the money that it does work that way in large companies and I think it's economies of scale. I think at some point companies get to a size and scale where they say, listen, exceptions are really expensive to track and take care of and limit the flexibility, right? Like, oh, you want to do this project in Haskell? Fantastic. You're one of three people who work for the company that know Haskell, and if you leave, then we're stuck with a Haskell project that nobody understands; we'll have to throw it away and start over. Like,
there's a lot of risks that big companies just don't want to take on new languages and new frameworks a lot of the time.
0:06:13.240 --> 0:06:25.860
Cool. That makes sense. So you're at this energy kind of management or energy trading startup. Did you go from there to Shopify or was there a string of opportunities in between? Oh, yeah, there's a bunch of stuff in between.
0:06:26.460 --> 0:08:14.000
So from that startup, you know, imagine it as I wrote some code for, you know, six months to try to get us a beta version that we could build and sell. We were in startup mode, and then I needed to go actually pay my mortgage. So I got like a day job and I was doing that at night. And my day job was at Pivotal Labs, which back in the day was a well-known agile consultancy that specialized in Ruby and Rails applications at the time. And so I started there and we worked on this enormous Rails app for a client called Case Commons doing child welfare management, which is a really, really complex business domain. And Rails helped us focus on like the business logic and not on the incidental complexity of building a large system. And that's when I really got sold on Rails as kind of the easiest and fastest way to get something new up and running. Later became a client at another startup of Pivotal, and I went back to Pivotal again, where I ran their New York consulting business. And then finally I worked on Cloud Foundry, which is like Heroku for enterprises, right? You want your developers to have that ease of pushing an app, but you have your own data center. Like, what do you do? You buy Cloud Foundry and you run it internally. And Cloud Foundry, as it turns out, was originally built by VMware in Ruby. Weird coincidence. It was built in Ruby. But it turns out that Ruby is not great at doing things like handling, at least in 2000 and 16. It was not good at handling 10,000 simultaneous network connections, the kind of things that you need to run this big platform as a service. And so then we started selectively rewriting pieces in Go. But for the most part, there were big chunks of Cloud Foundry that today are still in Ruby. And so I ran engineering for Cloud Foundry for about four years too. And then I came to Shopify finally.
0:08:15.000 --> 0:08:20.720
Nice. Very cool. So I'm trying to do the math here. So you joined Shopify four or five years ago?
0:08:21.300 --> 0:08:27.840
It was about two and a half years ago. Oh, two and a half years ago. Two and a half years ago, yeah. I was at Pivotal for about 12 years total.
0:08:28.700 --> 0:08:29.780
Okay, got it.
0:08:30.160 --> 0:08:30.820
Really long time.
0:08:31.940 --> 0:08:51.839
Yeah, that is awesome. So Pivotal is more like targeting developers. So Shopify is more of like a B2C, or I guess it is a B2B, but it has a different sort of customer base. And so was there any shearing effect going from Pivotal to Shopify? What were the biggest differences there?
0:08:52.439 --> 0:09:48.640
So definitely the
biggest differences were, you know, Cloud Foundry. We were selling to like the Fortune 100 companies, right? We were selling to like huge financial institutions, huge retail institutions. And Shopify is selling a product to a lot of mom-and-pop store owners, especially during the pandemic. A lot of mom-and-pop store owners who no longer could open their store and wanted to get online. And Shopify was a really easy way for someone who has inventory and a store and a business model to start selling online. Like that's what Shopify is really all about. It's trying to make in the same way that like a great language will help a developer focus on the business logic that's important, right? Shopify helps a store owner focus on the business and not on the problems of accounting and how do I get connected to a payment gateway? And all, you know, if someone's not a software developer, they don't want to deal with that part of running an online store. And that's what Shopify takes care of.
0:09:49.619 --> 0:09:58.479
Got it. That makes sense. So when you joined Shopify, there must be a legacy of Ruby at Shopify for it to really pique your interest.
0:09:58.900 --> 0:11:15.560
There is. So Toby, Toby is our CEO. He's only got one name. He's like Madonna. Toby Lutka. He is an old-school Rubyist himself. And he, in fact, was one of the early collaborators on the Rails framework, which is the big web framework in the Ruby community. So he started Shopify. He was like the second person ever to use Rails, right? He and David Hansen were friends and he started using it to build Shopify. And I think he feels very strongly if you asked him. He would tell you that he feels strongly that Shopify was successful because he was able to move so quickly. He was able to get to production faster than his competitors/suppliers. And there were a couple of instances that we have an internal podcast at Shopify where he talks about this. And he said there were a couple of occasions where Shopify was close to going on a business and the fact that he was able to ship new features and get new customers in a matter of weeks made a real fundamental difference in whether Shopify was going to make it through those tough times. And since then, we've, of course, IPO'd and now we're a multi-billion dollar company. So it's all in the past. But I think he credits Ruby and Rails with a lot of Shopify's success. And so we have a very strong opinion internally that that's the default stack we use.
0:11:16.040 --> 0:12:28.150
Cool. That makes a ton of sense. Yeah, I have not a counter example, but a correlated example where we were trying to build a while ago at another company, we were trying to build a new product, a new area for the company. And because so much was done in Java, they said we'll write the whole thing in Java. And I actually, and this is a bit of my personal anecdotal opinion here, take it with a grain of salt, but I feel like Java really caused the product to slow down, the product development. And part of it was not, it wasn't just that it was in Java, but it was also that it was hooked into all these other systems that were written in all sorts of different languages. And so they all had different APIs and, oh, there isn't a Java API for this backend, so now we're all just sitting on our hands. And I think that's one of the reasons why that project just couldn't get off the ground, is that it couldn't move fast enough. So we'll definitely talk about, you mentioned several times, agility with Ruby and Rails, we'll definitely cover that, but we'll put a bookmark in it for now. And switch gears and talk to Evan. Evan, why don't you tell us what your background is and what your sort of connection is with Ruby? Sure.
0:12:28.579 --> 0:12:49.400
So my story starts in the first tech bubble, the bursting of the first tech bubble. So I graduated from college in 2002, which was uniformly known as the worst possible time to get a programming job. Like every single place was firing; no place was hiring.
0:12:49.940 --> 0:13:05.760
I remember that same time I was in undergrad. I graduated a little bit after you in 2004, and I remember my dad basically shaking his head saying, 'I told you, you should have got a math degree; you went and got a CS degree, you know, look at you now.'
0:13:06.360 --> 0:15:05.740
I mean, you were right in the end, but at that time, it was tough. So it was 2002. I had just graduated, I moved to Seattle. My then-girlfriend, now wife, and I moved to Seattle; she was starting her master's program, and I was not a great student. I had no interest in continuing with higher education. So I was like, 'I'm just going to figure it out.' And so I tried to get a job, couldn't get a job, ended up getting a job with a local ISP. It was a three-person ISP. And I basically put 802.11—not B, so pre-B standard 802.11 dishes on people's roofs for this ISP because it was a wireless ISP. And so I would spend afternoons on roofs, retirement buildings on roofs, lots of roofs. I've seen so many the roofs of Seattle. I should have started a scrapbook in retrospect—so many roofs. So I'm at this job, and I wanted to be a programmer. That was what I had done. I'd actually done open source in college. I had worked on some programming language stuff in college because it was really interesting to me, but now I didn't have any opportunity for that. But when I moved to Seattle, I was very active in a specific IRC channel from college. And one of the people in the IRC channel actually was like, 'Hey, I'm writing this really interesting thing.' And I found he was also in Seattle, coincidentally, this guy, even though we'd been talking for years. And he was like, 'Hey, I'm writing this thing, and it's in this programming language called Ruby.' And I was like, 'Huh, I'd never heard of that.' And so I went to go look at it, and it took me about a couple weeks before I was like, because I had done Perl and PHP almost exclusively, well,
and C++ and C at that point in time, but on the sort of Ruby-ish side of things, PHP and Perl. And so it took me a while to get the feel for Ruby. But once I did, I was like, 'Oh, this is great. I like this.'
0:15:05.740 --> 0:16:26.560
Lot better than the stuff that I've been doing before. It's easy to express what I want. I'm not fighting with Perl sigils, which is a little symbol you put at the beginning all the time. I liked it a lot. I ended up getting involved with Ruby and then seeing that RubyConf, which was like the Ruby conference that started in 2000. I actually missed it by a week. It was in Seattle. It was down the block from me. Didn't go because I didn't realize I literally was just like, 'Oh, yeah, Ruby, that's a cool thing.' Oh, the conference was here last week. It was pretty amusing. But I did get involved with some other Ruby people in Seattle: Ryan Davis and Eric Hodel. And we started the first—it's hard to say if it's the first, but effectively people used to call it the first Ruby User Group, Seattle RB. And it was just the three of us. We used to meet at Ryan's work and just putz around and do random talk about things. We ended up getting like I remember one time we got a review copy of the Pickaxe book, which is like the canonical, the original reference book for Ruby that Dave Thomas wrote. And we did a review of that to set Dave notes because I think Ryan knew him at the time. And anyway, so that's how it started.
0:16:27.200 --> 0:17:20.199
So you were working for this ISP, mounting dishes, Wi-Fi dishes on roofs. But you were involved in a lot of these social groups and building up this Ruby ecosystem. And yeah, that's actually a testament. I think there's so many companies talking about this looming recession. I don't know what's going to happen. Nobody really does. But something to sort of foreshadow or some foresight based on your experience is that even if the job market does contract to get difficult, there's always so much that you can do as an individual. There are so many different conventions you can go to, people you can meet, and that is going to be more and more important as we sort of go through this kind of small lull here.
0:17:20.899 --> 0:19:20.219
Yeah, I mean, recessions affect the economies of monetary policy, not people's enthusiasm or interest, right? Right. Yeah. At the time, it was impossible to get a Ruby job. Well, at the time, Ruby jobs did not exist. It was not a thing. Matt's had only begun Ruby in 1996, and it only lived on his laptop for the first couple of years anyway. So we're talking 2002-ish timeframe, maybe 2003, a little bit now. And Dave Thomas, the guy who wrote the Pickaxe book, is kind of credited with bringing Ruby to the English speaking world. Matt's is Japanese. Dave has a great story. I can't remember the exact detail, so I'll probably butcher it, but effectively, he saw Ruby—he saw some of the original documentation, he was getting into technical book publishing, and he wrote the first English version of the Pickaxe book. We call it the Pickaxe book because it has a pickaxe on the cover. And so he wrote the original version of that that basically was the only guide to Ruby that wasn't written in Japanese. And I think, so I'll fast forward a little bit, I ended up stumbling into another job accidentally working as the Windows IT administrator, which was better than putting dishes on roofs, so I went to do that. And then I, but I still wanted to be programming, and so I started just—it was a startup in Seattle. I started attending all the engineering meetings. They started; they had a meeting where they were like, 'Hey, we want to, we want to redo the back end for this thing because it's not working very well. It's really cobbled together.' We want to actually use—like, basically it was like sort of a Linux administration slash programming project. And I was like, 'I am very interested in this. If no one else has, I have actually done this before because I'd done it in college. I will, I'm happy to take this on.' And they're like, 'Sure.' I was, again, I was still the Windows IT admin. And so I was doing the Windows IT.
0:19:20.219 --> 0:19:55.600
administration, keeping the mail server up, making sure people could log in, and writing this new back end. And when I was writing this new back end, I was like, no one's—this is sort of what you were talking about earlier. Nobody was telling me anything. They just get it done. We just need a thing. And I was like, 'Great, I'm going to write it in Ruby.' Because that was way more interesting than writing it in anything else at the time. So I started writing it in Ruby. I wrote this amazing gateway so that PHP could call Ruby methods on the same machine because all the front end people were writing PHP. It was great. It was an insane system.
0:19:55.820 --> 0:19:57.040
PHP, Ruby, interop.
0:19:57.480 --> 0:21:38.427
Yeah, it's somewhere out there on the—I might not be on the internet even. Anyway, so I worked there for a while, ended up leaving a couple of years. Oh, like that, they got built up. We ended up doing a lot of Ruby at that company. I ended up leaving and then going to another small startup for about six months, basically writing a Rails app. And then in 2006—that was in 2000. That was like the beginning of 2006. In 2007, I was still living in Seattle. It's going to move down to LA. I ended up going to RailsConf that year. This is another sort of diatribe. I'll keep it short, which is I have weird programming interests. I had been writing a new version of Ruby, the programming language, the interpreter. So Ruby, as any kind of dynamic language, is just a program that reads other programs and runs them, right? It's like a chef that's running a recipe, but the program is the chef. And so I had all these interests in how to make Ruby better, and I had started writing my own version of the actual interpreter, the engine, to run Ruby programs. And I had been doing
that for a year and a half, two years at that point. And I had a thing that was interesting. I ended up giving a little talk about it at RailsConf, which is in Portland that year. I drove down from Seattle to Portland to talk about it. And the CTO of Engine Yard, which was an early Rails hosting company, saw my talk and he's like, 'I think your thing's cool.' Tom Marnini is his name, CTO. 'I think your thing is really cool. Would you be interested in coming and working for Engine Yard, and we'll let you work on this thing?' And I was like,
0:21:38.832 --> 0:21:39.820
This is the dream. That's amazing.
0:21:40.180 --> 0:22:01.620
This is the dream, right? Like someone wants to pay me to work on my open source project. So I said yes as fast as I could, and then I did that for five years. I just worked on my own—well, an open source Ruby implementation for about five years called Rubinius. And yeah, that was super intense. There are lots of stories about that.
0:22:02.280 --> 0:22:07.640
Where did Rubinius go? Like did parts of it get folded into Ruby or are folks still using it?
0:22:07.640 --> 0:23:26.560
Well, it had a lot of contributions. I would say that a big portion of the stuff that we wrote, it lives out on the internet, but it's probably not in heavy usage. Probably there are a couple of people who still use it for random things. What ended up happening was I started writing Rubinius when Ruby was at version 1.8.2. That was in 2006. And at that time, Ruby was actually moving pretty slowly in terms of the API, the functionality, all that kind of stuff. And so it made it easy if I was like somebody's trying to come in and being like, 'I want to implement this API,' which is just the program language's API. And it was about a year after that or so that the Mats and the Ruby core team really started to speed things up. And it only got faster and faster over the next couple of years. And it's hard. It's very hard to write a thing that's chasing something else, and you don't have any control over it. You're just chasing this other thing. And after about five years of working on it, I was personally like, 'I want to be more in control of my own destiny.' Like every time, like every day I was coming in and being like, 'What crazy weird API do I have to implement today that I don't want to?' And that's not fun as a job. I ended up leaving there and going to Living Social, but yeah, that was that bit.
0:23:27.460 --> 0:24:23.860
Oh, interesting. I think there's one other thing I want to throw in here while we're talking about Rubinius. Like if you look at Ruby on—like decades long time scale, one of the, I think, most important outcomes from the Rubinius project was actually Ruby Spec, which is like the specification for Ruby. It was an executable, it was tests, right? They were an executable specification for Ruby because the original Ruby interpreter, it was just like, well, it behaves how it behaves. Like it's the only Ruby interpreter. And so there were a lot of edge cases that were kind of undefined behavior. And as part of the Rubinius project, that Ruby Spec project is actually still alive and kicking today and unifies all the Ruby interpretations because there's like JRuby, which is built on the JVM and there's TruffleRuby, which is built on GraalVM, as well as Ruby and Rubinius and a few others that are all using Ruby Spec as the de facto standard for the Ruby language now. I think that that is a really important outcome as well.
0:24:24.000 --> 0:25:03.940
Yeah, that totally makes sense. I think, you know, the parallel that comes to my mind is io.js, right? So Node had some deficiencies. So I think it was maybe the original Node author—I don't actually remember the—I might be getting that wrong, but somebody wrote EO and long story short, EO and Node merged later on. And so a lot of the best parts of EO made it into Node. And so I think, yeah, it sounds like something similar that happened here where as a consequence of Rubinius, you have this specification for the language and that created, you know, a huge harmony among all these different interpreters and pushed the language forward.
0:25:04.780 --> 0:27:01.752
Yeah. One of the most interesting things, the Ruby community is a byproduct of—there's a saying in the Ruby, in the Ruby community called Minneswan, which is 'Matt's is nice, so we are nice.' And that there's a big, there's a big, it seems like a thing that people wouldn't actually say, but people, people mention it all the time. It's really part of the ethos of the Ruby community. The Ruby community has like spread its wings as it's gotten bigger in time. And I think one of the most interesting things is that this is my skewed perception, but my perception is that the Ruby community is one of the first communities that really took TDD (Test-Driven Development) to heart. It existed mostly from Kent Beck in the small talk world, but there isn't that many small talk developers. And a lot of those small talk developers ended up in Ruby or were influenced into Ruby at various times. And like, I remember TD being exposed to TDD in like 2002, 2003, when nobody was doing it. And that was a big impact on Rubinius writing Ruby spec, Brian Shirai, who was a like the second or third person to work on Rubinius with me started that specifically because it was like, 'Hey, we got to know what we're doing. We got to write some tests. We got to write specification for this thing.' And so to this day has a huge impact. So it's Ruby spec ended up being adopted into the mainline Ruby interpreter that they still write those specs. One of the big things about Rubinius was I tried to write all of, or as much of the Ruby API in Ruby itself. Right? So you could go and like look at the implementation of Array, and it would be written in Ruby. For instance, that code made its way over to TruffleRuby, which is a very specialized implementation of Ruby and has evolved since then. They have edited
it. It's—you know, it's perfectly much more owned by them at this point—but it's kind of seeded itself in different ways. Very.
0:27:02.309 --> 0:27:13.280
Cool. So after Rubinius at that point, what's the sort of link between that and RubyGems, which is what your focus is on now? What's the path there?
0:27:13.899 --> 0:28:19.664
Yeah. So I had been going—I started going to Ruby conferences in 2005, which was in San Diego. I got to watch the first release of Rails be released. They released it at RubyConf, which is just Toby and David in the front of the room releasing it. It was very interesting. So I ended up starting going to Ruby conferences then. And they were great. I was in the community. I was super interested in it. And I kind of just kept going—as my second job or whatever in this story showed, like I fall into system administration jobs fairly regularly, tasks maybe is probably the right rather than actual jobs. And in 2011, there was a thing called RubyForge, which was a hosting platform that was meant to—this is pre-GitHub. So it started pre-GitHub. It was basically a place for people to store their Ruby code, right? That was really what it was for. And it was sort of an alternative to SourceForge, which some of your audiences heard of. Some of your audiences have not. It was a sort of a precursor for where to store your code on the internet. Yeah.
0:28:20.340 --> 0:28:28.607
Yeah. SourceForge. If you've ever needed an old library and you end up clicking on 14 ads and you don't actually get the zip file of the library, that was SourceForge. That.
0:28:28.607 --> 0:30:27.940
was SourceForge. Yeah. Oh man. There's like, you could do a three-hour thing about the evolution of SourceForge as well. So there was RubyForge, which really just ran—there was a package called gforge, which was just like, you could run your own for SourceForge-like thing. And so there was a thing called a couple of Ruby developers ran a thing called RubyForge, just rubyforge.org. People would upload their things. And then in 2007 or so—I'd have to go back and check if it was 2006, seven or eight, I can't remember. A couple of Ruby developers, Chad Fowler and David Black, who were all directors at Ruby Central, which is the nonprofit that puts on the conference, started basically at a conference where like, 'We need our own like Java JAR-like thing. So let's start, let's write one.' And so they basically wrote RubyGems, took the first version—was a couple of weeks, maybe probably that first version was probably at the conference. So within a couple of days, and then they wired in the ability to start to handle RubyGems inside RubyForge. So if you uploaded a gem file to RubyForge, it would be available for you to do `gem install`. That was the first version of RubyGems. So fast forward again, back to 2011, I got wind that they were still running RubyForge. Well, I knew they were still running RubyForge and that there was only one person who was this administrator
for this whole system. And I was like, 'That's not cool. That's not fair.' And I was like, 'That's—I'm going to reach out and I'm going to say like, I'm happy to help you out run this thing.' And so I reached out just to say like, 'Do you need another hand? Another person who can basically help you on call?' Because the guy who was running it is a wonderful guy, but it was not fair to him to basically be doing this whole thing. So that's how I got involved with RubyGems originally. It was—was basically, 'I'm going to help out run.' Well, a little bit. I got involved with RubyGems software a little bit earlier than that, but the bulk of it was really the stuff we're talking about today is really helping out.
0:30:27.940 --> 0:30:32.900
run the server, debug some crazy things. And then, yeah, that was how it began.
0:30:33.700 --> 0:31:23.800
So what is it like going to a language conference? So, let's say you're a college student, you really love—I'm just going to pick a language. You really love, you really love Ruby. Maybe you've made a few commits to the sort of core, you know, Ruby interpreter or other parts of the ecosystem. But you just love programming in Ruby, you know, is like what would someone like that get out of a conference? How would you recommend getting the most out of a conference if it's your first time? What's that whole thing like? I've been to—personally, I've been to a lot of conferences, but admittedly I've never been to a programming language conference on my bucket list. But, you know, kind of describe to us all what that is like and what you're expected to—you would expect to see there and how to really have an effective time there.
0:31:24.600 --> 0:32:58.440
Let me take a whack at answering this real quick. So my strong opinion here is that there's a spectrum of conferences, and there are some conferences are small. Like I used to organize, co-organize the Gotham Ruby conference in New York City, which was one day, one track, very intimate conference. So everyone had the same shared experience. You show up, you sit next to somebody, you get to know them, you go to lunch, you come back, there were some more talks, then we'd go on a boat and have dinner. And it was great. I think that for me was my introduction to software language conference. It helps you build a local network of people. And there's usually a really great mix of introductory talks as well as some more advanced talks. And then I think, once you get comfortable and you go to one or two of those, then maybe you want to say, 'Okay, I'm going to get on a plane and I'm going to go to a bigger conference.' And maybe I go to like a three-day Ruby conference in New Orleans, which was like my big experience at my first big, huge software conference. And like, that's like a really big deal. And then the social network that you've built locally can help you there. But again, there's usually a great mix of both introductory and more advanced talks at all of these conferences. So you can kind of pick and choose which ones you're interested in and want to pay attention to. And you get to talk to the speakers afterwards. And it's as much about the social network you're building as it is about what you're learning inside any individual talk for me. I don't know, Evan, what's your experience been?
0:32:58.440 --> 0:34:57.980
Yeah, I background—I didn't give this the beginning, but like I helped run RubyConf and RailsConf for about 10 years. And so I have like there's three different styles of programming language event. They're called that: the first is a seminar. That's probably really the way to think about it. Which is basically you're going to show up, you're going to all sit in the same room. You're going to all watch the same talks. You're going to find out about interesting things that you didn't know that you were interested in, or and maybe they're going to be over your head, but then you're going to go sit with people at lunch and you're going to say, 'Can you explain this to me a little bit more? Because it seems interesting and I don't really get it.' And you're going to have some nice person's going to say like, 'I'd be happy to explain it to them.' Now you're friends. Now, when you get on the boat later on, maybe you meet their friends and that's a seminar in general, right? That doesn't even have to be programming language specific. That's how all seminars generally work, which is that everybody sees the same thing. Everybody talks about the same things. And then you all sort of bond over that and you learn, right? So when you go home, you go like, 'I found out about testing. I found out about asynchronous programming, whatever it is.' And you want to take that back with you and kind of let that percolate, figure out where it's going to come out in your day-to-day job. Second one is programming language conference, like just regular conference, which is like multi-track conference. RubyConf is an example of this. You have a lot of different—you have like three or four, two, three or four talks going on at the same time. You have to pick what you're going to go to. There's lunch, there's a keynote talk, there's that kind of thing. It's definitely a little more overwhelming. People have to figure out where do I, what do I go to? Right. And I would always—people always ask me that at those conferences. And I would say like, 'Just if you don't know what to go to, just walk into a room, just wander into one of those rooms and sit down in the back and be like,
0:34:57.980 --> 0:35:46.024
about Ruby reflection or something like that. So that's not, that's number two. Number three is sort of trade show. RailsConf kind of fits into this, this one, which is more like a trade show, which is really where you have an actual exhibit floor. You have exhibitors, you have people who are going to show you interesting things. You have sponsors, you can solve talks as well. Trade shows always have like a continuing
education, but there are a lot of places where people are looking for jobs. People are showing off their companies. People are networking. That is more of a trade show and they all have their place. They're all sort of on the level of overwhelming. Those are ratcheting up the overwhelmingness on that thing. But yeah, there's sort of those three. Those are the three kind of blends. So
0:35:46.024 --> 0:36:13.581
cool. That makes sense. Yeah. If any of your listeners are worried about whether the conference is right for them, like I would say, if you think it's for you, it is for you. And you'll be surprised when you show up and there are 200 other people that have common interests that you can chat to about. So even if you're introverted or you're shy or you're not really sure like what you're going to talk about, generally folks are going to turn up because they're interested in the same things as you. And it's usually a very welcoming experience. Yeah,
0:36:14.121 --> 0:37:35.779
definitely. You'd be surprised to if you have you might be sitting at home very introverted. But if you have a topic that's really passionate to you, you'd be amazed at how quickly you will become an extrovert when you're surrounded by other people who have the same interests. Like I saw this joke the other day where someone said when they have trouble with their CS homework, they ask a question on Stack Overflow and then they they have a second account, a dummy account where they give the wrong answer. And then that's what they need to do to get like hundreds of right answers. Yeah. So, you know, you know, it's there's there's so many things where when you dive into the details, there's you know, it comes from there's sort of different differing opinions and not really any right answer. And so you're going to come with with your opinion that you've calcified, you've spent a lot of time and energy on. You're going to find someone with a totally different opinion. And the two of you are going to have really engaging discussion. And at the end of it, you probably get to a place of even better balance than when you started. So, yeah, that was one thing I found. I was pretty introverted. I was going to a bunch of machine learning conferences, but I found when I was at the conference, then it was like, oh, yeah, I really want to explain this thing. And here's my take on it. And all of a sudden, like all these words start coming out.
0:37:35.780 --> 0:39:02.440
I wanted to say one thing, which is that you want to highlight what effectively I don't know what other people call it, but we call it the hallway track, which is the thing that happens when you're not in the sessions, but is during the conference times. It's not a lunch or whatever. Right? Because at Ruby conferences, at least the hallway track is as just as valuable as any other time that you will be there. Mike and I, I think I think our first time meeting was in Orlando outside the ballroom where we basically with
this is RubyConf 2006, I'm going to say. And it was in Orlando. It was in a hotel where we couldn't leave. Basically, it was like in kind of nowheresville in Orlando. And so we're all sort of sequestered in this hotel. But it was a nice hotel. And we all that the hallway track was amazing because there was like these U-shaped couches where there ended up there would end up being like 12 people sitting in a U shape, one of these U shapes. So on the floor, some of the couches working on things. I think I don't know if you're working on Noka Geary or H-Picot at that point in time. But and then, you know, yeah, we were we would talk like I remember debugging Web XML issues with you and Aaron at that point in time. Like, you know, does anybody know how this thing works? And someone would be like, oh, I've dealt with that before. And you kind of just do that dance. Right? And then you find that like, oh, I didn't realize that other people were also interested in this or whatever.
0:39:02.680 --> 0:39:19.206
Right. Something else I want to call out, Evan. I mean, I don't know if you have these numbers handy, but at every RailsConf or RubyConf I've been to during the initial keynote, you ask for how many people is this your first RubyConf? And like half the room raises their hand usually. Right?
0:39:19.660 --> 0:40:30.379
Yeah. So it's always half the room. It crazy as that may be, it's always half the room. I mean, I'm up on stage when I ask this question, so my perspective is a little skewed. But it's the most interesting thing that it's half the room. And I think for the audience who are listening to this and thinking like, you know, is Rails something that I like do? Are there people still picking it up? Is it is it a thing? It's very much still a thing. And there are so many people who are just learning Rails for the first time every single year. It's learned in boot camps. It's done in all kinds of different places at small scale, at large scale. And the fact that it's 50% at RailsConf is so important to me because of what it says is that the community is always changing. It's always vibrant. It's not the same 500 people who show up every single year to talk about the same thing they did last year. You know, we talk about that when we would work on the programming for, you know, the scheduling for what talks are we going to have. We always think, should we have this talk again? And I would remind people, 50% of this conference will be brand new. So you can have the same talk every single year and 50% of people would never have heard it before.
0:40:30.879 --> 0:40:45.200
Yeah, that's wild. So so you're helping the support on this. I think it was a Ruby project. And and was that was that Ruby Central or is Ruby Central something in the future? Yeah.
0:40:45.200 --> 0:42:26.502
Yeah. So Ruby Central is an actual like nonprofit set up in the United States that maintains it was set up originally actually to run the conference to run RubyConf. They needed an entity that could basically like, you know, take the insurance load, if you will, of running a conference. And that was how it started. And then after I started helping out with Ruby Forge and RubyGems.org, I was asked by the then directors of Ruby Central if I wanted to be on the board, if I wanted to help out with with Ruby Central at that point. And I was like, yeah, I do, because I want to make sure that stuff actually happens. So I yeah, I started helping out with on with RubyGems.org as a board member and then started helping out with the conferences, we almost tanked the whole thing at RailsConf 2012. That's a longer story than this podcast is available for. But I'm happy to tell it as some future junction. It's great. It has to deal with eating pot pies for three days. It's great. It's a great story. But yeah, so I started getting involved then. And Ruby Central is the entity. So Ruby Central exists. There's directors. They have staff now. They didn't have staff back then, which is why we almost tanked it. But their staff and it basically maintains and organizes the RubyConf and RailsConf is an entity that can just basically all it exists to do is is improve the Ruby language and the community. And so it is the entity that pays for RubyGems.org. It pays all those bills. It manages all of the things related to that. So it sort of is the owner of a lot of community resource. So, yeah.
0:42:26.654 --> 0:43:30.500
OK, that so there's I went to SciPyCon this year, which is, I guess, the closest thing I've been to to a language conference. But it was it was an entity and I'm totally drawing a blank on the entity that that runs it. But I had a chance to talk to some of the directors and it was it was wild. I mean, basically, they that same entity also, you know, make sure that NumPy, SciPy, Dask, all these core languages have sort of a healthy ecosystem. You know, one thing a lot of people take for granted is, you know, if you file, if you get, you know, an equivalent of like internal compiler error or internal interpreter error at Ruby and you file an issue on GitHub, someone has to be there to catch that. And it's and so that that's a huge amount of time and effort for any language. A lot of these consortiums exist to make sure that there isn't sort of a tragedy of the commons where everyone is kind of taking, but there isn't really somebody who can contribute and contribute in a really organized, focused way.
0:43:31.520 --> 0:44:45.720
Yeah. One thing I wanted to say about Ruby Central as well, because I think that this has been a misunderstanding over the years. It's fine because we didn't correct it. Ruby Central doesn't doesn't really make money like it's it's a nonprofit. It exists basically just put money back into the community. So like when we run a conference, it's really just to like pay the bills for RubyGems.org. Right? Like so we always tell people, how can I contribute to RubyGems.org? I said, like, go to one of the
conferences, buy a ticket. Right? Like there isn't prior to 2012 in RailsConf was actually run by O'Reilly, the book publisher. And so and that was run kind of O'Reilly ran it as a for profit entity. Right? Because that was what they were in. That's why they run conferences is for profit. Ruby Central took it over. We continue to run it. But we were like, hey, let's now we can tell you where this money goes. It goes. It's for you. We basically take in the money, but we basically give it back to you in the form of these community resources. So there is not some big corporate entity where, you know, they're just taking in profits to buy jets or something like that. It literally just goes in there to basically be pumped back out into the community. Yeah.
0:44:46.395 --> 0:46:05.680
totally. That makes sense. So cool. Yeah. This would be a good time maybe to talk about about Ruby at a high level. My my first interaction with Ruby was through this this software called Jekyll where you could spin up a static website, which I needed for a GitHub project. And the thing that I was really impressed with with with with Ruby and Rails was how easy it was to switch databases and things like that. So I had I had a a development version, which was using a SQLite database. And then I had a production version that was using some type of hosted. I think it's like a hosted MySQL database. And all of that back in the in when I was writing data web services in Python, I would have to build all of that from scratch. I'd have to say, OK, check some environment variable. If it's this, then use the development database. And, oh, you know, I don't have the or I don't have the MySQL library. So I have to go pull that in. It was a lot of manual effort. With Ruby on Rails, you kind of get all of that for free. That was the thing that that I really noticed. So, yeah, maybe, you know, with your with your kind of expertise, you know, what kind of separates Ruby on Rails from, you know, what kind of makes it distinct?
0:46:05.680 --> 0:48:03.660
So I like to think about Rails as being like really well vertically integrated pieces of software, right? Like you can come at building a website from like, oh, I'll pick my own like artisanal database adapter and then I'll figure out what how to render views. Then I'll figure. And what Rails did and continues to do is put together like pretty strong opinions. This is how you want to interact with the database. This is how you want to render your views. This is how you do your controller. This is how you do all of your models. And this is how you unit test all of your models. And those conventions are actually really, really liberating, I think, for as a developer. Like I like not having to think about the small details like, well, what directory do I stick this file in when I do the thing? Like you just say, I need a new model. And all of these things like self inflate for you. And I feel like over the years, other web frameworks have borrowed a lot of those same like strong conventions and opinions like Django. If you're if you're writing an app in Django, I think Django is borrowed a lot of stuff from Rails over the years. So so for me, at least again, like if you're going for I want to get something up and running on the Internet as quickly as possible. That's going to set me up to continue to add new functionality and continue at this really high velocity over time. like Rails really sets you up as a as a software developer to do all of that from day one out of the box. And if you want to color outside the lines a little bit, Rails does allow you to go ahead and configure out however however you want. And there are a lot of like really interesting plugins and alternatives for parts of Rails. But for the most part, I think vanilla Rails is a great way to run a business like this is what Shopify does. And part of what my team does is make sure that Shopify is running as vanilla a flavor of Rails as we possibly can. And if we need something special, we try to push that back upstream into open source so that everybody can benefit. And I think if you look at other companies like GitHub and Airbnb, they've made contributions
0:48:03.660 --> 0:48:25.259
back upstream to Rails over the years as well to make it a better framework. And now I'm going to like grind my open source axe for you a little bit and just be like, this is what makes open source so wonderful is that, you know, these companies that are using the software in Angular to do something real are all motivated to contribute back to keep that flywheel going of making the software great and attracting new developers to the community.
0:48:25.920 --> 0:50:19.220
Yeah, I think DHH, David Hanen, our hands, the originator of Rails, he said it a couple of times, I'll paraphrase, which is basically that having constraints helps you be more creative. And that philosophy also is true in like just how you set up your stack, right? So like having all those opinions also means that there's more constraints like, oh, I have to use this, I have to do this, I have to use this one piece. Now, yes, that basically means that like, if I don't want to do it, use it that way, maybe that's annoying. But the flip side of having those constraints and assuming that they're going to be there is that all of those things work really well in concert together. And they allow you to basically say like, okay, maybe I didn't want to spend or and you know, most people don't want to spend, you know, months trying to just figure out how to write the best SQL query. Great, you don't have to do that, you can use Active Record. And that as a part of the stack as constraint, but it also adds an incredible amount of commonality. So that as a lot of developers will know, when you move from one project to another, so you move between companies, right, you move between companies, and they're both writing web apps means almost nothing about the idea that you will
be able to pick up the new company's app, right, they could be a different language, it could be even if it's they're both JavaScript, they could be completely different, like off the wall different, right? If you move between two companies, and both of them say, hey, we're both writing Rails, you'll probably be productive on your first day at the new company, you'll probably go in and be like, okay, did you do this? Did you make this decision or this decision? Oh, you made this one? Cool, got it. And then you're often off to the races, right? And that has such power in being able to have people, you know, be productive, fulfill what they need, and also, like be expressive at the same time.
0:50:19.220 --> 0:52:18.380
I love the talk about sort of the opinionated framework and being able to build something that lasts. I think it's such a important piece. It's also a trap. I'll give kind of a quick tale of two developers. I have two buddies in college, the three of us were eating pizza and talking about video games. And the two of them both wanted to become video game developers. And I was just sitting there eating pizza. It's not my thing. But one of them said, I want to use Unity. Because even back in, I guess it was like 2005, Unity was around and it was, you know, an easy way to get started. And the other one was saying, no, I can't do this and this and this and Unity. And I can't do all these really specific things. You know, I think we should write everything from scratch, like build our own game engine, our own everything. And I actually don't know what happened to that second guy. So I don't know, maybe he made his own game engine. I don't know. But the first one actually started a game indie game studio and did really well. And so I think this trap that we fall into as creative people is we want to have the most creative medium, right? And the most creative medium is arguably like, I don't know, assembly or something, right, where you can do absolutely everything. But the problem is that actually when you're getting started is when you need to be as least creative as possible with the particular paradigm you're working on. So, you know, if you're if you've never built a website before, you should focus on having, you know, a nice end product and being able to be creative there by iterating quickly and not spend a lot of time saying, oh, how am I going to, you know, like, what if I need to use this really esoteric graph database, right? So don't worry about that stuff. Just get the thing up and running. And the opinionated thing, whether you're talking about Next or whether you're talking about Rails, it's going to put really polished ivory handcuffs on you. And in
0:52:18.380 --> 0:53:09.591
The beginning, you're going to say, 'Oh, I'm getting all these weird errors.' And, you know, oh, it's not letting me, you know, put everything in the same folder, all the source code in the same folder, because at least for Next, you know, the folder,
the directory structure determines the API. So you find all these roadblocks. But then once you've figured out how to make your thing fit in that paradigm, all of a sudden, you get all of these benefits that were outside of your conscious coherence. So all of a sudden, you realize, 'Oh, now I see how, you know, if I wanted to add a piece, I can do that without breaking everything else.' Right? So yeah, I think this is a trap I've personally have fallen into a lot as well, where I say, 'Oh, this piece of software doesn't easily let me do X. So I'm going to write my own thing.' And then sure enough, your own thing never actually gets done. So I was
0:53:10.705 --> 0:54:44.175
Just going to say, I have been through this many times. And I like the way that I like to think of programming specifically is it's an artistic tradecraft, right? Like you can just, like plumbing. You can pick up programming; you can just let you can start doing it. You can learn how to learn, learn from other people. You can read a book, you can just, you know, ask somebody, you can be an apprentice, you can do all those things. And you can be the best programmer in the world. That definition makes it a tradecraft. But so is watercolor painting. Watercolor painting is also a tradecraft; you just sit down and you start watercolor painting. You read a book, you look at how somebody did it, you just start doing it, right? Programming is somewhere between plumbing and watercolor, right? And one of the most interesting things about say watercolor is that when you decide to do that, it's so constricting. You're like, 'Oh, my gosh, I can only make colors like this; I've only got these kinds of paints; it only works on this kind of paper,' right? But think of the artistic creativity that's come out of just doing watercolors, right? The world over, right? That constraint breeds creativity in other ways that are potentially much more interesting than just being like, 'Oh, well, I need to be—I need to express myself. And so I need to spend two years making my own paper.' Great, maybe you will achieve something great. But more likely, if you sat down and just learn how to watercolor on normal paint for two years, you'd be able to express yourself potentially better than saying I need the best paper in the
0:54:44.665 --> 0:56:19.553
world. Thank you for saying that, Evan. I agree 100%. There's a wonderful article, a blog post from like 2015 by Dan McKinley, who if you all just—if your listeners Google 'choose boring technology,' you will find this essay. And he introduces this really interesting concept of innovation tokens. Like if you're building a thing, you should say, 'Okay, I have two tokens that I can use for some innovative technology; everything else I do has to be boring.' And this forces you to make the choice about where do you want to take that risk? Where do you want to spend that time—to, you know, rewrite a gaming engine or go grind your own watercolor paint color, or make your own paper? And think about what is the core competency that you're going for? Like if you as you want to start a new gaming company, that's predicated on faster frame rates, maybe you want to go build your own gaming engine. Yes. But if you want to build a gaming company built around like super fun stuff, maybe the gaming engine is a distraction. And you should use something that's standard off the shelf and put your time and effort into making the game super fun. And I think about web development the same way. Like I could write my own like socket handler from scratch, or I could just use like a load balancer off the shelf. And just, you know, there's a ton of trade-offs that you can make along the way. And people should feel free to make those trade-offs. But like 'choose boring,' where you don't actually need a competitive advantage is how I would think about it. Yeah, that
0:56:19.874 --> 0:57:22.319
makes sense. It's actually a paradox, right? Because if you can make something fit—I'm thinking about the watercolor example. You know, you see examples where people take a style that's very difficult to express in watercolor, and they or in any other medium, and they make it happen. And people really appreciate that. It's sort of like when you see these pixel art, your gigantic landscapes and pixel art and all of that. And so—you know, that could be sort of part of the challenge instead of saying, 'Well, I'm going to write everything from scratch, and that way, I can be as creative as possible.' Say, 'I'm going to make this work in this framework.' And that actually is going to force me to be as creative as possible. You know, sensibly, there's—there's, you know, Ruby is a language, Rails is a set of frameworks. But, you know, like where is sort of the gap there? Where, you know, what other things are is Ruby used for other than Rails? Like what kind of captures a lot of the Ruby market share? And how do we sort of differentiate these two things for people?
0:57:23.080 --> 0:57:37.431
Yeah, I think if we had—we're having this conversation six years ago, I would probably say DevOps was also in that group, right? So famously, Puppet and Chef are both written in Ruby. Oh,
0:57:37.431 --> 0:57:37.971
I didn't know.
0:57:37.971 --> 0:57:46.544
that. Yeah. So if you go to write Chef cookbooks, you write Ruby; if you go to write Puppet thingamabobs, I can't remember what the noun is for Puppet plans.
0:57:46.544 --> 0:57:47.640
I don't know. Yeah,
0:57:47.640 --> 0:59:20.400
you go right, you go to write Puppet Pinocchios, then you actually write them in Puppet's specific DSL. But that DSL is actually parsed in Ruby. So if you wanted to extend Puppet, do different things, you actually write Ruby on the back end. So that was big. Those things were both that were born out of this time, this interesting time in the programming community—this is like the zeitgeist of Ruby circa 2010, 2009, around that time, where people were like, 'Hey, let's
write everything in Ruby.' And so that was and DevOps was coming up and cloud was getting big. And we hadn't really hit containers yet. And that was really the era of those tools. Those tools still exist; people still use them every day. I would say that they're probably on the downslope a little bit right now, because cloud and containerization have given people different ways to solving the problems that those same things solved. And so you don't see them as used as much anymore. I think Rails is still the 800-pound gorilla in the Ruby community. I think there are other people you can write. I mean, it's Turing complete; you can certainly write other programs and people write all kinds of other services—non-Rails web services, internal services, all kinds of stuff like that—in Ruby as well. But I think that service-based applications, be it web or otherwise, are probably the lion's share of what we see in Ruby today. What do you think, Mike?
0:59:21.300 --> 1:00:19.414
Yeah, I would agree. I think there's a healthy number of people who are pushing Ruby towards being a better platform for like big data analysis, right? Like there was the big Ruby conference in Japan happened last week, Ruby Kaigi. There's been a series of talks over the last few years about like how to integrate Ruby with Apache Arrow and how to get low-latency data access and how to do OLTP and OLAP. You know, and I think that's really, really interesting because I think Python has been like the dominating language for a lot of that. And there's no reason Ruby can't be equivalent, except that like we don't have a lot of the same libraries that the Python community has invested in over the years. And so I do see, you know, some hints there of like, well, what are the interesting things that Ruby hasn't traditionally been used for—like big data—and pushing in that direction, which I which I really
1:00:20.292 --> 1:02:17.620
like. Yeah, that makes sense. There was a big effort, Swift Torch; it was this effort to do tensor processing in Swift. And that I think it was Google actually was pushing that even though Swift is an Apple thing. I think Google is really pushing this like Swift TensorFlow and Swift Torch. I don't know what happened to that. But I think there is a space for other languages to be in that domain. I think there's a lot of times you need to do tensor processing, you know, no matter where you are. So imagine if you are trying to do some analytics on—on, you know, within your web service. You're seeing a lot of this now where, you know, as the third-party cookies and other things are getting blocked, you know, people have to push the analytics to the server side. So it used to be just a bit of background used to be, you know, anytime you would—well, depending on how they set up the website—but maybe every time you click on something, you know, it would send a little packet of information over to Google that would then make its way into that company. So for example,
you're running a website for your pizza place and you want to know how many times are people clicking on your menu bar. So you would set up Google Analytics. Every time someone clicks on your menu bar, it fires a little packet of energy to Google; Google accumulates all these and sends it to you. So now if someone's using Brave or using—I think the new Safari has this, those are all blocked. So, you know, if I'm talking to, you know, PizzaHut.com, I can't actually—it won't, my browser will actually block packets going to Google if I'm supposed to be talking to Pizza Hut. And so what that does is it forces all the analytics to have to go to the backend. So that, to use this example, every time I click on the menu, I send a little packet over to Pizza Hut, and then Pizza Hut can then pass it on to Google or they could even do the analytics themselves. And so that's where I think
1:02:17.620 --> 1:02:29.160
we'll start to see more of a need to do, you know, these kinds of tensor operations and, you know, calculating distributions and these other things in Ruby, in Node, in all of these different languages.
1:02:30.220 --> 1:02:53.888
Do you so rewind your mind back to 2004? What was the piece of software that started with web that analyzed your Apache logs and basically gave you these really great graphs of like who's accessing your website from where and all that kind of stuff? Basically, it's fascinating that we're returning to that era of things. I know exactly what you're talking about. I can see the graph in my head.
1:02:53.888 --> 1:02:57.263
Yeah. Yeah. I ran that for a while for my research.
1:02:57.550 --> 1:04:52.755
Lab. Yeah. Anyway, on the topic of like, you know, what, what does, what is Ruby used for? I think that one of the things that you see over and over again in the apps, the kinds of programs that Ruby is really good at is they're largely applications that are highly dynamic. And by that, I mean that they go through heavy development cycles constantly, right? That is where Ruby and Ruby is supremely, supremely good at, and Rails makes it even better. Right? In that same way that like, for instance, if you were like, I need to write an app and I'm never going to change it and needs to be as fast as possible, Ruby ends up being kind of a weird use case because it's like, it's not really optimized for that kind of usage. Right? And then on the flip side, right. If you write, if you want to write a web little web thing, and it's going to go inside to say a Wi-Fi router, right. You might write that and see because I got to just, I got to write it one time and I needs to run in like the tiniest memory footprint possible because it's running on a little teeny MIPS chip. Right? But I'm never going to change it. So it might be awful to write the first time, but I'm never going to go back to it. And so it doesn't, I don't really care. Right? And so that spectrum of dynamism is really where you find Ruby at that far end where you're like,
'Hey, look, every day, like Mike can speak to this better than I can.' But one of the amazing things about Ruby and Rails is the number of people that you can have that are simultaneously working on the same code base and not stepping on each other's toes. That probably is the biggest feature of Ruby that Rails enables that by with convention, but it is astounding. I mean, Mike, maybe you can speak to this. What is the largest team that works on a single app inside Shopify? I
1:04:53.312 --> 1:05:49.928
Think. I mean, the big monolith that we have on any given week probably has 800 contributors to one app, to one GitHub repo, to one GitHub repository, one Rails application. Yeah. I mean, there's hundreds of PRs a day get shipped to production. How do you AB test that? We test to production. No, I'm joking. So, so I think we really embrace the fast rollback paradigm, right? It's like, we're going to be fast to ship it. And we have great observability into what's going on in production. And if something's wrong, we can roll back instantly. And so that makes the risk of failure really, really low, which means that we generally will roll forward. If something is wrong at production, we'll roll forward as often as we can. When we need to, we can, we can back out. And we do have AB testing frameworks. Don't get me wrong, but for the most part, I think we're all developing on main or pushing from main and it's managed to scale. We just have great
1:05:50.130 --> 1:05:50.924
Tooling. Wow. That's
1:05:51.497 --> 1:06:29.820
Awesome. Yeah. That is such a like, if I would have someone said, 'You got to spend money to buy a banner that basically says like why someone should use Rails.' It would probably be that it would probably be like, 'Hey, do you want to work on the same app with 800 or your friends? This is probably what you should use.' Right? Because I think if you were to try to go around and evaluate that condition amongst different languages and different places, you find all of these places where stuff falls down. Oh, well, everybody has to write to this and then that, right? The fact that that is, and I don't know that they necessarily meant that to happen, but the conditions allowed for it to be the case.
1:06:31.559 --> 1:06:53.901
That makes sense. What about scalability? So, so I mean, clearly Rails scales because look at where it's being used, but you know, how does that actually work? So is Rails is rails like sitting on a thread pool or do you spin up a bunch of copies of it on a single server? Like, like what's the scalability part like?
1:06:54.998 --> 1:08:28.367
Yeah, that's all me. So one of the things I did during Rubinius was I wrote a web server for Ruby and it was specifically to make, to make advantage of the characteristics of Rubinius. One of the characteristics of Rubinius was it had native threads available to it that could run concurrently. And so I was like, 'Okay, I need a web server that can really take advantage of that
situation.' And I coded it in a certain way that it could take advantage of it, but it used the normal API that web service called Puma. And that web server has sort of become the dominant Ruby web server today. And it uses techniques that come from Webbrick, which is the original web server framework that actually built into Ruby itself, techniques that come from Unicorn, which was a web server that was created in the 2007, eight ask era that still powers GitHub, and kind of combines a bunch of different elements in order to give people all the right knobs that they need to do things. So what generally people do is a combination of three things. They utilize a thread pool in a single process. So it's like, 'Okay, great. I know that my app's going to be blocked on talking to the database a good amount of the time. Anyway, I'm going to use a thread pool and I'm just going to basically handle requests through a thread pool.' Ruby's concurrency model is similar to Python's, and that it's you're not going to have multiple native threads running concurrently. They're going to be blocked in IO. They're going to switch control, but in root in a web app very rarely matters because a lot of times you're waiting on backend for processing and that kind of thing. Yeah.
1:08:28.502 --> 1:10:25.345
Let me just dive into that a little bit for folks at home. So, so in it sounds like there's like a global interpreter lock in Ruby, similar to Python. Yeah. So, the way these languages work, imagine you have a so using like Python or Ruby, you have an automatic garbage collection. You have all these features that are built into the language. And so it becomes really difficult if you have to handle concurrency there. So imagine you have a Python instruction that's, you know, adding a reference to an object and you have another Python instruction that is removing that reference. If they can both run at the same time, you have race conditions. And that's just one of many examples where it becomes extremely difficult. So what most languages do is they say, 'You can only execute one instruction in a process at a time.' Now, what happens is your instruction might say, you know, I'm waiting for a packet to arrive over the network. And so that you don't want all the other threads to be blocked just because this one instruction hasn't finished yet. So certain instructions can what's called release the lock where they can say, 'You know, I'm waiting on this network packet until it arrives.' Someone else can execute instructions because I know that I'm waiting for this packet and I'm not going to change the reference count on the objects, for example. And so then when this network packet arrives, then that same instruction says, 'Oh, now I'm awake again. Now I'm going to get the lock. I'm going to do some work with this packet.' And then, and then when I'm done with that instruction, now it'll go back to the machine to decide what instruction to run next. And so, you know, if
you, and so in this way, like, even though you can only execute any one instruction at a time, you can still get a ton of concurrency as long as most of the time you're releasing this lock because you're talking to a database or waiting for a network packet or something like that.
1:10:26.729 --> 1:12:10.679
Yep. Exactly. Right. So you have these three knobs, right? You have threads, which you can tune up and down basically how many requests you want to individual process to handle at the same time, basically locking and unlocking. And you have workers, which is effectively how many processes you want, right? It's going to use Unix forking in order to basically say like, 'I need more of these things.' And then all of those things aren't going to share memory so they can run truly concurrent. They can share the same socket so they can handle different things. Use this, the same technique that the Apache web server came up with back in time memoriam, right? Of like, I'm going to just have multiple processes listening on the same socket on the Unix side. Right. And so basically what I tell people is you just sit there and you just tune those knobs, right? You say like, 'Okay, great. Like I need to, I need to want to hit a certain request per second.' Okay. I'm going to turn up the threads. You know, at a certain point, turning up the threads will actually hurt your requests per second because you'll basically be handling, you'll be accepting more requests than you can actually handle in your throughput for how quickly you can get around to threads. So then you, oh yeah, that was too many. Let me turn it back down. Let me turn the workers up a little bit. Cause every time you turn workers up, you increase your memory footprint, right? So you just turn those two knobs and eventually you find a sweet spot. That's for your app. And once you find that sweet spot, then you say like, 'Okay, great. Wherever you're running your container engine, your VMs, whatever.' You say like, 'Okay, great. That's our multiplier or that's our fixed number of requests per second. Now I want to multiply it.' And then you just, you just apply a multiplier of instances. You say like, 'Okay, we got a thousand, we need to hit a thousand requests per second.' And one of our tuning can hit a hundred requests per second, let's just say. So now I need 10 of those things. Great. Let me just fire up 10 of them and you're done. You go to
1:12:10.679 --> 1:12:30.000
Lunch. Yeah. Is having multiple processes, how does that compare to running multiple pods in Kubernetes? Right? So you can, in Kubernetes, you can say, 'You know, I want four pods,' and you might get all four pods on the same machine. Is that like what efficiency loss is there between that and just running four
1:12:30.777 --> 1:14:03.140
processes? So there is an efficiency. It's not as significant, but the reason that it exists to do it natively is to take advantage of a functionality that's built into Unix operating systems, which is what people mostly deploy on called copy-on-write memory. So what you will do is you'll load your app in, right? Let's just say you have a fairly big app and it's going to load the whole app into memory. It's going to parse it, load all the objects, do all the initialization. And let's say that your footprint is 150 megabytes, right? So you loaded all that stuff in, it was 150 megabytes. So you load it into one process. And then what you do is you fork that process. So basically you make a clone of it. And what happens when you make a clone of it is that clone has its own memory. It's never going to touch the parent, but what Unix systems do is they actually don't, they delay performing the copy until the latest possible time. So if I can still read memory and it reads from the parent, and if I write to it, it will copy it. That's the copy-on-write. And so what happens is that if you, if you do that, what you get is memory efficiency by using that sort of worker model where you can fork, because you will get this shared sort of memory pool that comes from the original start and that the memory that's used by the individual worker processes will just be the memory that's required to process each individual request. So you can achieve some memory savings. And again, it kind of depends on the size of your application, what you're doing a little bit with it, that kind of thing. So.
1:14:04.280 --> 1:14:53.679
It might also be worth mentioning here. I'll give a shout out to my colleague, Jean Boussier, who has recently proposed in Ruby to have an API call that says, 'Now we are ready to do that copy and write to fork a new process, to do the copy and write thing so that the Ruby VM is now being optimized for the web context that it's running in for Rails.' Which is, which is really interesting. It's like Rails requirements making its way into Ruby. But the idea is that Ruby does as much upfront as it possibly can. And then you signal, 'Okay, now I'm ready to fork,' so that as much memory as possible won't be written to afterwards. Like that mechanism that Evan just explained, we're going to defer more and more and more of that writing or try to do it upfront if we can.
1:14:54.339 --> 1:16:14.540
Yeah, that makes sense. Yeah. I saw this really compelling—it was a blog or tutorial where someone was using ZFS, which has copy-on-write as well. And so what they were able to do is basically take their—I think it was their family photos or some something that was really large, like gigabytes and gigabytes, and basically copy it every day so they could have a snapshot. And so even though you look at this, you say, 'Oh, there's a cron job that's doing, you know, CP directory directory.' And this directory is 20 GB, and it's doing it every day. Oh my God, this can't possibly be sustainable. But under the hood ZFS is smart enough to say, 'Oh, just keep references here.' And if someone changes a file now, actually just transparently make the
copy. And so yeah, fork does something similar for memory. I've gotten burned by fork in the past. I don't remember exactly what it was, but there was something with—it had to do with CUDA and the GPU. So when you start getting into GPU memory and some of these things, you have to be careful. I know Torch now switched to using spawn instead of fork, which does make like a complete copy, a deep copy of everything. But yeah, if you're not doing crazy GPU stuff, fork is more than
1:16:14.540 --> 1:17:49.343
adequate. Yeah. I think that there are so many footguns around fork specifically because one of the other words—yeah, what are the other specific ones? And this is probably what you hit is that the semantics of fork are—let's see, it's 2022 now. So the semantics of fork are 50 years old now or so. And so there's all these efficiencies that were built into fork that aren't useful anymore, but we still pay for by paying for in the quantity of footguns that are available to you on a daily basis. And so, like the resources. So for instance, file descriptors are shared between two processes, right? So if you open a file and you fork, that other thing still has access to the same file. Yeah, that's cool. That's maybe useful. It can be very useful. It is so problematic if you don't know that it's happening in certain cases, right? Because two processes are advancing the file just the file at the same time and trending and getting parts of it and all kinds of crazy stuff. Things like semaphores and all kinds of OS related handles are copy—they're not copied. They're shared between those two. It's really just memory for the most part that is a copy. Everything else ends up being this share. And I think spawn lets you say, 'I want like a whole—I didn't want a whole fresh, a fresh new coat of paint here. Don't share any. I don't want the same cup holders as the old one. I don't want the same gas pedal,' as to say, 'I want all new stuff.' And so, yeah. Yeah.
1:17:50.355 --> 1:18:55.220
So this is a perfect time. Just remind people if you don't want to have to learn the hard way about fork versus spawn and spend days on it, like we have use Ruby on Rails—like don't build your own web service, you know, that's just one rabbit hole you'll end up having to go down. And actually, you know, if you're really interested in that level of detail, that's great. I mean, you can work on making any one of these frameworks a lot better. But chances are you'll want to at least start by doing something high level and using something like Rails. Let's jump a little bit into what you all have kind of been up to and how folks can kind of contribute and be a part of this. So, so I think, you know, if someone is super enthusiastic about Rails, you know, it sounds like Shopify and Ruby Central are both kind of places where they can go to and contribute and learn more about. Why don't you maybe talk about what are some of the opportunities out there for folks, maybe are just graduating college or maybe they're still in
1:18:55.220 --> 1:19:16.040
college? Sure. Well, I think that the first thing I would say is there are indeed Ruby and Rails jobs out there; they're in demand, and they pay well. So number one, if you're interested in doing Ruby, right, you can always, you can always reach out to Shopify or a number of other Ruby shops, which is great. There—that's my plug for Shopify hiring.
1:19:16.040 --> 1:19:22.920
What is the state with remote? And is it sort of US? Is it global?
1:19:23.691 --> 1:20:28.360
Shopify is hybrid and globally right now. So we, post-pandemic, moved into a post-office world. We don't have offices anymore. Everyone is fully remote. That was a big—it was a big step change for Shopify because Shopify had kind of built its identity around in-person offices with great perks, right? Where people could go after work and go to, go to 3D print something or play ping pong or, you know, have a great lunch with their colleagues. And the in-person experience is just not available anymore. But the flip side of that is that we can now hire amazing people anywhere they are in the world. And so teams generally find a few time zones that they are affiliated with, right? So like maybe a team chooses to be mainly East Coast US, but also work a little bit earlier to handle European colleagues or vice versa. They're on the West Coast and maybe they shift a little bit later to have some Pacific Rim colleagues in Japan or Australia. And so it's a really, really flexible place to work. And if you're interested at all, please reach out.
1:20:28.680 --> 1:20:33.160
What about internships? Are there internship opportunities for people who are still students?
1:20:33.840 --> 1:21:04.120
Yes, absolutely. So we have internships of course. And I think we also have a really great program called the Dev Degree Internship, which is for folks who are in college and need co-op opportunities. They can actually spend a few years alternating between a semester at school and a semester working at Shopify on a real team. And I think that conversion rate of that program has been huge. Like a lot of really talented folks have stuck around to take full-time jobs afterwards. And that's a great opportunity as well. It's called the Dev Degree Program.
1:21:04.120 --> 1:21:12.434
Cool. That makes sense. Just out of curiosity, Shopify, I believe it was in Canada. Is that right? Before the remote
1:21:12.872 --> 1:21:42.876
thing? It is a Canadian company at its heart. Yes. Everyone is super nice, just like all Canadians are. Shopify was founded and the main headquarters has always been in Ottawa. Got it. Ottawa is not exactly a gigantic metropolis. It's kind of—I would I would call it like a, you know, a second-tier city. It's not in New York or Chicago or in LA, but Shopify built this reputation as being the best tech employer in Ottawa. And that fueled a lot of its growth for about
1:21:43.332 --> 1:21:52.040
a decade. Wow. That is
wild. So, so is it kind of like totally remote now? Is it sense like the lease is disbanded and there isn't an office or.
1:21:52.040 --> 1:22:20.020
So, I think we still have some real estate in a few offices, but we use that for like team offsites. Essentially, we use the verb 'burst' for it because the teams come together and they like burst in happiness and productivity, but they're mainly used as like coworking sites where teams come together for three or four days to maybe finish a project, shape-up style. And there's nobody going into that office every day for work anymore.
1:22:20.020 --> 1:22:31.949
That is wild. So, the things you talked about—the 3D printing and the perks, all of that—what have you found to be sort of the best substitute for that now that everything is distributed? I mean,
1:22:32.489 --> 1:24:06.769
I think it's definitely challenging. I know a lot of folks who find they really need like that work—the social aspect of being physically together at work—to be missing. And so Shopify has done a bunch of things, I think, to try to address this. Like we do a lot of social events. So teams get together. Like my team has like a show and tell or a social thing on a Tuesday afternoon. We do coffee on Friday afternoon. We have a couple of other events that we do. And that at least gives us an opportunity to kind of get together and just chat and be social, which is great. We try to get together as often as we can, like at least a few times a year; most teams will get together in person at these offsites. Shopify also has really great perks for at home. Like we know I think new employees will get a budget to build out a home office so that they're comfortable at least if they have to, if they can't have an office to commit to, they can be comfortable at home. And I think that it's a trade-off though, right? So folks who really like—I find a lot of folks who are right out of college—their social lives become the network of people that they know from work. Like I know I did this, right? Like I married my wife who I met at work at my first job, right? I think that it is a choice that everybody has to make for themselves, whether they want to be in person now that we're kind of—I don't want to say we're past the pandemic. Cause I don't think that's true, but a lot of places have their offices open again. And I think that's a choice everybody needs to make for themselves, but I've been super happy at Shopify. I really love it.
1:24:06.780 --> 1:24:46.257
Yeah, that makes sense. So when folks do get together in person, that's gotta be a fascinating thing. I mean, I remember I recently went to a new job. I took a new job about a year ago and we're in person. But before that, there were people who I had brought onto the team maybe two years prior. And even two years later, I'd never met them in person. So, you know, getting together—it's really interesting. You kind of have to say, well, you know, here's my sort of, here's the nonverbal
side of me, you know, here's like the part of me outside of the rectangle of the Zoom call. And then also at the same time, maybe we could do something productive while we're here.
1:24:46.459 --> 1:25:26.639
Yeah. For my day job, I work for HashiCorp, which we haven't talked about here cause not really Ruby related, but we do the same thing. And I was just going to say, whenever we're also fully remote and have been for quite some time, one of the things I always have to tell people is by the way, I'm six four, just so you know, because you can't tell at all. And so the first time people meet me, they're like, Oh my God, I had no idea. I was like, I know it's because my head is well proportioned through my shoulders. So there's no way you could tell on Zoom that I'm this tall. Like, and we make this joke every single time. And yet every single time I meet people in person for the first time, they're like, you weren't kidding. And I was like, no, I was not. So I have
1:25:27.179 --> 1:25:53.453
the same thing where I have my—I think part of it too is my camera. I don't use my laptop camera because just the way my desk is set up, I would be like heavily backlit. It would look like I'm in a Witness Protection Program or something. So I got a camera and it just happens to have a pretty wide lens. So my head and my body just look small because there's so much other room. And then people meet me and I'm six two, and they're like, Oh my God, you're—you're so tall. Yeah. Yeah.
1:25:55.124 --> 1:26:15.239
Yeah. That's wild. Cool. So, yeah, I assume you can go to shopify.com/careers or /jobs. We'll put the right link up in the show notes for folks. So if you're listening at home, go to the show notes; almost any podcast app has a little notes section. And so we'll put a link in there. You can just click straight in.
1:26:15.660 --> 1:26:20.082
Cool. I didn't mean to turn that into a whole employment pitch for Shopify, but I really do love working.
1:26:20.082 --> 1:27:09.200
No, it's cool. I'm a big fan of following Shopify. There was a really interesting blog post that the CEO of Shopify made. I'll have to go back and find it, but it really struck me. It had to do with—so basically, you know, Shopify is like a true marketplace. The person was saying, you know, if you look at YouTube, YouTube sort of has this like content farms where they're creating all of this content, but then the content creators are not really connected to the ad system. That system is really the centralized YouTube thing. And so it's almost like there are kickbacks, but it's completely up to YouTube versus Shopify is like truly a marketplace. That's like sort of building up, as you said, a lot of small businesses, which is really nice to see.
1:27:09.920 --> 1:27:54.497
Yeah, that's absolutely right. I think the store owners own their own brand. They own—they have their own domain. Like maybe like the flip side of that would be like Amazon, where if you have something to sell, people are still going to amazon.com and searching. And then like Amazon gets to show competitors up against your thing too. And you know, for us, it's really is about putting the merchant front and center, allowing them to build their brand, allowing them to build an audience or customers that come back over and over again. And they—they own that; they own that asset, right? It happens to run shop on Shopify's rails app on our hardware, but they actually own that storefront themselves and all the information about their customers; they own it, not Shopify. Yeah.
1:27:55.223 --> 1:28:56.700
I happen to be looking for an e-bike for my wife, and I went to Aventon.com. They do—they sell e-bikes, and it actually is a Shopify site. And the reason why I started going directly to these companies was something kind of—you know, sometimes something small happens but ends up kind of leaving a big impact. And for me, I was searching for; I typed in Duracell batteries, and I got Amazon Basics batteries as the first choice. And for some reason that had a really big impact on me. I was thinking, wow, you know, I must be missing out on like actually the best product here, you know? So yeah, I think it's amazing platform. It's really cool stuff. If you're looking out there for internships, jobs, definitely a good place to go. And there's no physical limitation there. So you could be out in Idaho; you could be anywhere. And you should definitely reach out. What about—what about you, Evan? Like, are there folks, you know, you have hiring opportunities either at HashiCorp or through Ruby Central?
1:28:57.660 --> 1:30:08.772
Yeah. I mean, Ruby Central, I think is really small. I think that there's not a lot of positions, and I resigned as a director there a couple of months ago, so I don't have the latest either. But one of the things that I know that Ruby Central is doing right now is working with the Ruby Shield program with Shopify to take some of the funds that have been income available to hire people. So like one of the things that we're looking to do is hire people who are interested in Ruby gems and that sort of thing. And I think that effort is starting up. And I guess if someone out there listening is like, you know what, I'd really—I have this really great proposal to improve this, that, and the other thing. Yeah, there's a—we'll I'll figure out a link in the show notes to shoot over to for HashiCorp specifically. Yeah. I mean, we've been all remote since the inception. So almost a decade now; the co-founders were remote from each other or have been remote from each other for eight of those decades—eight of those 10 years or so. So we have HashiCorp.com/jobs, I believe, working on all kinds of different things. A number of Ruby jobs.
1:30:09.126 --> 1:30:18.525
As well. Cool. Yeah. I've used, um, I think Terraform and Vault are both HashiCorp projects. Yeah. I didn't realize there was a big Ruby footprint there.
1:30:18.880 --> 1:30:25.240
Yeah. Uh,
Terraform Cloud, which is our Terraform app, SAS offering is all written in Rails.
1:30:25.540 --> 1:30:40.860
Wow. Did not know that. That is what, actually, this is a bit curious. If you are going to a website, is there a telltale sign that this was written in Rails? Is there something that kind of gives it away? Like I'm trying to think like maybe it's a developer tools.
1:30:41.519 --> 1:31:42.620
Not as much anymore as everybody has moved to RESTful routes. It's harder to tell. You could probably look at maybe some of the headers to try and figure out like, Oh, this looks like the pattern that is injected by this asset management framework that's available in Rails, but that's pretty minor because everybody has sort of copied the same techniques over time. So not as much anymore. Yeah. No, people stop putting the old 'Powered by PHP' band buttons on the bottom of the footers, you know? I'm all for it. Yeah. Yeah. I love those. I love the 'Powered by,' you know, Linux powered by PHP little buttons that people put down there. So that was in the days pre, like what we're talking about at the top of the show of free cookies, cookie tracking and all that kind of thing. Those images would go into someone's log so they could find out how many people hit this thing. So I can figure out how many people are actually on this website. So.
1:31:42.620 --> 1:32:11.700
Yep. Yep. Very cool. Actually, I just kind of a random question and then we can close it out, but you talked about REST APIs. Is there a connection between Rails and OpenAPI or, you know, Swagger, or these other things? Is there a way to generate that? Is that a thing? Or like, I guess maybe the higher level question is, are people using Rails for API servers or is it really just mostly for, you know, front-end web servers?
1:32:12.480 --> 1:32:59.007
100%. People are definitely using Rails as, you know, both a full-stack website, but also just an API server, like a hundred percent. In fact, I think there's actually an option you can pass to the Rails new command, which is like `--api`. And what it'll do is it'll just optimize that installation for like a headless API only version of Rails. Shopify's big monolith is primarily a GraphQL API server for the most part, right? Cause we do a lot of React on the front end. And so the React is just hitting GraphQL APIs or REST APIs on the backend. And you find like, that's where all the complicated business logic is anyway. It's not like, it's not easier just because you're not having to render views, right? But yeah, absolutely. Rails is fantastic as an API server.
1:32:59.631 --> 1:33:16.354
Cool. That's awesome. Well, I want to give both of you some time to just kind of close it out. You know, if there's tons of folks out there, a lot of students out there who are just getting started and what kind of advice would you give them? Maybe Mike, I'll start.
1:33:18.278 --> 1:33:57.495
With you. Hmm. Stay curious. Hmm. I guess that would be my advice is every, every I think looking back on a 25-year career, all the really fun things I did were because I noticed something that was like broken or wasn't quite right. And I was like, why is that doing that? And then like you do the deep dive and you learn a little bit about your tools and you learn how things break, which teaches you how they're supposed to work, which makes you a better engineer. And usually you get like a great cocktail party story out of it at the end of it all too, where you go, you're not going to believe what I found at work today. And just stay curious. And as long as you're doing that, I think that's the best advice I can give.
1:33:57.951 --> 1:35:43.500
On. Yeah. I'll piggyback on that and push it even more. I've talked about this with other people before, but like, I'm not generally a life planner, right? Like I don't plan, I didn't plan out a career. I didn't plan out most of anything. Vacations is basically what I plan out. That's about it. And, but I feel like I've been very lucky and looking back on my luck over time. I feel like it's one of those elements where I mostly just took the thing that was most interesting that really, I trusted my gut about the thing that was most interesting to just go and say, like, 'I'm going to do that next.' That's the thing I'm going to do next. Right? I'm interested in it. So I had to have interest. So again, to Mike's point, like, be curious. Like, you know, if you think that this sounds interesting, just do a little research, look it up, like, try different things. Right? I think that you will be amazed at how those things more than, more so than even a cocktail party, you know, you'd be amazed at like, 'Oh, I looked at this thing and now it's perfectly applicable to what I'm doing every day,' or in your interview and you may say, 'Do you have an interesting story?' And you tell them the story and be like, 'That's amazing. I had the same problem.' Like those, the tech community is amazingly small, but amazingly wide in terms of breadth. Right? So like if you had some weird little thing that you did, you might find that somebody else had that same thing. And that might be your in to have a conversation with them about a job. Or if you are really interested in this thing that maybe you can't figure out how to do right now, you might just continue to cultivate that and find out that later on when there's that thing sort of appears. It might feel like luck, but really it's you making your own luck.
1:35:45.520 --> 1:37:17.400
Yeah. Really, really well said. You might even get to the point where you've only done Machine Learning. You can still talk about fork and spawn and how painful they are. Exactly. Somebody who's done Ruby. Yeah. It's amazing. A real treasure and a pleasure having you both on the show. I really appreciate it. Absolutely fascinating interview. Thank you again for your time. Thank you for having us. Oh, my pleasure. Yeah. Cool. And thank you folks out there for listening, supporting us on Patreon. It's getting close to the holiday episode. I mean, it's by the time this goes out, it'll probably be about two months away, maybe six weeks. So, but Patrick and I are already planning a pretty awesome holiday episode at the end of the year to kind of round it out. And yeah, thanks again for supporting us on Audible and sending us emails. We really appreciate all of the feedback that we get. Thanks a lot, guys. See you later. Music by Eric Barndoller. Programming Throwdown is distributed under a Creative Commons Attribution ShareAlike 2.0 license. You're free to share, copy, distribute, transmit the work, to remix, adapt the work, but you must provide attribution to Patrick and I and ShareAlike in kind.