1010: No One Cares Anymore?  🔗 **Source:** [1010: No One Cares Anymore?](https://share.snipd.com/episode/2e13f554-f949-4407-8b08-56c209112391) ## Highlights - **Front End Requires Deep Fundamentals** - Front-end now demands far more breadth than just React: performance, accessibility, UX, HTML/CSS fundamentals and cross-browser compatibility matter. - Wes traces the skills gap to the post-React bootcamp boom where many grads learned only React basics without deep web fundamentals. Transcript: Scott Tolinski Right so let's get into the first question here it's from way why is it so hard to find good front-end devs my company is hiring but everyone i interview doesn't know the difference between Png and jpeg or what the purpose of a bundler is. It feels like everyone out there just knows a little bit of React and has very little in the way of web fundamentals. My gosh, yeah. Frontend is hard. Oftentimes, I feel like frontend is looked down upon in a weird way, whether that is because people don't like CSS or HTML, or they don't feel like it's difficult when I arguably I think I mean, front end's gotten like crazy in terms of breadth of things you have to understand. But also you have UX considerations, you have to have accessibility considerations. There's just so much is there speed, performance, all kinds of stuff. And anybody who has been part of this industry kind of pre the React boom and stuff like that would know that you used to work on front ends and all this stuff. And then all of a sudden, developers became really in demand. And what happened? A thousand in one boot camps sprung up where all they teach you is here's how to make site with React. Okay, we do a create React app, we make things click, we make things open. Here's maybe a little bit of CSS, here's to install things. That's the front end to some of these folks. So there was a huge boom of boot camp graduates who really didn't ever have that full experience of working on real projects that really matter with the team over the course of time when Web fundamentals weren't just something that you, something that would be nice to have. It was like something that you had to have to make anything that worked across browsers and actually was shippable, right? So, Wei, I think it's really just that you need to keep looking. ([Time 0:01:06](https://share.snipd.com/snip/fc9d0772-c629-4213-93c1-e5a4ee10f1b9)) - **Make Pages Editable For Quick Fixes** - document.designMode and contenteditable let you make an entire page editable instantly, useful for quick edits or customer-facing tweaks. - Wes uses contenteditable for invoices so customers can self-edit VAT numbers and addresses, eliminating repetitive support emails. Transcript: Wes Bos Next question from Humongous, good name, design mode. It's a weird property I never see used, but seems like it could be useful. Why was it added to the spec? What's the problem? What problem was it solving? Does it serve a purpose today or is it some vestigial artifact of the old web so design mode is essentially if you type document.design mode equals true it essentially just makes the Whole dom content editable and every every six months somebody figures this out it's a really good tweet If you want a tweet to go viral, because it's like, what? The browser has this thing where you can just turn it on. And then when the whole document is content edible, literally every text node, you can just click on it and type and delete and whatever. And then under the hood, what it's actually doing is it's modifying, it's adding and removing the HTML and the text and the text nodes. So it's no different than just doing a content edible on the entire html document so like like why is it there um the content edible was are you eating that i'm sorry i have to stop you are You eating uh the web here content edible content editable uh it it was added i think it was added to the browser with the hopes of like we would have this like gui where you can just like Make this really rich text interface and you can just click into it and type in and what you want um and and the is that like WYSIWYGs are extremely hard. We've seen many, many WYSIWYGs over the years of like, how do you make something where people can simply just click where they want and type and drag and drop and resize and all of this Stuff? How do you make that, but like make it like manageable and like still, still nice on the, on the backend. And we've seen many people try and fail and it's, it's not something I ever wish on myself. So I think the idea with adding it was that we would have this beautiful GUI. And I don't think we've really seen that pop up. Anybody who's doing it has to implement a whole extra layer on top of it. But why do we have it? I don't know. It's useful in many cases where if you just want to simply modify a web page, if you're taking a screenshot, if you want to do something, just pop content editable on the same thing and It'll rip. Another thing is like I have like invoices and receipts when people buy a course from me and what always happens is somebody says can you add this VAT number to it can you change the name Of it I put the old address in it like I'm not going to get it approved it's all it had so much just busy work of people saying my invoice doesn't have the right information on it so you know What what I did? I slapped the content editable on that thing and said, change it yourself. Yes. Whatever you need to do to get your boss to be happy with your invoice, go ahead and add it. And that stopped all those emails from coming in. ([Time 0:05:11](https://share.snipd.com/snip/94d06e49-c872-4008-836c-684636dad856)) - **Enforce Standards With Concrete Evidence** - Do push for concrete standards and automated enforcement like linting and blocked PRs to raise code quality across a startup team. - Scott recommends framing changes as ways to reduce customer complaints, showing specific failures and clear, smaller fixes to get buy-in. Transcript: Scott Tolinski My current organization is full of developers who don't care about the platform or code quality. They make no architectural decisions and just keep pushing code that isn't well thought out, well tested or even looks good. Hey, your coworkers might just be an AI because this is sounding a whole hell of a lot like an AI to me. Management talks about customer complaints and the need for better code, but the senior engineers don't care either. They write poor code themselves. For context, we a startup with about 50 developers. 50. That's, yes. That's not the worst part. Another senior developer and I actually care about engineering quality and we've tried to drive a lot of improvements, but they keep getting pushed back. The team always finds faults with our suggestions or comes up with vague reasons not to support us. A lot of opinions I hear don't hold up. For example, they insist on writing end-to tests for every small thing we ship. I've explained why integration tests would be more effective and that end-to tests are slow, costly, flaky, and a lot of the times won't scale. I even shared articles from Kent C. Dodds, but they won't listen to feedback. The hard part is that the product is gaining real traction and growing fast. I don't want to walk away from a high growth company, but this people problem is genuinely stressing me out and holding back my growth. I want you to consider something here. I want to work with people who genuinely care. I want you to consider something. You might not be right on everything. I'm just going to throw that. I'm not saying you aren't, but you might not be right about everything as much as you think you are. Personally, I prefer end-to tests for everything. Me, I prefer end-to tests for everything. And other people might too. Sure, costly, timely, those types of things. Potentially flaky, yes. All of those things, all of the above. But man, I got a lot more value out of end-to tests than I do anything else. Wes Bos Can you explain the difference for the audience, the difference between an integration test and an end-to test? Scott Tolinski Yeah, an integration test tests exactly what the name suggests. It tests how things integrate with one another, so systems and how they integrate, where a unit test tests one single unit, like a small unit, like a function. An integration test is more or less testing the pieces and how they fit together, where end-to tests is testing as a real user using the app. So many times, especially on the web, end to end tests are done via some with something like Playwright or Cypress, which I haven't heard of Cypress in a while now. I know people probably use Cypress still. Most people have landed on Playwright. But what those are doing is it's writing the test code is running your app in a browser and clicking around and using it like a user would so therefore it's kind of the ultimate integration Test because it's the whole system integrated in my mind it's one step away from having like a guy that just checks it for you yeah so that was the red flag for me that was like maybe they Do have good reasons for things. Now, I genuinely know what it's like to work with coworkers who don't care as much as you or have pushing poor projects out. Or in my case, it was oftentimes they don't have the pixel attention to detail that I had. So I would see coworkers push out a client site and I would just be like, oh, you didn't even do this. Like, you didn't even check this. And that was like frustrating for me to be in that. And those were like agency projects. So it's like, OK, those those those things are gone the next week or whatever. I don't have to think about it's not a big old project that everyone's going to have to work in. I think the biggest thing that your team needs to get on the page with is a set of standards and hard enforcement, things that robots can do to tell you what the problems are, like linting Stuff or hard guidelines, things that block code of a certain type for making it into the repo. But this problem will not ever fix without the management, the engineering management, taking control or even believing that it is a problem. So one, I want you to consider that other people might have valid opinions. Two, I want you to talk in a non-aggressive way, a non-judgmental way to your engineering manager and express some of your concerns. That's tough for a lot of people, especially people with coding egos. I know best, I'm doing it this way. They're not doing it the right way. This isn't a, they're doing it wrong, you're doing it wrong. It's a, hey, I've noticed these things in our project and I have some concerns for these things. Do you think it's worthwhile for us to establish some guideline practices and enforce them in some kind of concrete way? Wes Bos You're probably stomping in being like, we should do things X, Y, and Z way. And they're having a hard time caring. And if you ask yourself, why don't they care? It's probably because fast growing startup. Everybody's got a lot on their plate. Everybody's always busy. And they don't want some little wiener coming in and telling them, we should be doing things differently. We have to change how it is because you have to just say, okay, well, now we have to figure out this new way of doing things. And now I can't ship as much code because I'm trying to figure this out. Now you're breaking things and maybe it doesn't work as well. That's extremely frustrating. So what you need to do is to just simply like this is so much easier with AI is just like go spend some time figuring out how you can fix it and then just bring it to them. Bring the problems that you have. Be like, hey, customers are complaining about X, Y and Z. Here are three times when we drop the ball and it made us lose money or customers or whatever. And then here, here's my here's my And this is why it's going to be easier, right? It's not going to be harder. You're not going to have to learn a whole bunch of new stuff. It's simply just going to be easier. It's going to be faster. It's going to be better in every regard. And if you can do that rather than complaining and rather than trying to be a drag on their energy, but you can sort of energize and move them along. ([Time 0:10:37](https://share.snipd.com/snip/022279e3-f97f-4804-9ddf-7bca44723f9d)) - **Match Tests To The Failure Mode** - Use the right test level for the problem: unit tests for small functions, integration tests for subsystems, and end-to-end tests to validate user flows. - Scott explains end-to-end tests (Playwright/Cypress) run the app in a browser and catch real user regressions but are slower and costlier. Transcript: Wes Bos An integration test and an end-to test? Scott Tolinski Yeah, an integration test tests exactly what the name suggests. It tests how things integrate with one another, so systems and how they integrate, where a unit test tests one single unit, like a small unit, like a function. An integration test is more or less testing the pieces and how they fit together, where end-to tests is testing as a real user using the app. So many times, especially on the web, end to end tests are done via some with something like Playwright or Cypress, which I haven't heard of Cypress in a while now. I know people probably use Cypress still. Most people have landed on Playwright. But what those are doing is it's writing the test code is running your app in a browser and clicking around and using it like a user would so therefore it's kind of the ultimate integration Test because it's the whole system integrated in my mind it's one step away from having like a guy that just checks it for you yeah so that was the red flag for me that was like maybe they Do have good reasons for things. Now, I genuinely ([Time 0:12:40](https://share.snipd.com/snip/247f557b-0c3b-4d22-8df3-368a3eb73205)) - **Consolidate Duplicate Animation Libraries** - Consolidate duplicate animation libraries when feasible to reduce payload and inconsistency; audit pages that load both and convert usages. - Wes suggests using AI to list GSAP usages then plan migrating them to Framer Motion for consistency. Transcript: Wes Bos Says i inherited a code base that historically has used motion for encode animations motion is really cool motion.dev um but recently looks like they also added G sap. Um, is it reasonable to keep both or should I make an attempt to consolidate to just one? What should I look at to determine which one may be better? There are some recent animations that also use three JS, uh, as well. If that's a factor, the three JS stuff probably is, is totally separate bag of worms because... Bag of worms, yeah. You know, that's a different bag of worms. I would probably leave that out of it. That's probably more 3D stuff. Although, I don't know, it depends on what kind of animations they are. Maybe they can be converted. I certainly would move them into a single library. It depends on how many and if it's going to be worth it. But if you've got pages where you're loading both libraries on there, the animations probably don't feel very consistent either. I'm a big fan of both of these. I would probably look at the motion has been like cranking lately and I'm very I love everything that they've been putting out both in terms of like their defaults but also the library The the UX behind all of that and I don't think there's any better time to to do a refactor with all the AI we have right now being like like if you're on two weird things you can just ask the Little robot to go through your code base and find a list of every single thing that is written in GSAP and figure out a plan to move each of those over to motion. I think that's a very easy thing to do. ([Time 0:18:12](https://share.snipd.com/snip/23167698-b43a-4621-a749-01cdbfef1de8)) - **Watch Interview Code For Malicious Hooks** - Scott and Wes called out a real interview scam where an NPM challenge contained a malicious postinstall hook that would steal crypto. - They recommend scanning any code before npm install and using LLMs like Claude to spot red flags in challenge repos or archive links. Transcript: Wes Bos Charles says, not a question, just a thanks. In a recent potluck, you talked about interview threats. Opened a code and challenge this sunday evening and immediately saw the red flag so let me pause for a second we were talking about how uh adib hana he went through some interview and they Sent him like a thing to npm install and he's he paused for a second and ran it through clawed and realized there was like a post install malicious hook that would have like totally nuked His computer and stolen all of his crypto and did all these awful things. And we mentioned it a couple episodes ago. Saying thanks because I opened up a coding challenge this Sunday evening, immediately saw the red flags, Google Drive, Zip Link, API key, weird API key, follow up email, strange spelling And formatting. I hope I would have noticed before your episodes, but I never know. Thanks. So, man, you got to think like the scammers can get the like weird spelling figured out by now, you know, all the technology we have if the fact that your your english is broken and not very Good like that that's the dead giveaway like even at century we do these like phishing email things where we have training yeah training to like learn how to detect the phishing email And it's often like if it's written in poor english and like i i it's almost the opposite now and now if something is way too polished that sets off my red flags and thinking oh someone someone Ran this through an llm so good and people still don't see that the m dash is our dead giveaway oh the m dash is the the least of the words i just see it in absolutely everything now you know Scott Tolinski It's not i know i'm just saying like an ai tells it is crazy that everyone knows that it's an ai tell yet i still get things with m dashes 24 7 i don't know if everybody does like i think we're Wes Bos We're in it i went to a a fair the other day in our cottage, small town, and they have all these different vendors and they're selling stuff or their signs and stuff. And man, oh man, have they found out about ChatGPT, man. All of them, all the signs, all the logos of all these things, all of the write-ups of these. It's unbelievable how much it has shook small town. Not necessarily small town, but it certainly has reached the outer non-technical group. And it's the greatest thing to them. Because remember when we first figured out about it and you go, whoa, it's outputting. You know how exciting that was initially? And then you get jaded and realize all these things. Yes, I know. But good. Jay, if you guys are interviewing, certainly before you NPM install or run any code in like a test that they give you for an interview, just give it a quick scan, run it through Claude, Something like that, because it seems like this is going around. ([Time 0:22:38](https://share.snipd.com/snip/23c11a43-0a88-44d1-9a95-8ccbae62511c)) - **Learn By Scanning Then Hitting Edges** - Learn by surface scanning then go deep on a few areas that excite you; pick projects that force you into edge cases. - Scott and Wes recommend becoming your company's in-house expert (for example on LLM/harness tooling) and run demos or lunch-and-learns. Transcript: Scott Tolinski Hey, guys. Thanks for the awesome show. You really helped me stay up to date on the latest and greatest trends in JavaScript and LLM technology. Currently, I am a mid-level software engineer at a large enterprise company and I'd like some advice on leveling up. Most days, I'm trying to be efficient and productive with my time. Deadlines make it difficult to focus on learning while working. All too often, I feel like a code monkey. Oh, I remember that term. I used to work at a place that had a code monkey room. That was like, you could just go and work free form out of the code monkey room. Thankfully, I'm not using LLMs as a crutch. I try to spend at least 30 learning something new every day. How can I learn the deep or core knowledge of software or web tech that will make me indispensable in my career? What would you recommend building courses, reading docs, all of the above? Now this one is tough because there are different answers here. So if you're focusing primarily on what will make you indispensable in the future, then your best bet is to stay on top of all of the latest AI stuff. Honestly, the the techniques, the skills, the stuff that other people might not be getting deep into, you're going to be competing with people who are just straight up using, you know, Chat GPT or cloud code and whatever. So having like a good handle on all of those things is always going to be helpful in the future at this very moment. Yeah. That said, that might not be the stuff that gets you excited to learn. I think that's a huge gap in the way people try to learn things as they try to learn things because they feel like they should be learning blank instead of because they're excited to learn Blank. So you need to figure out what excites you and then use your time to dive into those exciting things. You'll pick things up faster. Maybe you can sprinkle in some more boring things into the exciting things. The number one tip that I have for learning things is to pick projects of stuff that you would like in your life, stuff that you would get excited to be able to use or to have, like, even if It's just like a little robot lighting up when you click a button on a website, right? If that's exciting to you, those are the things you're going to want to spend your time on because they can really push you forward into creating, into exploring new avenues and exploring New ideas. And oftentimes that process is like what opens our brain up to picking up big concepts and things that we might not have dove into before. Wes Bos Yeah, I think about this a lot because I love, love learning things. And I find my learning happens in two ways. First, I do what's called like surface area learning, meaning that like, you're on Twitter, you listen to podcasts, you're reading blogs, you're just kind of scanning everything Out there just to kind of understand what's out there. What is the surface area of this? Reading documentation, understanding what the different APIs are, what the different texts are, what the different frameworks, languages, all of that stuff, right? That's very surface level, just understanding what's out there. But that only gets you so far. Like there's a lot of people out there that simply just know about everything, but they don't know like the nitty gritty of like why you might want to do something. And it's only once you go and build something in those several specific areas, do you realize, oh, this is why people are so fed up with that? You might be looking at the LLM landscape right now and be like, why are there so many harnesses right now? And why are there so many different ways to do X, Y, and Z? Why are people trying to reinvent memory in LMS. And it's because those people have gone deep with some of the other solutions and have hit the pain points. They think that they can do a better job because they understand it deeply. And I feel like a lot of people aren't going deep anymore and then learning things and actually hitting edges and having to like think and solve real problems um people are just very high Surface level i understand what's out there i can use the llms to boop boop do whatever i want so i think it sounds like you're doing a pretty good job at like the first level which is like Understanding what's going on you'll see this podcast i think a second level is picking a couple of things that you are interested in. And that may be like, I think it's probably a very good point to become the custom harness, cloud code, skills, cursor, whatever at your company. If you're a mid-level at a huge enterprise company and you become the guy that has figured it out and has the sickest setup and you can show everybody, you can have a lunch and learn, that'll Start to spread. That's probably the thing right now to focus on and to go deep on. So figure it out. Go download Hermes or go get Pi, get a custom thing set up. ([Time 0:26:43](https://share.snipd.com/snip/7e555097-e363-467a-b24f-67e96fa0b3af)) - **Update Strategically Not Emotionally** - Balance update avoidance with security and bug fixes: keep critical apps patched but question invasive UI bloat that harms your workflow. - Both hosts admit update fatigue; Scott updates obsessively, Wes recommends catching yourself resisting change when it harms productivity. Transcript: Wes Bos Says developers won't like hearing this buckle up guys you're not gonna like hearing this but i generally don't update software unless i'm forced to column seemingly harmless updates Have ruined enough native apps for me that i'd rather avoid them entirely i have a few reasons yeah there's certainly enough people on adobe photoshop cs2 because they don't want don't Move my cheese. I know where all my buttons are. Apps are getting absolutely massive. They add invasive features that take away from the experience and can't be toggled off. Reels, YouTube shows. Yeah. Can we talk about how awful the YouTube homepage is recently? Yeah. There's like three good video and then games for some reason. Who's playing games on YouTube? I don't understand that. Scott Tolinski I don't understand that. Wes Bos Do you get games on your you have youtube premium so maybe yours is different but mine is a hellscape yeah i don't yeah but even if you look at like the the explore section of the sidebar Scott Tolinski On youtube is just like a list full of things people don't care about explore shopping playables like yeah what are we doing yeah so he says example i got a new phone the latest ad-ridden Wes Bos Version of a simple guitar tuner that i had used for years and was installed and i had to find a new app unfortunately where i live local communities communicate via facebook groups i Know i know this all too well everyone's always anti-facebook that's where everything goes down is Facebook groups. There is no way to see local road conditions without seeing a shrimp Jesus or a deer on a trampoline. He's talking about like AI memes or whatever. I need OpenClaw to check Facebook for me so I can avoid seeing shrimp Jesus. For a long time, I used web versions of Facebook and Instagram because the apps were much more pared down, but they eventually added all of that invasive features. So true. Man, this drives me nuts. Instagram, like you can't pause a video on Instagram. Yeah. You can't scrub. Not easily. Sometimes. You have to like hold that. You have to like swipe sideways and like just let me pause a video. It's unbelievable. Anyways, this is not the rant, the rant thing here. However, since I'm a developer, I'm also on the other side of it. I want users to update immediately when I ship something. How do you reconcile the tension? Am I rational to avoid updates? Is that a normal behavior from the public up the, the general public? I've been making more of an effort recently i keep my browser updated and i sometimes scan changelog for important security updates or features that i might want for the most part i still Prefer early versions what's the problem is it me well call him i think he might be a little bit of a wiener um but i i certainly understand where you're coming from where sometimes you Don't want to update because it's it's getting worse um or like like i always complain about the warp update they put this huge update button on top of my warp and it ruins my videos all The time and it drives me nuts because been using the terminal for, what, 30 years, 40 years now, however long terminals have existed. I don't need to update until tomorrow. It can wait. I'm doing LS-L. I don't need to update my terminal immediately. And I understand from their point of view because there's fixes. And now people are complaining because something is broken. Like a lot of times, these updates are simply just fixing bugs that people are hitting, right? But then also, there's, they're changing stuff and who moved my cheese. I think that you're probably being a bit of a wiener here. I think in many cases, the updates are trying to make the app better. In many cases, the updates are fixing bugs. And I often try to catch myself being like, I don't want to update. ([Time 0:32:22](https://share.snipd.com/snip/2b004204-6774-4f51-8da2-7a5cab895007)) - **AI Shifts Which Developer Skills Matter** - The rise of AI changes what parts of coding matter: craft and syntax puzzles become less central, while system design, tooling and new problems gain importance. - Wes and Scott say feelings of loss are valid, but new domains (LLM workflows, plugins, hardware) open opportunities for those who adapt. Transcript: Scott Tolinski The rapid evolution of AI is killing my spirit as a developer. Crafting code and solving problems has been the best part of this job for 15 years for me. Now, the more I adopt different AI workflows, the more anxious I get about the future, both for the dying love for this job and the fear of becoming irrelevant. I know that this is a quite common feeling that many devs share right now, but I'm curious how you guys feel about this, as people seem to really love the craft. Patrick, I really love the craft. But more than the craft, I love solving problems. And the thing about AI workflows that make me feel bad is that the non-determinism in solving problems makes really stressed out. I really love that. In coding, I know exactly what to type or where to look to solve problems. I solve them, they're done. With AI, it often feels like, all right, I have this problem in my AI setup, not just with my code, but with my AI setup. It's not doing the things that it's supposed to be doing or that it's been told to do, or it's trying to use different tools when it has a read and write tool built into it. Those types of things make me actually angry. I get frustrated. That's what I, when I'm thinking about my joy being massacred in this job, it's strictly because my ability to solve problems has decreased because of things not respecting the determinism That I like. That said, I think you need to take an approach for this that there are just new problems to solve now. There are new problems to solve. There's a whole host of new problems to solve. And it's your job to solve those problems if that's what you want to do. And with that, again, there's crazy new browser APIs to explore. There's crazy new workflows to explore. And yes, AI is different. It's very different than how we used to work. But in the same regard, you're still solving problems, and you're still taking on challenges, and you're still using technology, advanced technology to make and do cool things on The web. So in those aspects, I think you need to look at it holistically as like, we are able to do a whole lot of cool things with the advent of LLMs and coding. And we are able to solve problems like never before. How can I use these tools to fuel that excitement rather than to let it kill my spirit? I think that's where you need to be, Patrick. Yeah. Wes Bos Patrick, you're not being a wiener here. You're probably the first person today that's not being a wiener. And you're not. Scott Tolinski I have a lot of empathy for you, Patrick, because I feel you. Wes Bos I would be lying if I said I wasn't bummed about the dying of lots of the stuff I love. Like understanding closures or just the deep, tricky parts of programming that I feel like I understand deeply are now – many parts of them are just now irrelevant. Doesn't matter that i i i understand how um like the closures and things work as much anymore certainly they still still matters to a point but i don't think it matters as much not nearly As much as it and even just like things like spot the syntax error that's a game that we we do on our live shows um it doesn't matter anymore that we're good at spotting the syntax error i Don't i don't think it does that you're really good at understanding where the curly bracket goes but does it matter if you are good at uh what's a good game it doesn't matter if you're Scott Tolinski Good at settlers of katan or something like that it doesn't matter it's still fun it's We will continue to do it because it still is fun. Wes Bos And I think like what I've seen over my career of like teaching people to code is that you kind of had two people. You had the people that were just learning to code because they had an end goal. I want to learn JavaScript because I want to build something. I want to make something. I have this idea. I simply I want a job because coding pays well. I saw all of it of people that simply just, I want to build something. I want to get that job. And I'm going to learn code because that is it. And then you have the other people as they're using code because they just love writing code. They love solving problems. They love the learning new things and the intricacies of it. And the people who use code to simply get to that end goal are stoked right now because they didn't necessarily love coding. And that's totally fine. Maybe you loved a business or you loved a project and learning code was simply the means to the end there. And now that has changed. And then the people who simply just loved coding are feeling a little bit bummed out right now, because it's like a lot of their identity and self-worth is kind of diminished. So I think that's totally fine to feel that. And I think a lot of people are feeling that right now. But, like Scott says, there are so many more new, exciting things to sort of tackle. If you are simply looking at AI and being like, my job before was to build this thing. And now, instead of building the thing, I type into the box and it builds the thing. And that's the way it's going to be forever. I think you're wrong there, right? It's totally what we are doing is changing. And you have to sort of buckle up and realize that what your career is, like what you're going to be doing day to day, is going to look dramatically different in the next couple of years Um yes solving problems still going to be the same thing um but the areas which you dip into and the kind of the stuff you dip into is going to going to look a lot different so that's kind of My thoughts on that and in some regards it sucks because it's everything is changing and you're worried for your job and in some regards, it's really exciting because now you can start Like there's so many areas of my life where I'm like, oh, now I can. Like I was always into like microcontrollers and whatnot, but like I I can get way more into it now, knowing that I'm a technical guy who can solve problems and I'm pretty good at thinking, But now I have this new superpower. ([Time 0:41:06](https://share.snipd.com/snip/f56c944d-6f63-4359-8a10-14f0fcc4d969)) - **Fix Broken Plastic With A Plastic Welder** - A plastic welder saved Wes from replacing broken household plastic like fridge bins and a wheelbarrow by melting squiggly staples into cracks. - He calls it a ~$30 tool that mechanically reinforces broken plastic far better than superglue. Transcript: Scott Tolinski Wes, do you got any sick picks for me today? I got a sick pick. Wes Bos I don't know if I have sick picked this in the past, but I'm going to repick it again. And this is what is referred to as a plastic welder. So if you have ever have something that's plastic that breaks. So namely, the thing that always breaks for us is the bins in our fridge you know the kids grab on them they crack and then they start to sag or like we had like a wheelbarrow that had a crack In it and it was like starting to open up one of those yeah yeah it happens all the time where plastic stuff breaks and you can't like super glue it together because that doesn't work so What this does this plastic welder is you have these like staples that, let's see if I can show the camera if you're watching the video. You have these like squiggly staples and you simply just press the button on this gun here and it will heat it up like immediately. And then you just sink the staple into the plastic and then you let go and the plastic rehardens again. And it works so, so well. It's unbelievable how good this is. And it's one of these tools that's like, I don't know, 30 bucks, 40 bucks to buy. And it's saved us like hundreds of dollars in buying like bins and wheelbarrows and just stuff around the house that you can't just simply glue you need to like physically it needs to Scott Tolinski Be mechanically put back together melted yes i love this yeah i i mean my wheelbarrow is currently cracked and i was like oh we're like i gotta get a new wheelbarrow i've had this thing Wes Bos Forever yeah well i i literally picked up one off the side of the road something I do all the time. I will drive and I see stuff on the side of the road that people are throwing out. And then I stop and look at it and go, I can fix that. Because you look at it and go, it has a crack in it, right? People, you crack it, you throw it in the garbage, right? But I love fixing things. ([Time 0:49:22](https://share.snipd.com/snip/f89b3b55-d97e-4aef-b0e3-8c3a263470b8))