Being an Engineer
Being an Engineer
Jacob Evink | From CAD to Mechanical Curiosity: Student Engineer Spotlight
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
Jacob Evink is a mechanical engineering student at Western Michigan University with interests in mechanical design, robotics, manufacturing, and product development. Rather than waiting until graduation to begin practicing engineering, Jacob is actively developing projects that allow him to apply CAD, prototyping, electronics, and mechanical problem-solving to real-world challenges.
His industry experience has already exposed him to several sides of the product-development process. During an engineering design internship, Jacob created and modified CAD models, prepared manufacturing drawings, supported prototype development and testing, participated in design reviews, and collaborated with cross-functional engineering teams. He now works in a high-volume injection-molding environment, where he operates production machinery, performs quality inspections, and troubleshoots problems that can affect production.
Outside of work and school, Jacob is building an online engineering community by sharing his projects and lessons publicly. His content includes not only successful results, but also the mistakes, failed ideas, and repeated iterations that are often responsible for the greatest amount of learning.
Jacob also serves in a leadership role as a founding member of a fraternity chapter at Western Michigan University. As he continues through his engineering education, he is developing a perspective that combines technical curiosity, hands-on manufacturing experience, leadership, and a willingness to learn in public.
LINKS:
Jacob Evink LinkedIn: https://www.linkedin.com/in/jacob-evink-b67b12353/
Jacob Evink Instagram: https://www.instagram.com/gruff.makes?utm_source=qr
Aaron Moncur, host
PDX 2026 is October 20-21 in Phoenix, AZ. Learn more and register at https://pdexpo.engineer/
Subscribe to the show to get notified so you don't miss new episodes every Friday.
The Being An Engineer podcast is brought to you by Pipeline Design & Engineering. Pipeline partners with medical & other device engineering teams who need turnkey equipment like cycle test machines, custom test fixtures, automation equipment, assembly jigs, inspection stations and more. You can find us at www.teampipeline.us
Watch the show on YouTube: www.youtube.com/@TeamPipelineus
Yeah, I'm kind of all over the place. I always am like, is mechanical engineering best for me?'Cause then I get into electronics and I'm like, this is kind of fun, but then it's also the manufacturing side kind of all over the place. But I think the best for me would be mechanical because it's such a broad basis and I can go different places with a mechanical engineering degree
Aaron Moncur:Hello, and welcome to the Being an Eng- Engineer podcast. Another exciting episode for you today. We've got Jacob Evink, who is a mechanical engineering student at Western Michigan University, going into his sophomore year. Jacob has a background including mechanical design, CAD prototyping, injection molding, electronics, and robotics, along with engineering internship experience supporting product development and design validation. Jacob also shares what he's learning with a growing online engineering community, documenting both the successes and failures that are shaping his path into engineering. Jacob, welcome to the show.
Jacob Evink:Thanks for having me, Aaron
Aaron Moncur:All right, so usually we have engineers who have been out there in the field for many years on this show. And, and today we've got Jacob, who I'm excited about, our special guest here, and he is, uh, going into his sophomore year of engineering, so younger in his career than, than most of the guests we have. And I thought it would be fun to have the perspective of a, uh, a student in the engineering program who hasn't quite entered the work field yet, just to hear about what you're doing and what you're learning and how you're preparing. And I was particularly impressed with Jacob because he's doing a lot of, let's say, extracurricular activities outside of the, the demanding coursework. We all know how demanding the engineering coursework is out there. So to be doing these extracurricular kind of, uh, passion projects, personal projects on the outside, I thought was really impressive. And, and he's doing some cool stuff. So, uh, without further ado, Jacob, what made you decide to become an engineer?
Jacob Evink:So for me as a kid, I was big into Legos. I know a lot of engineers start out with liking Legos, but it was more than Legos to me. big into like making sure everything's perfect, everything's the right color, even. There's a lot of little details to me that if something wasn't right, would throw me off and mess everything up. So I think that's kind of what sparked me wanting to become an engineer. And then throughout high school, I did a lot of CAD and, uh, manufacturing classes with like mills and lathes. So that kind of sparked even more to really tell me that that's what I wanna do.
Aaron Moncur:That's awesome that you had mills and lathes in high school. We had nothing like that. Were, uh, uh, were… Did you go to a high school that had some kind of emphasis on engineering or manufacturing, or you're just lucky to be in a place that, that naturally had those things?
Jacob Evink:We just, it was just normal public school. It was a pretty big school, but we had a big shop, so there was probably seven, five to seven different mills. There was like probably eight lathes,
Aaron Moncur:Wow
Jacob Evink:saws, horizontal band saws. We had a lot of different tools, so got to learn kind of hands-on with that through high school
Aaron Moncur:That's amazing. Do you remember anything in particular that you made in those classes that you really liked?
Jacob Evink:Yeah, so I kind of started to outsmart my teacher towards the end of my high school career, 'cause was b- focused on teaching the class, and I kind of realized that's what I like, I kept going farther and farther. So I think it was my junior year, kind of just made a simple steam engine like a piston and, we could never hook it up to steam 'cause we couldn't have a fire in the shop, but we just hooked an air compressor to it and it worked perfect
Aaron Moncur:Nice. Super cool. And how did you even come up with the, the plans for this? Did you find drawings online or someti- something like that?
Jacob Evink:So I kinda got the idea in my head that I wanted to make a small motor of some sort, and I knew that, like, making an actual motor was gonna be too complicated. So then I was like, steam engines. I looked at different designs and I'm like, "That's doable." So I drew it all out. I think I started with paper, brought it to Inventor, then machining parts
Aaron Moncur:Wow, so you designed it yourself. This wasn't a de- design that you just found online somewhere
Jacob Evink:I kind of used like reference images I found, but overall the design was me
Aaron Moncur:Super impressive, man. Very cool. All right. Well, maybe it's that one, maybe it's another project, but what's, what's a project that you've done that, uh, like a hands-on project where you, uh, you learned significantly more than, than you, than you expected, and what are some of the things that you picked up?
Jacob Evink:So my recent project I've been working on is, like, a four-axis robotic arm, I'm been mainly with 3D printing and making parts with not a lot of um, components involved. And with my robot arm, I learned a lot of r-electronics, and I didn't this with, like, a teacher or anything. It was all trial and error. in the process of that, I have different stepper motors in it, so that involves stepper drivers, which involves a lot of wiring a lot of different voltages going to different things. one problem I faced was accident-- or I don't know exactly how it happened, but I short-circuited a little converter, and it blew up, and it started smoking everywhere in my room.
Aaron Moncur:The magic smoke.
Jacob Evink:yeah, very good smell too
Aaron Moncur:Nice. Uh, did you figure out what you did wrong so next time hopefully that doesn't happen?
Jacob Evink:N-- I never, never found the first, uh, error what happened, and then got a new converter for it. I put that one in and I accidentally, uh, reverse wired that one, so I knew the exact cause of that one. That was just me going too quick. But the first one I could ever figure out
Aaron Moncur:how funny. All right. Well, third time's the charm, I guess, huh?
Jacob Evink:Yeah
Aaron Moncur:Um, tell us more about your robotics project. Uh, where did this come from? What, what was the inspiration?
Jacob Evink:Yeah. So I think it was kind of going into my freshman year of college. I always got, uh, seen on social media different robot arms and stuff like that. So I kind of designed like a quick hour pr- uh, model of just ser- different servos, like little servo robotic arms. And I printed out, took a couple different prints figuring out what fits where and whatnot, and I kind of stopped that to an extent and then went through college. And then this summer I was like, all right, I need a good project to work on kinda gonna teach me a lot of stuff. So I came up with making this four-axis robotic arm because I didn't wanna quite go to six with my electronical knowledge at the time, I was like,"Let's do it." So I've worked on it for probably two or three months
Aaron Moncur:And you're doing mechanical engineering, right?
Jacob Evink:Yes
Aaron Moncur:Um, where did the idea come from to do a personal project at all? I, I love the fact that you're doing this because that is really where all the learning comes from, right? You, you go to school, you take the classes. It's all important foundational knowledge, but you don't really get the, the, the practical experience until you start building something and, and failing and learning from that. So what… Did you have a teacher or a mentor who suggested that you start doing these personal projects, or was this just something that you always wanted to do?
Jacob Evink:I follow a lot of different engineers online in different companies, and a lot of, lot of what I was seeing was your grades matter, but when it-- at the end of the day, when you start doing these personal projects that give you the trial and error mistakes, but you learn a lot, that's what helps. Um, I'm always pushing for, like, a goal, and I'm always myself towards that goal. So I always like… I set a robotic arm project as a goal, and I worked on it and worked on it and worked on it, and finally, I have a robotic arm sitting on my desk next to me
Aaron Moncur:Good for you. What, what did it feel like when, uh, all the different joints started moving and you could control it?
Jacob Evink:It took a minute for sure. had a lot of different wiring errors, but as soon as I got that first base, uh, stepper motor working and being able to move under my control, it was like I was so happy. I was showing my parents, I was showing all my friends. I was like, "Look at this."
Aaron Moncur:That's awesome. Yeah, look what I did. Um, how did you do the programming? What, what are some of the components that you used, and, uh, how did you figure out the programming? Because your background is mechanical, not electrical.
Jacob Evink:Yeah. So um, I have three or four different stepper motors along with drivers, as I said earlier. I have a buck converter 'cause I have a 12-volt DC jack going into it. So the s- the drivers need the 12 volts. Everything else, I'm using a ESP32 microcontroller to control the, um, everything else. So that obviously can't have 12 volts, so that's why the converter comes into play. have a, a ground rail, a 5-volt rar- 5-volt rail, and a 12-volt rail to power each of those components. And inside of the base, it's a-- somewhat like a mess, but when I look at it, I understand exactly where everything's going and what needs to be attached to where
Aaron Moncur:You're doing something I think is very smart. You're, you're documenting a lot of these projects. You're getting some video and pictures, and you're putting them into an online portfolio. When you start applying for jobs, that's gonna be so valuable. I can tell you, as an employer, I hate looking at resumes. I almost refuse to do it at this point. But when someone comes to me with a portfolio and can show me pictures and video of things that they've built, even just CAD screenshots, it's so much more powerful and compelling than someone who just shows up with a paper resume. So keep that up, and what, what is the platform you're using? I know Instagram, is that the, the main one?
Jacob Evink:Yeah, mainly Instagram, and then I post occasionally on LinkedIn trying to do like project updates, I'm get-getting better at making sure I'm posting more on that. But mainly Instagram I do of the projects I'm working on, the trial and errors,
Aaron Moncur:Ja
Jacob Evink:just overall like stuff like that
Aaron Moncur:Yeah. Keep, keep using Instagram. That's where the professional network is, the people who ultimately are probably going to help facilitate, uh, jobs or different connection, connections within the industry. Um, uh, what was I going to say? Oh, I just, I lost the thought. I had something, but it's gone now. Anyway, um, how long have you been working in CAD? I think you started in high school. Is that right?
Jacob Evink:Yeah. So year in high school, I took STEM. So that started out with getting a big old drawing board out and drawing out prints. Then halfway through the year, I started using AutoCAD, and I picked that up really quick. And then by the time I was a sophomore, I took a class called CAM/CNC. So we did, uh, AutoCAD and Inventor, so I learned 2D and 3D. And then we actually started making the parts with simple parts with mills and lathes. then in my junior year, I took advanced CAM/CNC, which was kinda like the step up from CAM with using a automatic CNC machine. We had three of those in our shop, which was pretty neat. And like I learned a little bit of writing G-code out for those, along with just uploading a program and making it cut out a part
Aaron Moncur:It seems like you're almost as interested in manufacturing as you are in engineering
Jacob Evink:Could you say that again, please?
Aaron Moncur:I said, "It seems like you're almost as interested in manufacturing as you are in engineering."
Jacob Evink:Yeah, I'm kind of all over the place. I always am like, is mechanical engineering best for me?'Cause then I get into electronics and I'm like, this is kind of fun, but then it's also the manufacturing side kind of all over the place. But I think the best for me would be mechanical because it's such a broad basis and I can go different places with a mechanical engineering degree
Aaron Moncur:Yeah, I, I'd say that's 100% accurate. Get that foundation in mechanical, and then like you said, you can branch off into so many different things with that, that foundation. Hmm. Uh, what have you learned about the difference between what it looks like in CAD versus how it actually looks in, in real life when it's, when it's manufactured?
Jacob Evink:So, I mean, I'm currently working at an injection molding factory, so I look at prints and then there's so many different factors that tu- tune into different tolerances and so many things that could mess a part up, and that's just with injection molding. I know with like CNC machines, there's a ton of different factors as well uh, the s- simplest, slightest little tolerance issue could be part that you can't even use anymore
Aaron Moncur:Yeah. What are, what are you doing with the, at the injection molding company? Are you actually running the machines?
Jacob Evink:Yeah, so a lot of-- Some of the machines are automatic machines, so you just have to make sure the parts come out all right, check a couple different key dimensions. Some of them are semi-automatic, so we actually gotta take the part out, look at it, trim up some of the trailers where the mold goes in or the plastic goes in. And it's a lot of measuring and making sure parts are coming out to the right, uh, dimensions, 'cause little dimension could throw off parts from the last hour
Aaron Moncur:Yeah. What are some of the, the process parameters that you found make a pretty big impact on the final geometry of the part?
Jacob Evink:So like we have hourly checks, so each machine that's running in the whole factory to be checked every hour of a shot of the, uh, parts. So that helps narrow down like, all right, are the parts coming out good for the last hour, this and that. And then every three hours on some of the machines that are producing a lot of different parts, we do like a box check. So a box of the parts, and we go through each of one of them one by one, making sure they're all lining up, making sure everything's good, there's no errors at all
Aaron Moncur:Nice. How about documentation? This is something that especially younger engineers maybe don't have a lot of visibility on, right, until they get into the field. I know when I was going to school, the only engineering documentation in the form of, of, uh, 2D manufacturing drawings I ever did was because of a capstone project that we worked on, and we just happened to get lucky on this capstone project that required us to, to create drawings. But outside of that, there wasn't, like, a class on it or anything. But working in a manufacturing facility, this injection molding place, I imagine you're exposed to drawings quite a bit, and the tolerances, and various documentation
Jacob Evink:Yeah. So each, each part that's running at the time, there's obviously a drawing. There's key dimensions that are highlighted, like this needs to be between this tolerances. Other ones are important, but they have a wider tolerance. And for documenting, we have check sheets, a lot of them. So going through writing out, all right, this section is this dimension, this section is this dimension. So you kind of see, all right, from this past hour, this part's coming this big, but this hour it's significantly bigger, so you gotta out what's going on with that
Aaron Moncur:And what are some of the, uh, parameters that you change if you see parts start to drift out of tolerance? How do you… What's the, the high-level troubleshooting process that you go through more than specific p- parameters that you're looking at?
Jacob Evink:So with the molds, you gotta look at how fast the plastic's going in, how hot it is, how long it's cooling. Like it's simple things like that that will completely throw off a part. Or if it comes out too hot and then gets instantly stacked with another part, it'll mold or bend or flex to that part, and part's unusable after that
Aaron Moncur:Yeah. Um, what's the… So you just finished your freshman year. Um, did you take many engineering classes that first year, or was it mostly like, you know, general, uh, general courses?
Jacob Evink:It was mostly general courses only because I did, uh, dual enrollment in high school with another, uh, CAD class. I took pretty much just another CAD class like I did in high school, but more advanced a community college near me.
Aaron Moncur:Okay
Jacob Evink:So I would've had to take that at college, but since I had the credit already, I didn't. did have technical writing so far, so that kinda helped me. And it was kinda funny, one of my final essays I wrote in that class was about injection molding and the to how important it is with tolerances and everything, and then I got the job at a injection molding place.
Aaron Moncur:Oh, wow. The universe was listening, huh?
Jacob Evink:Yeah
Aaron Moncur:Um, okay. So you're going into your sophomore year. What, uh, what CAD programs have you worked with? You mentioned, I think, Fusion 360. There was AutoCAD. Were there any others?
Jacob Evink:So in high school, I was taught AutoCAD and Inventor,
Aaron Moncur:Veteran, that's right
Jacob Evink:I kind of taught myself Fusion just with my Inventor knowledge. And then I'm kind of in the process right now teaching myself SolidWorks, so I have a basic knowledge of it, but I don't really have a teacher. Like obviously at school there's teachers for everything, but I'm kind of just doing it on my own, it, figuring it out
Aaron Moncur:Well, that's a big one. I definitely encourage you to keep learning SOLIDWORKS, because that is still, I'd say, the industry standard right now, the most, the most common CAD platform that's used, although Onshape is definitely up and coming. Um, and then there's, like, PTC Creo and, uh, NX is out there, and of course, like you mentioned, Inventor and Fusion 360. But SOLIDWORKS is still king, so, so keep learning that. Um, speaking of the extracurricular learning that you're doing, what, what are some of the resources that you've tapped into to learn a little bit about, uh, electronics and, um, CAD and anything else that you've come across so far that you didn't learn in school?
Jacob Evink:A lot of it is for me, it's just trial and error. But then I also am a big believer with AI. I know it's kind of like a topic if we like it or not, but I use it beneficially to help me figure it out and troubleshoot things, along with just looking at like YouTube tutorials. Like I come across an error, it's like, all right, how do I not-- how does this not happen? Or how do I fix this? Or how do I do this? Usually I can figure it out right away
Aaron Moncur:Yeah. Yeah, it's huge. Uh, I c- I've been obsessed with telling people lately about the, the new Sites feature in ChatGPT. I played around with it a couple weekends ago, and it was mind-blowing. I, I don't code. I'm not a programmer at all. Um, so I don't know how to, you know, build a website from scratch. And I used the Sites feature in ChatGPT and gave it, like, a paragraph and said, "Go build me this website that does A, B, and C." And it took, like, 45 minutes or so, which is a long time in, in, uh, AI hours, right? Usually ChatGPT or Claude, whatever, you get a, a response in a few seconds. This one took, like, 45 minutes. But it was incredible. It built this brand-new website from scratch that was not only functional, but it was beautifully designed. It looked like, uh, you know, I, I had some graphic artist who helped create all, all the graphics for this thing. Uh, and it had, like, a back-end functionality, admin privileges, different membership tiers, and all kinds of things. I was, I was floored with what this could do. So, uh, yeah, you're right. I think AI is still kind of, um, what's the word? Uh There are different camps for sure, but it is so productive. You know? You can be so effective. You can be like a… It's like a superpower having AI in your pocket
Jacob Evink:Yeah, I'd, I'd have to agree with that. I-- I know some people think of AI as just, do I do this? Or like, write this for me. Like simple task that you could do that you're lazy. I mean, that's at the end of the day, it's what it does. But like when you kind of abuse the privilege, but in like that scenario or like how I use it, kind of just like your sidekick on the side. Like if you ever come across something, you quick shoot a quick text and you know what, you know what to do next
Aaron Moncur:Yeah. Yeah, it's like your own private executive assistant, right? It, it can take notes for you, it can do research for you, it can write code for you, it can give you advice. It's pretty amazing. Shouldn't make it a crutch for sure, but there's a lot that you can do with it. All right. Um, what, what led you to make the decision to share some of these projects publicly that you're working on
Jacob Evink:I guess I always see people on social media, it's always perfect and how… Like, I look at these robot arms, for example, and everything is, like, perfect, and it doesn't look like it was even made by a person. It was, like, just perfect. I don't think some people realize that you can do that kind of stuff yourself, and you can, work through it, and eventually it'll turn out to be like that. But it's not just gonna happen after a day of working on something like that.
Aaron Moncur:Ja,
Jacob Evink:So just seeing other people's perfections and how it's-- you're gonna start somewhere
Aaron Moncur:It's not like in the mo- movies, right? Where, uh, tell Jarvis to do something and two hours later you have a brand new Iron Man suit. It takes a lot of time, lots of failure before you get to the end How has sharing these projects online and explaining them, how has, how has that helped you understand engineering principles at a deeper level?
Jacob Evink:Sometimes if I come across an issue, uh, kind of post like, "Hey, does anyone know this?" And I'll get some good feedback in the comments of like, "Do this, do this, do this, check this," stuff like that. it's also given me resource- to other people with other engineers or just hobbyists in my area that have kinda helped me and taught me different things, like random things I would've never thought of that now I know
Aaron Moncur:Yeah. Yeah. Well, you're still young in your, your journey even as a student, but what are some of the things that you hope you will learn in school? And do you have any ideas about, uh, maybe, uh, not shortcomings of education, but have you seen anything already that makes you think, "I wish they would do more of this or, or less of that in, uh, formal education for engineers"?
Jacob Evink:I mean, ultimately, I wish there was just all in all more hands-on stuff.'Cause like I know some people are better with taking notes, like just paper and pencil all day. Like I know there's a lot of people, especially me, that you could tell me something and it'll go in one ear, but unless I'm actually doing it, it's just not as beneficial to me. So like working with little projects like a robot arm or it doesn't even have to be that intense, just using simple like that, I think that'd be very beneficial
Aaron Moncur:Yeah, I agree. Uh, I, I've used the phrase for a long time, "Doing is better than learning about doing." And it's exactly what you said, Ry. I'm the same way. It, it'll go in one ear, out the other, and I won't remember it. But if I do it, then it takes it to a whole new level of understanding. There's so many little nuances that you figure out when you actually do something that you just don't, you don't get when it's all theoretical
Jacob Evink:You say that again? You cut out a little bit
Aaron Moncur:Oh, we might have a little trouble with our, our connection here. Um, what are… Do you have any other personal projects that you're looking forward to? Anything that you're planning on in the next, you know, six months or year?
Jacob Evink:So I actually just, I'm always looking for something else to do, whether I finish the current project I'm working on or not. But right now I'm kind of doing research and starting some files of making a little five-stage manual transmission, like a little model of one
Aaron Moncur:Cool
Jacob Evink:I'll be able to put on into like a little casing I'll make, and it'll read out the RPMs. You'll be able to see the gear shift and all that.
Aaron Moncur:Wow.
Jacob Evink:that's my next project
Aaron Moncur:That's awesome. Um, if you could learn anything, what would you learn?
Jacob Evink:Well, this is kind of a fun one. I wish I could like, completely learn all of like the coding, like knowing exactly what each code does and like just in general, all of it.'Cause I feel like many of my projects involve code, and a lot of the times it's just, "Hey, ChatGPT, I have this plugged into this, this plugged into this, and I want it to do this. Can you give me a code for that?"
Aaron Moncur:And it'll do it these days, right? Most of the time.
Jacob Evink:Mm-hmm.
Aaron Moncur:Yeah. Yeah, it's, it's almost like you don't-- You… Not knowing how to program is not the limitation it used to be because of AI. Have you used, uh, ChatGPT and Claude Code for programming or just one or the other?
Jacob Evink:I've stuck to only ChatGPT for now. I know there's a lot of different AIs, and then I've also heard more and more about Claude, I just haven't really gotten into those 'cause a ChatGPT by heart. I, I love it. So-
Aaron Moncur:Uh, yeah, me too. I started with ChatGPT, and I've kind of just stuck with it, and I really do love it. Um, the people who I know who, who are programmers say that Claude Code is probably the superior AI for writing, for writing code. And actually, we just started, um, experimenting with it internally and, and our, our, um, controls engineer has, uh, uh, shared some very promising things about it. So I guess if you are getting into code, uh, Claude Code does a pretty good job. But, you know, to be honest, I don't really know what the differences are between it and ChatGPT. I imagine they both do a great job All right, Jacob. Well, um, what else do you think that people should know about you and your journey through engineering? How are, how are you thinking of, like, what does being an engineer mean to you? Do you have any thoughts about that?
Jacob Evink:For me, I'm always thinking about how can I automate things, which is another kind of engineering. What engineer am I? But I always look at things about how they're made, how can I make this better? Especially with just my simple injection molding factory, how could I automate some of these machines to where you don't need people sitting behind them? And like engineering to me is just making people do less and different automated things do people jobs.
Aaron Moncur:So what happens when people don't have to do as much because engineering has taken over those, those roles? Uh, how do you think that changes people's lives, es- especially engineers who were doing all this technical work and now, you know, maybe AI grows and takes over some of that? Uh, how do you think that changes the, the industry, the profession?
Jacob Evink:For AI in the future, I still think that whether it does a lot with the environment and everything, we're still gonna need people checking it just to make sure that what it's doing is right. if we have AI working with machines and getting parts coming out, we're still gonna wanna have people checking those parts to make sure, 'cause we don't know everything about AI yet, it could still make a lot of different mistakes. So people are still gonna be needed. I, I feel like people are still gonna be needed in the, in the near future. But eventually, once we know more about AI, I think event- yeah, people might lose some of their jobs, but then it might grow opportunities for different types of jobs
Aaron Moncur:I was talking with my father-in-law recently, and he's a, a software developer, and he was talking about how some of the large tech companies out there had, had, uh, let go a lot of their programmers because of AI, right? How good it is writing code these days, and how it turned out to be a mistake letting all these people go because competitors, other companies out there, instead of letting their software developers go so that they could cut headcount, reduce expenses, they kept those people who are all now just turning out a lot more work. So instead of, you know, saving money on, on headcount, the number of, of salaries you're paying, these companies are just doing a lot. They're advancing their product, their service a lot faster because they still have the same number of engineers who are writing code, but they're all, uh, amplified, right? One, one engineer now can do the work of, I don't know, five engineers before because of the advances of, of AI and writing code there. And so some of these other companies who have let go all of these software engineers have had to scramble and, um, rehire them so that they can keep up with the companies who have kept everyone and are, are just moving at a, a much more rapid pace than they were before. So I, I think that trend is probably going to be true across all industries in-including hardware, mechanical. You know, eventually AI's gonna catch up to, uh, us in mechanical engineering as well somehow, whether it's humanoid robots or, or whatever. And as opposed to, uh, people losing their jobs, I think that we're all just gonna be a lot more productive, and, um, uh, co-companies aren't going to, I don't think, long-term gonna let people go. They're just gonna move faster. They're gonna do more with the resources they have, which is a really exciting prospect for the future, right? I mean, think of all the, the progress that humanity has made in the past, just the past 20 years. All, all the new things that have come out. The iPhone, right? Smartphones. 20 years ago, they kind of started just barely. Uh, and what, what do the next 20 years hold with the, the rapid acceleration of progress and technology that AI is allowing us? I, I think it's gonna be a really exciting time.
Jacob Evink:Cut out on that last part again. Can you say it again?
Aaron Moncur:No, that was a long rant, a long diatribe. I don't think I can even remember everything I said. But anyway, Jacob, anything else that you wanna go over before we sign off here?
Jacob Evink:I think that for any young engineers listening, I'm going through exactly what you are, and school is gonna be rough just because you're not gonna be always doing things that you like, like taking gen ed classes or doing hands-on stuff. But use what you learn for that hands-on stuff because it's very beneficial
Aaron Moncur:Amen, brother. I remember going to school and thinking it was so hard, and there were a couple of times I can still remember where I thought I was gonna give up. I just wanted to quit because it was too hard. But I didn't. Kept, kept pushing, kept moving, and I eventually made it through. And I can tell you, at least in my experience and in the experience of many people I've talked to, the actual job of being an engineer is more fun and less hard than being a student in engineering
Jacob Evink:Cut out again at the end. Can you
Aaron Moncur:Gosh. Executive summary, what I said was it is easier to be an engineer than it is to be a student in engineering. Yeah. All right, Jacob. Well, all, uh, technical difficulties aside, it was great talking with you. Thank you for being a guest on the Being an Engineer podcast today. And, uh, I look forward to seeing more about what you're doing online in LinkedIn and in your Instagram
Jacob Evink:Thanks for having me
