 Welcome, okay, everybody here is from Texas, I assume, pretty much. So Texas, yeah, Texas forever, baby. I'm from Texas, but I'll get into a little bit later, like I'm not from Texas, I guess. I'm born here, raised here, went to high school, elsewhere. So is everybody ready to docker raise your react containers? Yeah. Yes. I wanted, I knew this was a single track conference, so everybody would be here, but if I had a multi-track conference, this is, this title, take this title. And you will fill an entire room. Just, people will be like, I don't know, I just know that I'm gonna, if I, if I don't go to this talk, I will be unemployable in six months. So I loved the previous two talks, I loved both of my endorse everything that I heard so far this morning. It makes me super happy that people are talking about the emotional and pragmatic aspects. Dave is a surprisingly pragmatic programmer, somebody should do something with that. I want to thank Saran for starting this hashtag. I actually follow it. I've never participated in it because I'm super shy, but I follow it most Wednesdays and sort of just look around. I get labeled as senior dev by people that I trust their opinions on stuff, but I totally, totally feel insecure about my code and about being a newbie about stuff. I started learning to program six years ago. We didn't have cool code schools and stuff like that, but I had a really amazing community of people that helped me learn and come up to speed on how to program and some very, very kind people took time out of their lives to, to pair with me and grow me as a developer and I'm anything, any success I experience as a developer is a result of a huge community of people. And so I'm super grateful that this exists. The struggle is real, like it's very scary if you're new and vulnerable. So I had a bunch of code in these slides. I mean, a ton, I had about 20 minutes of technical content I cut for this talk. So you're welcome. There's no code on any of my slides, I don't think. So yeah, we're going to talk about dockerizing or whatever, right? Actually, we're going to talk about midlife crises. A midlife crisis is complicated. Some of you have experienced it. Some of your parents have experienced it. But basically, it's you start facing your mortality and you decide to make some rash decisions. So this is my dad when he was just a shade younger than I am now. He shares my enthusiasm for fanny packs. This is not my dad, this is his brother. But it is my dad's midlife crisis car. And at school, a lot of kids used to come up to me and be like, is your dad a drug dealer? And I don't know, I don't think he was but maybe we had some sort of like breaking bad situation going on, I don't know. So I think we've gotten to where we sort of sit around and fixate on the mortality of the tools and things that we use and our current base of knowledge and that leads us to start making some rash decisions. Like hey, cool JS framework, right? The web reinvent itself every 45 seconds now. I wish it was 14 years, I live in JavaScript, it's every 14 minutes. So it's tough to think past the next framework we're supposed to learn or you become immediately permanently unemployable, right? So you've got to learn that virtual DOM. So I'm Brandon, I help run the front side. I think we're doing something kind of special there. It's a consultancy focusing primarily on these sort of front end problems and new tooling around that. We're working on a catchy slogan so that people know who we are. I'm totally open to feedback, just sort of spitballing here. So let us know. We're thinking about buying some TV ads and stuff, so we'll see how that goes. I'm gonna use the history of Rails and my experience is learning Ember, which is a client-side framework that's famous for being authored by an anthropomorphic hamster. So first, let's talk about the state of web development today and explore that a little bit. I'm gonna make some prediction for you if you are the type of person that wants to keep up with the pace of new tooling, language, frameworks. My prediction is pain. So the first pain point I wanna talk about is just keeping up part of it, right? Have you guys all webpacked your Docker file in Gulp yet? Why not? Wow, you're still using NPM2 to shrinkwrap your React? That's like so last month. All the tools, just a variety of tools out there, you just stare at it, like opening the fridge and just looking inside there and being like, I don't know, there's like a thousand things, but nothing sounds good. People talk about this stuff like you're supposed to have evaluated these thousands of options and you haven't heard of two-thirds of them. Maybe this is a problem for people like me once you get too old. I don't know. Remember it's about three and a half years old now. Other frameworks have sort of have launched and come up since then. A lot of them, actually. I wanna know in what universe could there be 24 best JavaScript frameworks? Like are any of them actually any good? Like that's the saddest thing I've ever seen. Anyway, all right, so what's your favorite technology? Just you can, we can shout it out. Elixir, whatever, I don't care, it's dead. It's already dead. According to Google Trends anyway, literally everything that you use is now unpopular and terrible. So let's take a moment to remember Rails. Node shot it down at high noon at Framework Gulch, it's a sad day. See you at the Crossroads Rails. MySQL died so long ago that only the old timers in the room are gonna remember what it was back when we still used relational databases. Ask your grandma to tell you about those sometime. That poor MySQL dolphin. My favorite front end framework got killed this year because a library showed up last year and it's time for me to pack my stuff up and move on. Tomster, no, I can still hear his little voice, please no. All right, I think everybody will remember where you were the day that you heard that Ruby had died. So, man, this conference is a bad time to reflect on that, but we can hug it out, I guess. The thing is all of this stuff is totally predictable. So predictable there's actually a chart for it. And there's a company called Gartner that gets paid a lot of money by a lot of companies to chart where these tech trends fall on this cycle every, I think every quarter or every half year. And turns out once it's gained popularity, technology is harder to get rid of than Steven Seagal's to pay. So let's take a look at this cycle through the lens of Rails' history. How many of you remember this? And let's see if I've got audio. I'm gonna try to just, please, please make sound come out. Whoops, it worked. I wanna listen to that again, it's so good. Okay, so how many people here remember this? Okay, so if you have not heard of this, please do this at some point. Please go watch the Rails build a blog in 15 minutes. It was the technology trigger. It's the thing that launched this thing into the stratosphere of programming hipster awareness. And of the people who saw it, how many people saw it at a time where you were completely blown away? All right, those people are totally old-timers. But I wasn't even a programmer yet, but yes, you just dated yourself, sorry. I wasn't a programmer yet, but the tech lead from our team brought this and showed it to me and I was like, I wanna do that for a living. That looks awesome. He's like, it's not all this easy and he made me go learn Ruby first, but that worked out really well. So this trigger is marked by hacker news commenters and tech analysts that trip over themselves to present and rank and predict the future of tools in this phase. And then it hits this thing called the peak of inflated expectations. And I don't think he gets any more inflated than this, right? Let's reflect on how this was a thing. What? Where's my magazine cover? I want that. Ruby everywhere. Again, he started with Ruby. Ruby, the enterprise, it's like, this is gonna change everything for us, right? It will fix everything, it will fix all of your problems, all your dreams will come true. And you have these thousand tutorials where everybody writes a blog post and none of them actually help you understand anything. And then you go to a conference and the talks on this technology are standing room only. And once you do figure it out, the promise of the productivity gains means you're finally gonna ship web apps ten times as fast as you used to, obviously. And that means you're finally gonna wow your boss. You get the raise, you buy the house, you'll fulfill your wildest hedonistic dreams. And we'll talk about the real promise. That's not the actual promise, but that's the one that we sort of buy into. And all these inflated expectations also tend to inflate our egos a little bit. Like anyone who came before you was totally wrong and you are the one that's totally right. And come on, you're taking this baby to the moon. Except there's only one problem. Like drinking expired soy sauce, the fun can't really last. And you hit the trough of disillusionment. If you remember how Google trends informed us our framework died and there was much weeping and wailing and gnashing of teeth. This phase is marked by prominent defectors. The thing that caused people to leave for your greener pastures is now causing them to leave for other greener pastures, go figure. So remember this, maybe you don't, hopefully, we don't have to get into this. This guy eviscerated rails and the consequences were never the same. This dude in a blog post literally offered to fight every developer reading it. It was amazing. So, rails still reeling from this like unstoppable attack left the opening for node to go in for the kill. And now rails is dead forever and none of us have jobs. So that's the amazing thing though, right? Once the super early adopters declare a tool dead, it actually starts getting to do some real work. You know technology is being put to work when it has to speak XML over non-restful end points. And this is where those blog posts are turning into book deals and a loose affiliation of enthusiasts turn into a real community. I actually like the word community. I like the idea of community. I don't think it has to necessarily equate to tribalism. And then all those enterprise dollars turn into race cars. So a little gratitude would be nice. And finally, you hit this plateau where a bunch of people become quietly productive with the technology and they don't really see the need to talk about it anymore so much. And there's nothing exciting or cool about quiet productivity. You don't get any more magazine covers. It's been a decade since my sequel died and did anything cool. But billions of dollars are pretty cool. Billion with an S, that's like multiple cool. Rails is like it's irrelevant whether rails is a good technology or bad technology because it's an entrenched and productive technology. Now you're seeing sort of the middle part of this, the early to middle part of this process again with front end frameworks. That initial spark of interest hits a few early adopters and then the hacker news crowd just like piranhas this up. And it's good attention, it's bad attention, doesn't matter because it's like off to the races. You've heard of this thing now. And then here again, being unaware of the pattern, we assume this new thing will solve all the things. This is where people new to Ember are astonished with how much work they're not doing. Does that sound familiar? And it's the hottest thing in the world for that moment in time. And it feels great, inflates your ego. And then suddenly the rocket ride is over. And it starts feeling like work. And you get your prominent defectors and the whaling and the gnashing and then what have you. And then if the tech survives that trough, some tech doesn't have the inertia to kind of pull it through or for some reason was so fixated on hitting that peak that it doesn't really survive the trough. You start seeing a light at the end of the tunnel. The tooling gets better, the learning materials get better. The community starts growing and stabilizing. And finally you get to that plateau where a bunch of people just become quietly productive and they don't really see a need to talk about it. Here's something I promise you will never see on the front page of Hacker News. Yeah, we've been quietly productive with Ember for about 18 months, it's pretty nice. Oh, that's boring, go home, there's nothing new there. So hype isn't an insult, it's just the process that we work by. These are the peaks and valleys of any successful technology if they make it out of the trough alive. And once you know this stuff, you can set yourself up for some career success, instead of being at the mercy of this cycle and feeling like you're being steered into a mountain. There are ways definitely to lose it. You can watch as your skills turn into commodities and become trivialized and devalued. You can burn yourself out trying to keep up. Or you can side with tech that isn't gonna make it. Or you can just opt out entirely and be a Fortran programmer that pays actually pretty well. So you can't be Gartner, that $7 billion is spoken for, but you could be like a trainer or a consultant during the peak. But as an individual dev, I think that if a tech doesn't crash in the trough, getting to that plateau of productivity is where the wins are. And how to win is actually sort of dependent on your personality type. And so all of this information is a little bit information overloading, we haven't really parsed through it yet, we haven't taught you how to pick the technology. But once you understand your preferences, you can focus your attention on where it's most valuable. A friend recently sent me this article that articulates a theory that I've had for a while, that there are like three predominant personality types among technologists, the pioneers, the settlers, and the town planners. Pioneers itch for the latest technology. They like floating the rivers, they like contributing, they like exploring new territory, it's all about the thrill of discovery. Settlers try to create order from the chaos that those pioneers discover. They build infrastructure, they build communities, they build the first shops and hospitals, they connect that pioneering work with real business and user needs. And finally, town planners are just trying to get things done at a scale and performance that isn't possible in those uncharted territories at first. And they're trying to take that exciting tech and turn it boring, and they always win. So let's dive back into history and see how this kind of fits together. My theory is that DHH is actually a settler who was sort of pushed into pioneering out of frustration with existing tools. I don't think many people, and certainly not him, would disagree that his ideas were lifted from true pioneering people that were exploring, like Martin Fowler or people that were pushing new ideas out into the world, and he was sort of synthesizing them. I moved to Austin from Utah a few years ago, and they love pioneers in Utah, love, love, love them. They get their own holiday on July 24th. It's bigger than the 4th of July. I think tech is similar. We love our pioneers, we raise them up and we make them heroes, and so they show up early because they like this phase. In the pre-014 beta, which was the 1.0 release candidate, Rails was strikingly similar to the look and feel of the Rails you use today. But if you tried to actually use it, you would die at a death of a billion cuts. Much less, oh, deploy it. Who here has deployed Rails pre-1.0? Okay, and the reason that you don't see more is they literally died. Quick aside, we had Rails, we couldn't figure out how to deploy it anywhere, so this was late 2005, early 2006, and we had a Rails app sitting on a box underneath Rusty's desk, Rusty our venerable lead developer, and next to it was another box that had our billing server on it, and you would know that Rusty had accidentally kicked the billing server because our customers would call and say they just got billed 14 times. So these days were not good. But then the settlers arrive and they're like, that's insane, you cannot do that. People need guides, they need infrastructure, they need books, they need supporting libraries, deploy tools, hosting services. The settlers are all too happy to look at those as opportunities to help and to build and grow businesses. Back in, if you were doing Rails back in, you know, 1.0 to 2.3 era, you might've had nine gems starting with access, and I think we owe a huge debt of gratitude to Ryan Bates for starting Railscast back then. Heroku and Slicehost got their starts around this time. And then, interestingly, around three, Rails was created to fight these architecture astronauts that had set up shop and fragmented Java's web culture, but as the needs grow more complex, architectures had to respond. And the much-revolved computer science folks take over some of the development of much of Rails, bringing modularity, relational algebra, like I don't even know what that is, that sounds awesome. The big money starts moving in at this point and the Rails tent has to get bigger. And suddenly you have things all the way from code schools to enterprise names being covered by this technology. Now, I had no intention of becoming a historian, but the actual history on this stuff is pretty scarce. I'd love to, again, if anybody here has, remember stuff or wants to talk about it, hit me up after, I'd love to buy you lunch and talk about this stuff. All right, so let's see how these three archetypes play out in a successful community. Everybody actually has all three of these personality types in this big, soupy mess internally. And so it's an oversimplification to say you're one or the other. But I think one of them is usually dominant. So let's pick what irritates you. Is it most irritating to be required to use outdated stuff? Is it more irritating when your team members come in and they're like, I wanna build it, I'm not gonna name any names. Some invented framework and language and the back end and the front end and the middle end that they just invented. And or is anything that gets in the way of shipping at all, like, look, just let me do my job. Do you like merging pull requests? Or do you like applying a technology in a way that makes your company real actual money? Or do you like solving the trickiest performance problems? Where do you feel the most helpful? Do you like extracting shareable libraries from your side projects you're doing? Do you prefer improving somebody else's documentation? Or do you like automating some tedious deploy process and make the other developers 10 times more productive? Each of those is really valuable, but if you find yourself siding with the first answer, you might be a pioneer. More on the second answer, you might be a settler and on the third, you might be a town planner. All of those roles are important. Pioneers do the experimentation and they help define a sense of what the future could look like. Settlers connect that with real problems and opportunities and town planners help scale and help that grow to large numbers of people. So settlers and town planners might call pioneers hipsters that are swept around by fad technologies and call them millennials or whatever. And pioneers often get mad at settlers for exploiting their work for notoriety or commercial gain. And town planners get called out for lacking a sense of adventure and being architecture astronauts. When they're just trying to make things stable and scalable and predictable. So as humans, we're wired to be dismissive of those that don't share our default opinions. Her react was good. So we take on each of these roles at different points, but it's to our advantage to lean on what we're best at. Me, personally, I'm totally a settler, absolutely. Like solidly in the settler camp is a default. And which is, you know, doesn't necessarily mean I'm a sociopath. So let's jump though. Like, okay, what am I supposed to do with any of this stuff? Like, great, thanks. You've given me my cosmopolitan quiz. Well, let's map that out in the cycle, in the hype cycle for your personality type. And you simply just can't get wrapped up in trying all of these new technologies that comes out. There's 12,000 of them. 13 million Google results. I'll wait for one of you to, maybe we can divide and conquer and get through all of them today. You just can't, right? So when you feel obligated though to check something out, you just need to be able to answer these couple of questions. What stage is it in? Should I concern myself with it? And based on your type, you can kind of know whether it's okay to avoid something or if it's time to start looking at it. Pioneers are best served though by grabbing new interesting things as soon as they come out and become interesting to them. Settlers can kind of hang back and just watch and planners can completely ignore it. At the peak of inflated expectations where the magazine covers are happening and all that stuff is happening, it's time for the pioneers to shine. This is like, they get to train, they get to consult, they can write blog posts, they can become core team members. There's lots of opportunity for both community contribution and exploiting it for commercial gain, tons. Settlers can exercise skepticism but they do need to keep an open mind and town planners can just keep their head down and keep shipping with the tools they know. Now, once a tool hits the trough and you start seeing prominent defectors and all that stuff and you see the signals of a trough of disillusionment, the pioneers can exit the ride. They have made all of the changes and progress that they can. They can change roles to become a settler and stick it out but they have to recognize that their role has actively changed. You are no longer a pioneer of this technology, it has caught on and other people are grabbing it. Now is the time for settlers though to step in, learn that technology, make a judgment as to whether it's gonna survive and be valuable and town planners can glance up from their desk or go back to work. Pioneers at this point are totally done. They're out of the picture. The technology is climbing the slope of enlightenment because the enterprising settlers have written books, they're establishing consultancies, they're building products, they're creating a support infrastructure for this thing. The town planners need to start running through some of the new tutorials that are coming out. So even if you're a town planner and you're really productive in what you're doing, this is the time where you need to start exploring one or two of the new things that are coming out. In the plateau, settlers can apply the now low-risk tech to novel business problems. Town planners can help automate and improve performance and create enterprise-scale solutions. The toy solution, this used to be a toy, right? But now it's running Fortune 500 companies and it's running your bank transactions. Okay, so what about leaving? What about getting stuck in a rut? You might be wondering when it's time to get off that plateau. But the good news is, if you're doing little bits of exploration according to what your personality type is, you never leave anything. It's like Dave was talking earlier, he still loves Ruby, he's just doing something else. You wind up finding yourself working toward a different plateau with a different stack when you have a different kind of problem. There's no big dramatic exit. There's no blog posts while you left X and you never hit hacker news front page. I'm sorry. So in summary, if you wanna turn this cycle to your advantage, you have some pretty simple prescriptions based on your own preferences. If you're early, help people reduce the risk of exploring the new technology. If you're in the middle, find novel ways to connect it with business problems. And if you're late, scale and automate and take advantage of the fact that it's commoditizing. There's one warning in all of this, and this eliminates maybe 11,997 of 12,000 frameworks. There are technologies that bet the farm on maximizing that big peak and hoping that that carries them through the rest of the way. And it never works, unless, unless you're trying to raise a bunch of VC cash and disappear and you wind up in like Cabo San Lucas. That could be a plan. You can figure that out. You wanna look for tech that has a vision that carries you all the way to the plateau. Here's some warning signs. Any tech that says it's sitting at the intersection of popular framework X and new language Y, that is a deal breaker. A slight variation is a modular alternative to a popular framework. Just look at it if it trades on the popularity of something else, that is a deal breaker. A five kilobyte micro framework that, you know what, I'm gonna stop you right there, shut it down, deal breaker. These pitches are not speaking to any sort of eventual gain in productivity. They're appealing to the peak of the hype cycle. So with that in mind, let's say you're investigating front end frameworks. There are already people who will help you evaluate for specific criteria. So let's, we'll stay back and analyze it from a more philosophical perspective. So your instincts are actually probably pretty good. Most people in here, no matter how long you've been a developer, you probably know when something is like sort of fishy. So you should be able to aggressively prune that list and filter out peak seeking missiles and you'll be left with a few front runners, which is great. From that point, any of the frameworks that you're probably familiar with can be used to fit any of the needs. That's just straight up true. This is gonna wind up being sort of personal preference. You'll have an easier time if you play to the strengths of the various frameworks. Backbone is solidly at the plateau of productivity. If you've got a bowl of jQuery spaghetti and you can't truly refactor it into a framework, Backbone has you covered. Ember is pulling out of the trough of disillusionment and starting the up the slope of enlightenment. If you wanna build a native web application from scratch against the API, it's got rails like tooling to get quickly up and running. If you wanna add a drop of functionality to server rendered pages and keep the mental model really simple, React is totally your tool. There's also a third party router and it's got a growing community. It can do most of the stuff the other framework can do. React is absolutely at its frothy peak. I went to a front-end conference called Fluent this year and the React talk was like packed standing room only and it's a serious contender though. It can back up the hype and it's actually had a big impact on the other frameworks already. And let's be honest, you're already using Angular. It's entered the trough around the time they announced 2.0 but it's pulling up the slope as well. It's similar in terms of its place on the path as Ember but it's already in your code base. So if you've got it, there's no reason not to use it. In terms of capability, the frameworks all seem to be converging on using components and a router to tie them together. Now in terms of your personal type, Backbone is pretty appealing for town planner types because you just need some organization around the code that you were gonna write anyway. Ember is perfect for settlers that wanna leverage a community of people to build native web applications and not have to write all that code themselves or write boilerplate code or maintaining a stack of build tools. Some people find that very appealing and I will never understand that. React is just exiting the phase where it's targeted at pioneers. It has several ideas that are so wacky that they totally worked. It actually turned out to be really good and everybody hated him at first and it turns out my business partner calls it their haggis technologies which he says they looks terrible, sounds terrible and it's actually very delicious but I won't know because I will never try haggis. Angler is great for settlers and town planners. It's a pretty simple model of supercharging your HTML by giving it dynamic new primitives backed by data and two-way binding and with 2.0 it's showing a lot of similarity to Ember. There's a lot of cooperation happening between the frameworks right now so watch for the ones that are converging because that's really nice. React is wonderful. Angular and Ember are wonderful. This sounds like a tough thing to evaluate for community but really after interacting on Twitter or whatever with some community members or visiting a couple of meetups you should be able to answer a very simple question. What are your nicest, smartest friends using? I think the Ember community in town is absolutely stellar. It's second to none. I invite you to check out the meetup sometime, Ember ATX. They're also look around for Angular or React meetups but for heaven's sake please, please no. Just don't do this. Let's write our own. Or maybe you're the world's itchiest pioneer and you gotta do it and just get it out of your system, it's fine. So great, you pick the tool, it targets the plateau and now you even have a fun toy app built on top of it. So you finish the tutorial, you have this not quite ready for a production app. It's working. You know that feeling, right? I got this. And then you're like, okay, let's put it in production. Ah, crap. You gotta come back down. So this is my friend Jameson. He's a very clever, cool, funny dude and he's pointing out like we buy into that peak of inflated expectations. It is okay, it happens. I just need to take a moment with this. This is like, basically the only thing is to open up Hacker News and pick whatever the most outposts. We've had some trouble with reliability lately which is why it's time to rewrite everything in Checks Hacker News failed Kickstarter projects. Just sub in whatever is on there that day. The reason is it's expectations, right? How many people here by show of hands have written a proof of concept that got put into production? Okay. So I look forward to the day this happens to you if it hasn't yet, because it will, unless you have iron, iron will. It takes like six months or more to actually get it production ready. And you're like, yo, this is the same piece of software. What's going on? Maybe that's what they mean by a 10x programmer. It's 100% me. Maybe the problem is your boss thinks the proof of concept is production and the expectations get inflated because at the beginning you demonstrate this incredible velocity with this new tooling and people expect that output forever. Like hurry up, we need the feature. What's the holdup? And all you can think is, wow, this worked so fast. It worked so well earlier. And it's like this personal exploration of tech follows the same curve. You made it to the other side with Rails. You've made it to the other side with one or two other pieces of technologies. Why would you do this again? Why wade to the trough of disillusionment? Well, even if you're a pioneer, you have to see a new technology to your own personal plateau. Clearly you pick the technology for a reason. It's curiosity, intuition, a problem you have to solve, whatever. The pain is higher, it takes longer, so why in the world are you sticking this out? But I want to talk about something that's happening in our industry that may be difficult to notice if you're right in the middle of it. Ponder this for a second. The way our whole industry works has flipped upside down in the last few years. It used to be you take your technology and bring products to market with it and now people are bringing product demands and we're making technologies to make that happen. And we've been swimming in this avalanche and we didn't realize the fundamental shift that has occurred. User experience is driving the technology choices we make now. So we need tools to manage the complexities of this new UX-driven architecture. Sorry, client-driven UX is a thing. Deal with it. Um, Ember is a mature and robust answer to this. Angular is a mature and robust answer to this. React is a mature in robust answer to this. And there are other tools out there and there will be more. So if you've been doing this long enough to remember selling the idea of installing JQuery into your app, does that sound familiar? Now that sounds completely bonkers. But it used to be something you had to fight for. That's where I believe client-side UX is headed. So Ember across this chasm, other technologies have crossed this chasm. Sometimes it really is time to bail out in a technology. Like it's just not going anywhere, it's not solving the problem. Like Dave said, it's like your code will push back. But if we're not careful, that process of bailing and moving to something new and new and new can trigger this eternal mid-career crisis. And if you notice this pattern in your work life, where you're like, I got it, I got it. Oh, wait, I got it, I got it. Oh, hey, I got it. Oh, hang on. Maybe check if you're getting to any kind of plateau or if you're actually getting close to your goals. The tools that have staying power, like Ember and like Angular, tend to push through that thing where they optimize for that first hacker news comment and that first 15 minutes of productivity buzz toward long-term plateau. I want so badly to ship stuff. I just want to ship stuff and make my users happy. And I thought Rails and then Ember would free me from all of the hard parts of doing that. And that's not true or it's not even possible. But I did buy into it because that's a cycle. But that is not the promise. The real promise is about helping you reach that plateau, your own personal plateau. And on the plateau, you have time to focus. You focus on things that had value. Business value. Serious business value. These people have added a lot of business value so they're gonna continue celebrating for some time. Like a lot of business value happened here. On the plateau, you have time to think. And you start thinking, you're like, okay, I'm thinking. And you start thinking, maybe my boss is an idiot. I'm not saying it's true, I'm just saying you have time to think about it. And since you focus on business value, you can afford to fire your boss. And then you do. And you turn out all right. And you get to have your own midlife crisis the way that you wanna have it. But that's another talk. And that's it till the next episode. Thank you.