Being an Engineer

S7E28 Justin Rittenhouse | What Engineering School Doesn’t Teach You About Industry

Aaron Moncur Season 7 Episode 28

Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.

0:00 | 49:02

Send us Fan Mail

Justin Rittenhouse is a mechanical engineer, educator, and industry leader whose career sits at the intersection of advanced engineering analysis, manufacturing innovation, and mentorship. With a Ph.D. in Mechanical Engineering and degrees in Aerospace Engineering, Justin has built a strong technical foundation in structural mechanics, computational methods, and advanced simulation tools such as FEA and DEM. His academic journey is complemented by hands-on expertise in programming, material testing, and product development. 

Professionally, Justin has spent more than 11 years in industry, including roles with Fortune 500 companies, where he has led projects from early concept through commercialization. His experience spans designing custom cable assemblies for defense and commercial applications, developing automated testing systems using embedded hardware like Arduino, and leading the creation of high-efficiency manufacturing lines that significantly improved throughput.  

In addition to his industry work, Justin has a strong passion for teaching and mentorship. He has served as both an assistant professor and instructor of mechanical engineering, where he taught CAD, FEA, manufacturability, and material testing, while also leading senior design programs and advising student engineering teams. His ability to translate complex technical concepts into practical, real-world understanding has made him a valuable guide for aspiring engineers navigating their early careers. 

Justin is also the author of Secret Keys to a STEM Degree, where he shares actionable strategies for succeeding in demanding technical programs—focusing not just on studying harder, but on thinking differently, avoiding common pitfalls, and building the habits that lead to long-term success. Drawing from his own experiences, including overcoming personal challenges such as being born with a cleft lip and palate, Justin brings a deeply human perspective to engineering—one rooted in resilience, growth, and continuous improvement. 

Today, Justin is driven by a mission to help engineers better understand what the profession truly looks like, how to transition effectively from school to industry, and how to build confidence in the face of uncertainty. His work bridges theory and practice, offering practical insights that engineers can apply immediately to their careers. 


LINKS: 

Justin Rittenhouse LinkedIn: https://www.linkedin.com/in/justin-rittenhouse-phd/ 

Justin Rittenhouse website: https://justinrittenhousephd.com/ 

Buy Justin’s book on Amazon: https://a.co/d/04FtX62u  

Aaron Moncur, host 

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 

Justin Rittenhouse:

There's people on the floor that don't like you because of x, y, and z. That's okay. You'll still get promoting, you'll still do well on your reviews, as long as what you're doing aligns with what benefits the company, and we're all aligned with. Don't worry about all the people that have bad attitudes, they exist, but you still need to have a good attitude.

Aaron Moncur:

Hello, and welcome to the Being an Engineer podcast. Justin Rittenhouse is our guest today. He's a mechanical engineer with a PhD in structural mechanics, over a decade of industry experience, and a background spanning both academia and Fortune 500 companies. He stopped engineering at the university level, led complex R and D and manufacturing projects, and is the author of Secret Keys to a STEM degree. Justin is passionate about helping engineers bridge the gap between school and industry, sharing real-world insights, hard-earned lessons, and strategies for overcoming self-doubt and building a successful engineering career. Justin, thank you so much for being with us today.

Justin Rittenhouse:

Awesome. Thank you for having me.

Aaron Moncur:

All right. Well, I'm excited to dig into this with you, Justin. Let's start with the standard question that I ask everyone in the beginning, which is, How did you decide to become an engineer?

Justin Rittenhouse:

I don't have a good story, so I'll tell you how, but I'll do a little backstory as well. If I was smarter when I was a kid, I would have knew I was literally an engineer my whole life. I love Connect, which, by the way, are way better than Legos.

Aaron Moncur:

I remember Connects, I like those too.

Justin Rittenhouse:

It was so much fun. I was always very good at math, very good at math. Like, in ninth grade, I got like 113% so there was like obvious signs I should have been an engineer, but I guess I wasn't smart enough to pick up on them. And then I went to college as a business major for like one semester, and then all the people I knew in college with me were engineering majors, so I'm punished, so that's why I switched. Not a very good reason, but that's why I became an engineer. Um, I was destined for it, but I didn't, I didn't see it myself until later in life.

Aaron Moncur:

I think business and engineering share some, some common elements. They're, they're both very logic driven. They both rely on numbers to make good decisions. They both, at least if you're, you're a good business person, you're doing testing right, you're iterating through testing. So, I think they share a lot. There's a lot in common there. Tell us a little bit about your journey post graduation. Where what have you been doing, and leading up to what are you doing right now?

Justin Rittenhouse:

So I'm in few different companies. Um, I started out as an intern slash co-op at a company called Denso, which is automotive, I worked in quality R and D in the test lab. From there, I went to a small company, less than like 80 people, called Glass Master Controls. There I was a project engineer and engineering manager. I went to another company called J Letten Meyer, they met as a food company, spent in automonium. Now I went to food. I was there for a couple of years as a process engineer. I was also a professor in Ohio, which I'm a Michigan man, so not happy about my Ohio plot, but I've been living in Ohio for two years, and then now I'm at Worfle as a new product development engineer. One

Aaron Moncur:

of the things we're going to talk about is a book that you wrote, The Secret Keys to a STEM degree. We won't get too much into the details yet about that book, but why don't you give us just a little bit of background. Why, why did you feel it was necessary to write this? What was the impact you hoped it would have?

Justin Rittenhouse:

I thought it was necessary. A part of it was a, I kind of wanted to write a book. I thought it would be kind of cool to have a book out there, and it is kind of cool. Um, but why I thought this book in particular is from my background, I grew up very blue collar, I knew nothing about college or anything about college, and this book is kind of like a hodgepodge of information I. Wish I knew it has great information, if you know nothing about college. And then, obviously, I went to college for my master's degree and a PhD, so I actually know a lot more than maybe your parents might. I taught at a university for a couple years, so I also know more than maybe your parents may know that didn't go to college, so it has someone can learn everything they need to know, and only people can learn even more than what they already know. It's a wealth of information that I thought students needed to have.

Aaron Moncur:

When you are going to school, chances are, like most of us, you had a certain expectation of what industry was going to be like, and those expectations may have been influenced by things that happened at school, or maybe your imagination just filled in the blanks. We've all had expectations of what's going to happen post graduation. What are some expectations that you think a lot of students have that just aren't based in reality once they graduate and get into industry.

Unknown:

First,

Justin Rittenhouse:

is in some aspects school is harder than industry, in other aspects school is significantly easier than industry. One aspect when school was harder is probably technical problem solving, like actually doing math problems. Obviously, when you're in school, you do it throughout undergrad, you have homework on top of homework on top of homework, solving complex engineering problems in the real world, solving complex problems is a very small part of what you do. In the actual world, you have to kind of have to be a project manager. As an engineer, you have to do some of the technical stuff, and then you also have to work with people that come from all different walks of life. People react differently. You have to understand how to navigate people, and then also lead times and manufacturing issues. Like in school, you design something for a project and you're good to go. In reality, there's a lot of trade off these engines that you have to make. Quality has to come into play, obviously. In industry, cost has to come into play, and these are all variables that you have to make. And when you're in school, you're like, I think it costs one more, I want, I can make the best of the best, and we're all going to go, but that's not how reality actually comes into play.

Aaron Moncur:

Yeah, those are great points. I remember interviewing for my first full-time engineering job, and I can't remember exactly what the question was, but we started talking about, or I started talking about how I think it's so interesting how in engineering we use math to predict answers. Right, there's always a solution that we can calculate. And the guys who were into interviewing me, they were all pretty seasoned engineers, and I remember a few of them chuckling a little bit, and kind of, you know, nodding their head a little bit side to set side, and saying something to the effects of, yeah, it would be nice if that was all that always the case, but oftentimes we're, you know, we're just kind of putting our thumb out there, and how close does that look, and that was one of the things that surprised me, and I think surprised other students as well, exactly what you said, like the amount of complex problem solving using like math and physics, you know, like it happens for sure, but it's not that, at least for many engineering jobs, it's not that frequent, and that was a big surprise to me. There was another one, oh, it was just another experience I had recently, we, we recently interviewed someone, and for an engineering role that we have here at Pipeline, and this was a student who's just about to graduate. So, right now, it well, I guess he has or is about to graduate in just a couple days. It's end of May right now, 2026 and so we're asking him about some tools that he's learned in college that are applicable to engineering, and it was very curious that Excel was not one of the tools that that he mentioned learning, and so we asked him about that, we said, "Oh, how much experience do you have with Excel? and it was so interesting that he kind of, kind of looked at us blankly, and it was like, what do you mean? Excel, I mean, I've opened it before, it's not really an engineering tool, though. And that was another, and I remember graduating college, and maybe being in a similar place, right? Like, I knew what Excel was, I could enter data and do some very basic things, but I. Did not realize at all the degree to which I would use Excel as an engineer. Someone said I don't know if this is apocryphal or not, but someone said that Excel is the most commonly used engineering software in the world, and I wouldn't doubt it for a second, but that was another thing that, as a student, I just.. I didn't realize how important understanding Excel was.

Justin Rittenhouse:

Yeah, I actually tell my class I actually changed how I teach. I used to like normally engineering you use like Python or Matlab or Active, a programming language, which is what I use for undergrad and grad school, and then I was working in industry. I realized every engineer uses Excel every day. Well, I shouldn't say Emily, most engineers use Excel every single day, very few actually program. So now when I teach classes, I tell them you can use Python, you can use Matlab, and it kills me to say this by also now allowing you to use Excel, because the reality is you're all going to use Excel all the time.

Aaron Moncur:

Oh, I love that. I think that is such a practical insight and suggestion you're giving to these students, Justin. I see the same thing, you know, students coming out with skills in Matlab and Python, and the reality is we just hardly ever use, especially Matlab, but every now and then we'll, we'll pick up Python for something, but man, I don't know that we've ever used Matlab for anything at Pipeline anyway, and the schools just, they push Matlab so hard, every student comes out knowing Matlab, and I don't know,

Justin Rittenhouse:

I agree, that's why I, I now let them use it, sell a Springfield program, like Google, Google Spun Sheets, because actually, let me use it someday, yeah.

Aaron Moncur:

Well, what are some of the other oversights or even mistakes that you see students making these days?

Justin Rittenhouse:

I don't think they focus enough on their career long game, because we obviously, we go into college for children or jobs, right? We don't go into college and going to college, so I know some don't know what they want to do, and that obviously makes it more difficult, but others do know what they want to do. So the whole talent experience should be geared towards that, and what I mean by that is obviously trying to get internships in films that relate to what you want to do, but even within school, a lot of times professors will let you pick a project, make sure that project isn't random, make sure that project aligns with your career goals, and then if you, when you apply for jobs in that film, you can have that project on the education on your resume, and you can talk about in an interview. I'm like, yeah, I designed X while I was in school, and this is how I did it. So, align school with your career the best you can.

Aaron Moncur:

Great advice, great practical advice. Yeah, whenever I'm interviewing someone, I don't really care what's on their resume. Frankly, I try not to read resumes these days. I, I want you to show me what you've actually done, right? Give me a project that you worked on. It's fine if it was a school project, a student project, or even a personal project. That's great, but show me how you've applied problem solving, right, and logical thinking, and any engineering tools that you do know, how to use. Show me what you've done. Don't, don't just give me a resume, okay? So, let's, let's go back to your book now. Secret keys to a STEM degree. What is one strategy? Maybe it's the same one that you just shared, but maybe there's another one, a strategy from the book that you think a lot of students probably overlooked, but actually will have a really big impact in their careers.

Justin Rittenhouse:

Yeah, so the strategy we just talked about in the book, but one strategy I want to talk about, maybe won't have a huge impact on your career, but will have a huge impact on your life, and I think it's worth talking about is how many different scholarships there are. I talked about listening to my book, um, I, I submit the exact number, but it's like $100 million on scholarship money goes unawarded every year, and there are more scholarships than people think. Um, I'll give, I've gotten some that you won't think of, but I'll give two examples on ones you wouldn't think of. One, I got this one was semi competitive, but I got a scholarship from my hometown. My hometown in the surrounding areas have scholarships you may apply for. These one. Not all competitive, but I'm only competing against people from my hometown, this valley area. I'm not competing against the world, so it's significantly easier to get than other scholarships. And then another one, obviously, I can't hide kind of the way I talk is when I is, and I'm born with a class talent in a clap lip, I got a scholarship for that, like

Aaron Moncur:

really,

Justin Rittenhouse:

yeah, like it's not very competitive. I was born with a class palette and clap lip, I applied for the scholarship, and I got it. So, my advice is, tell me one, think about what makes you unique, and look on the scholarships, for most of them won't be competitive, and there's a smaller number of them things that make you unique.

Aaron Moncur:

This is very timely advice. My son just graduated high school and is going to start college in the fall in the engineering program, and I'm gonna buy your book and listen, read it. I think, man, what, what perfect timing right now for him to start reading something like this. Yeah, I'll have to think a little bit more about what makes him unique. White upper middle class family, not a whole lot of uniqueness so far we'll have to brainstorm a little bit, maybe. Okay, going back to the academic environment, what have you found that makes students successful? Like, what separates the students who end up being very successful academically, and then you know, as finding a job, a good job after college, versus the students who seem to maybe struggle a little bit more.

Justin Rittenhouse:

I think it comes from hard work. Obviously, if you're doing your homework, you do one in school, and normally people that do their homework often have more drive than those that don't. Not always from people can have drives to do different things, but often have more drive to succeed in an academic environment, often have more drive to succeed in an engineering environment in well worm. So, I think it comes down to the student themselves in only doing the homework, if they're doing the homework, they probably watch this 15 in engineering environment, and they probably will.

Aaron Moncur:

Pipeline now offers procurement of custom machined parts at significantly lower costs without sacrificing speed or quality. We design and build custom machines ourselves, so we consume a lot of precision machined components. Over the past several years, we developed a proven overseas supply chain to support that work, and in 2025 we successfully piloted that capability with select customers. Now we're opening it up more broadly. If you'd like to see how our prices and lead times compare, send us a drawing or two for quote. Visit Team pipeline.us or message me directly on LinkedIn. What is.. let's see.. I'm trying to think about how to phrase this. So, we talked about, like, Matlab versus Excel, right? Matlab gets taught in universities all the time. What engineers actually use day to day is Excel. What are some other gaps that you've seen where universities teach one thing but industry is actually doing something else entirely?

Justin Rittenhouse:

Presentations, I feel like there's a significant difference between a good presentation in school and a good presentation to like senior engineering leaders in school, you kind of have more, maybe more detail, more, more technical detail to the presentation, but when you're presenting to a large group on 4050 people, especially when you have leaders in there, it needs to be very, very clear, what you're presenting in what the results are. Very clear, like for example, you know, presenting a plot, you can't necessarily have numbers on your plot. It's also good to have, like, some kind of shading in the background, like green, yellow, red, as in, if num, if the point is in the green, it means spec. If they send the yellow, it's within 10% on the limit. If it's in red, then you know it's from a limit. So, you have to visuals on a PowerPoint needs to be very clear. You need to know what it means just by looking at it. Yeah,

Aaron Moncur:

that's a great one. We have a, an Excel expert, and in our team, I mean, we're all kind of experts to one degree or another, but there's one guy in particular who's super good with Excel, and he makes it visual, to your point, right? This is Excel, not PowerPoint, but he is so good at making things visual, just like you said, like gradiented colors that indicate, indicate different, you know, levels of success or failure, or whatever. So, yeah, anything you can do to help your, your stakeholders, those to whom you're presenting, like catch the vision pretty quickly, just at a glance, as opposed to having to sort through all these numbers and tables are what am I even looking at. What does this mean? Let's go post graduation now. And this, this brand new student graduate is moved into the workforce. What are.. what are some areas where they seem unprepared, or maybe. well, let's just leave it at that. What are some areas that you think young engineers are most commonly unprepared for?

Justin Rittenhouse:

I will say this to start is not all always unprepared, like I tell students, we don't. Mechanical engineering, in most engineering, is such a broad term, it spans a lot, and there's no way of us knowing what you're going to end up doing in your career. So we teach you a foundation, and then when you go into industry, you build on the foundation, but we rebuild you a foundation out of bedrock, and then you build your house on top of that. So, because of that, you have a lot of knowledge spread out over a lot of things, and then you start to pipeline and learn a lot, so when you go into industry, note that we know you're coming right out of college, we don't - I don't want to say this in a way that sounds rude - we know you don't know a lot about what you're going to know, you're going to learn a lot very soon, and we know that, so a make sure you're asking questions, ask questions you don't understand, and ask questions until you do understand what we're doing, why we're doing it, so you can get up to speed quickly, you don't ask questions, it's going to take you longer to run, and then another thing, kind of like we talked about before, in trade-offs, all these making different trade-offs, and then another is CAD, would be another example that students can make things very, very good in CAD, but very few students know how to design things in CAD that can actually be made, actually manufacturer ability is one I think is very common for students to be lasting.

Aaron Moncur:

Yeah, yeah, that's a big one. Okay, so there's there's technical preparation, right? Like you can prepare by learning CAD and maybe do your best to understand how to use CAD to actually design for manufacturability. You can know all the physics equations, all that stuff, but there's another kind of preparation as well, right? There's like trying to think of the right term for it, mental preparation or psychological preparation, mindset. What are there any mindsets or mental preparation that you think new graduates are often lacking in,

Justin Rittenhouse:

yeah, I would say thus navigating people. If you, depending on how you grew up, you grew up in a white collar environment, and then you go into the real world, and you have to work on your management faculty floor. You're gonna have to work with many blue collar workers who are fantastic. I'm not being literally blue collar by any means, I'm blue collar myself, but some of them do have attitudes, and you have to be prepared for that. You don't have the right mindset, they might like you, depending on what company you work at, and how mean they can get. Obviously, you have to be prepared for that. And what I remind them is, while you want to be nice and plenty of someone, and obviously continue being nice, what matters is what you're doing. Is there alignment between you in your manager and perhaps you in your floor manager? If there's people on the floor that don't like you because of x, y, and z, that's okay. You'll still get promoting, you'll still do well on your reviews, as long as what you're doing aligns with what benefits the company, and we're all aligned with. Don't worry about all the people that have bad attitudes, they exist, but you still need to have a good attitude.

Aaron Moncur:

Yeah, not everyone is going to like you all of the time, right?

Justin Rittenhouse:

Yeah, one of my favorite quotes, which I love, is you can be the sweetest peach onion tree, but some people don't like peaches.

Aaron Moncur:

Is that's great. Yes, yes, isn't that the truth, right? Okay, how about self doubt? Any stories or situations that you can think of where maybe, especially as a newer engineer, self doubt showed up, and you had to overcome that somehow.

Justin Rittenhouse:

Yeah, self-doubt is huge. Early on, in.. I don't think it ever goes away. At least it has it for me. I still have it occasionally, clinically regularly. Um, it goes down when you get more experience, and obviously when you jump into the real world, you're getting a term we often use, and you have to drink from a fire hose, you get a whole lot put at you really quickly, and you start down, you're like, man, I don't know how I can do all this. The reality is, you can, we've all done it, we're human, you're human, we can do it, you can do it, and just as you get more experience, things get easier, and some of that self-doubt had some classes.

Aaron Moncur:

Remember when I was a student, and I was taking a physics class, I think it was electromagnetism, which was a particularly challenging class for not just me, but it was kind of a weeder class I remembered, and I was in the lab with a TA one day, trying to understand some equation or some problem, and I just couldn't get it, and I was so frustrated, and I remembered something that a family friend had told me before I started my college career. He said that the school is really difficult, but just get through it. Once you're through school, the job is actually easier, and I remembered that at that moment, because, man, I just wanted to give up. I thought, this is too hard, I can't do it. And there was a lot of self-doubt, lot of self-doubt. And in that moment, I remember having a choice, like I could just quit, you know, do something easier, get a degree in economics, or whatever. I say economics, just because I remember that was the shortest degree at the college that I attended. Anyway, I chose to.. well, I remembered what this family friend had said, and it's okay, I'll just.. I'm just gonna push through it. This sucks, but I'll tough through it and get through, and I did, and he was right, you know. Once I got into industry, it was like you say, like easier in some ways, maybe more difficult in other ways, but overall it was just more practical, right? Far less theory and much more practice, and that's for me that was easier. I thought

Justin Rittenhouse:

Dan, like you were saying, only in industry, depending on where you want to, what you're doing, you don't often have to come up with an exact number, you come up with a loud amount number, and then you add a little bit to it, and you call it good,

Aaron Moncur:

yeah, and then you test it, and if it works, great, and if it doesn't, you add a little bit more, yeah,

Justin Rittenhouse:

exactly.

Aaron Moncur:

All right, well, let's talk about AI a little bit. Everyone's talking about AI these days. What, what uses have you found, or do you think will become available with AI and engineering?

Justin Rittenhouse:

So, I do think AI is a very useful tool. I think it's almost blown on all the hype and money we've gone. Like, to be honest, I'm not remotely worrying about AI taking my job, I'm just not.. I could be wrong, but I'm not.. I'm not worried about it. I do. Thank goodness

Aaron Moncur:

you're not a software engineer, right?

Justin Rittenhouse:

That is one of the things that is good at mechanical engineering. I'm not.. I'm not remotely worried, but it is very good at writing, learning code and learning in general, so you can use it to proofling emails or help you write an email, or I often write the email or the chat myself, and then sometimes I'll put it in AI and be like grammar check this will and click, or whatever, and then it's also very good at brainstorming, maybe like you have a problem, you like, hey, what are solutions in this problem, it can spin out sometimes. They're helpful, sometimes they're useless, but it can still help with brainstorming. So, I think it's a useful tool that can help you move quicker, but I don't think it's replacing mechanical engineers anytime soon, ever. Actually, but

Aaron Moncur:

yeah, I have to agree. I don't know if I would say ever, but no time soon for sure. How about in manufacturing, or have you found any useful applications for AI in manufacturing?

Justin Rittenhouse:

Yeah, I think it can be very useful in manufacturing. A lot of times with manufacturing and people on the floor, we're not really depending on really working the people you have. We're often not really working to optimize the results. They click the machine to settings that seem to work, and they hit go, they hit stop, and they leave. They go home and collect the paint check. Where AI is helpful is now you don't need an engineer to kind of play around with the machine, you can collect data with many different sensors on a machine and not on the machine, like maybe humidity increases your throughput, maybe it doesn't, but also temperature sensors and stuff like that, and then you can have AI kind of look through that data and be like, "Hey, when we had this setting, this setting, at this humidity, we produced way more, but at this humidity in these settings we actually had higher output. So, you can have the AI kind of, you still need an engineer to go back through it once the AI gives them hints, but in having the AI give them hints on how we can optimize throughput. Well, a normal operator may not be interested in doing that.

Aaron Moncur:

Yeah, yeah. All right. Great. I want to go back to your book, just for a moment here. The book primarily is for students. Is there information in the book that non-students or practicing engineers would also find helpful or useful?

Justin Rittenhouse:

Yeah, there are some. The time audience, as you said, is high school students and college students, but a part of that is still becoming a STEM work. worker, and for that you have to apply for jobs. There's information there about applying for jobs. There's information there about resumes in how to do a good resume. And then I have a very tin bit at the end also on how you should always negotiate what I'm a whatever salary, and they give you normally, I have room to go up a little bit, so you should always negotiate at least a tiny bit, so you can normally at least get a little bit more money, and then there's a whole chapter on stress and how to reduce stress and stuff like that, so I would say I'm completely making up the percentage, but 40% of the book applies for those not just in school, but those outside of school, maybe a little more. I think it's a very, very practical book.

Aaron Moncur:

Okay, so you mentioned stress, now you're talking my love language here. Let's talk a little bit about stress and managing stress. What are some of the techniques, some of the pro tips that that you are a proponent of? The

Justin Rittenhouse:

first one I would say is sleep. I actually looked up Miss Henley for the book, and you're simply getting seven to nine hours of sleep every night, not any less, not anymore. 79 I shoot for eight myself. And it's crazy how much better you all when you sleep. I forget again, you'll have to read the book actual stats, but no, it's been many studies. In one study was, I believe, people playing the keyboard, and they had one group practice more, but sleep less. They had another group actually sleep more, but practice less. The group that slept more were like 35% more accurate, and like 17% faster, them percentages might be also, you get they were actually better with less blackness, because they slept in proper night sleep, so sleep, and then obviously diet and exercise are most really important for stress, and then I have both information on that in the book, as well. Eat meat, eat foods, eat vegetables, eat whole foods, exercise. And then also, as far as school goes, some of this you can do, depending on what school you go to. If you go to a small school, you have less options than a bin school, but you can take classes at different times, meaning if you know a class is very hard, try to align that with easiest classes. If you know a professor is very hard, either he tells you he's very hard, all the students telling you he's very hard, and I don't, I don't recommend ratemyprofession.com by itself, but you can use that with talking to your friends and getting information in person to find out if a professor is very hard, and then again, if he is, line up his class with classes that are known to be easier, so don't got cause classes together, and also manage your time well. So, what I mean by that is time management is important in college. It's really not, at least in my opinion, is even more important in industry, and you need to pick and choose when. You go to the tech degree, you simply can't do everything amazingly, and what I mean by that is, if you're doing a presentation and you're doing it to leadership, or you have to present it on it to the class, you should do that very, very, very well if you have documentation that's only for you, and you're the only one who's there, read it. It needs to be clear if you don't continue confuse yourself in the future, but you don't need to make it look amazing if no one's going to look at it. You write it down, you make it very clear with plenty of notes, so you know what you mean in the future, it'd be done. You don't need to kind of clone everything to an exact degree. You can spend that time doing other things. So, make sure you know how to manage your time.

Aaron Moncur:

This is really wonderful, just fundamental, foundational, practical advice. I love this. I assume a lot of this is in the book, which is just another reason that I want to get a copy and give it to my son and have him read it, because it's so interesting, right? Like being in industry or having been an adult in society for a long time, we take so many of these things for granted, and we forget that there was a point in our past when we didn't know these things right. We weren't born with this knowledge. It was hard earned over years, and it can be really easy to forget that. And these young students that are coming up, they just haven't had the experience yet. They haven't had the opportunity to learn a lot of these things. So, I love how practical the advice that you're giving is. Here at Pipeline, we have, we have some core values. Core value number two is governed by productivity, not bureaucracy. And I just feel like all of these pieces of advice you're giving are very, very productive and practical. I wanted to go back just briefly and touch on the sleep aspect. This is another one, just foundational advice, right. How do you deal with stress? Get good sleep. Now, obviously, that we're oversimplifying a little bit, but generally speaking, I would agree that is the best thing that you can do to deal with stress is get good sleep. And something that I have found helpful, layering on top of good sleep at night, is taking a short cat nap during the day, a little power nap, you know, I'll lie down for 1020, maybe 25 minutes, not more than that. I don't want to actually fall asleep and, you know, zonk out, but just close my eyes and maybe almost fall asleep, get into that, that space where you're not quite awake, not quite asleep, and I find that, man, those can work wonders in reducing stress, increasing clarity, productivity. You know, I can push myself, and, and you know, many days I do just work all day, but, but many days I'll take the little power nap in the middle, and I find that I can push myself through all day and just keep working, and probably get down to only 50 or 60% effectiveness productivity second half of the day, or I can take that 25 minutes out, do a little power nap, and probably maintain, I don't know, 80% effectiveness for the rest of the day. So, like, the trade off is for me, anyway, it's very clear that powering down for those 2025 minutes, it is, it's well worth it, and it pays for itself, you know, easily.

Justin Rittenhouse:

Yeah, I remember a couple times in engineering school, we would stay up all night, and then we would lay one time in particular, we, we sent an alarm, because we had class on like 750 and was like 740 so we sent her alarm for 10 minutes, and we took a cat nap on the computer room floor, and then we woke up and went to class.

Aaron Moncur:

I guess it's better than no sleep at all. Yeah, 10 minutes. Yeah, I remember peers in school saying things like, well, I'll just sleep less, and I'll just sleep less, and so I can work more. Oh boy, it never worked for me.

Justin Rittenhouse:

I used to say, like a lot of people say, I can sleep when I'm dead. I don't think anymore. I'm learning a lot since then. I now probably only in time sleep. I know back in time I wouldn't have pile in time sleep only on, but back then I didn't think it was as important as I know

Aaron Moncur:

it is. Amen. Yep, agree. All right, let's see. We're gonna wrap it up here in just a minute or two. So, couple last questions. What is one thing that you have done, Justin, or seen done in industry, probably to accelerate the speed of engineering.

Justin Rittenhouse:

Well, first one we kind of already talked about, which is using AI. AI lane signing can help you light faster. It can even, you can even put data into AI and have it help you with that, and lane it. You still have to do that yourself as well, but you. It's still a useful tool, and then understand when you have to analyze the same data, when it's useful to you to create a rubric on something, so a good example, unless if you get the same data from the test lab, and you get it in often the same exact format. It would be wise to create a very, very good Excel sheet that contains normally. When you get data from the test lab, you get it often off in the same piece of machine, or the same - it has roughly the same output, so you would normally create a very good Excel sheet that can break that output out and create plots and stuff for you automatically, so if you have to do it a lot, take the time and invest and create a good Excel sheet that will automate it for you, if you only have to do it once and twice, then you probably only want to do it manually, and then going back to what we talked about earlier, don't I get people can be shy and they don't want to ask a dumb question, which for the most part doesn't actually exist. You don't know what you don't know. I know a lot of, I don't know a lot of things that are common sense to some people, but I also know a lot of things that are not common sense to other people. We all have, we all have a nuggets from knowledge. Um, so don't be afraid to ask questions if you don't know. Um, it's much better to ask the question upfront, get clarity on what you're supposed to be doing than doing something you're not supposed to be doing, and then happy to redo it. So, make sure you know what you're doing.

Aaron Moncur:

Yeah, that's wonderful advice. Some younger engineers I've worked with, I think one of the lessons that they've had to learn is when enough is enough and when to ask for help, right? They spend just way too much time trying to solve something on their own that many other people on our team already know how to solve, for sure. You don't want to just ask how to do everything, because that's not good for you or the team in general, but you know, spend a little bit of time trying to figure it out on your own, and if it gets to the point where you're like, yeah, this is going to take hours or days, and someone else knows how to do this, just go ask someone how to do it. There's, there's no shame in that. In fact, I'd say it's the other way around, like there should be shame in not asking someone when the answer is readily available out there.

Justin Rittenhouse:

Yeah, and that's a very good point. I always tell my students, and if you ask me a question, it should not mean the first thing that answer should not immediately pop up on Google. If it does, I might not answer the question. You gotta do a little bit for you. Yeah, exactly.

Aaron Moncur:

Yeah, right. Okay. All right. Well, Justin, we're gonna wrap things up here. Before we do, we, what, what is something that you are trying to learn, or a person that you're trying to meet, you know, maybe a subject, subject matter expert, or vendor that you're trying to meet, or a technology that you're trying to learn about. I'm hoping that you can share something that you're trying to find, or something you're trying to learn, and all of these wonderful people out in our audience, who are listening to this episode, some of them might hear that and say, "Oh, I know the answer to that, I can help Justin with that. Is there anything like that that comes to mind that someone out there in the audience might be able to help you with?

Justin Rittenhouse:

So, two things, not necessarily engineering, but similar. It relates to engineering, for sure. Would be leadership. I'm finally reading the famous book. Is it How to Win Friends? I'm forgetting your name, How to Win Friends and Influence People. I'm finally reading that book, so I want to know how to influence people from a leadership standpoint, and then two marketing as an engineer. I've always been kind of against marketing for what is obvious for a lot of engineers, but as someone that actually wrote a book in trying to get my book out there, you realize people can't buy what they don't know exists, so you have to do the marketing side of it as well. Even as you know, it kills me a little bit. It still is important. So, leadership and how to market by now, and two things I'm trying to learn today.

Aaron Moncur:

Wonderful, wonderful. I'll share one book with you right now that I read early on as I was starting to get into leadership, and it's called First Break All the Rules, and it's mostly about management slash leadership, but that was a really great one that I read, First Break All the Rules, and then I have done a lot with marketing over the years. I'm going to send you a PowerPoint. This is an internal PowerPoint that I made for myself. To help clarify what marketing is and how to do it well, I'll send you a copy of that, Justin. And for everyone else out there, if you have tips or tricks or books or people that you know that might be helpful for Justin in regards to leadership and marketing, by all means please get in touch with him, which is a great segue to the final question of our time together. Justin, how can people get in touch with you?

Justin Rittenhouse:

I have two, really two options: one, and of course, LinkedIn - you can find me on LinkedIn, and then two, I have my website, which is my first name, last name, and then your letter is phd.com so Justin Rinton House, phd.com and there you can contact me through my contact form, so LinkedIn or my website, but on a side note, when you told me, first blank on the rules, I wrote it down, and I think that's a good learning lesson for students, write things down all the time, you won't forget everything you do when you'll forget a lot of stuff if you don't write it down, so if it's important, and getting on paper.

Aaron Moncur:

Absolutely, that's another great pro tip that I use all the time is lists. Keep lists of things. I use OneNote a lot. Sometimes I just, I have like an email that's a draft email in my phone that I never send. I just use it to quickly write down, you know, an idea or a thought, and then I refer back to it later. But yeah, keeping lists of various things has been tremendously powerful for me.

Justin Rittenhouse:

Yeah, I always have at work every meeting I go into, you know, I don't think I'm gonna mean it. I always have a pen and a pen and paper every single meaning, and then in my life outside of work, I even notes app on my phone, like I have probably 100 200 notes in my notes app that randomly go off at certain times when I need to know, I need to remind me to do something

Aaron Moncur:

fantastic. All right, Justin, well, this has been a really fun and just foundational discussion. Thank you so much for being on the show with us today, and sharing all of your background and your experience. Any final thoughts before we sign off?

Justin Rittenhouse:

One, I'll add on a quote. I don't know if you run him a lesson down, but he's my favorite motivational speaker, and his quote is, don't let someone else's opinion on you become your reality, meaning it doesn't matter what other people think, um, what matters is your reality, and you can, you can make your reality come true, um, I always think to remind, I sign it in this podcast, I'm human, you're human, requesting listening and human, anything we can do, or anything anyone else has done, you can do as well. You have to put in the work.

Aaron Moncur:

Maybe there's a future for you as a motivational speaker. Justin, all right. Well, thank you again so much. This has been really wonderful,

Justin Rittenhouse:

awesome. Thank you for having me. It was fun and exciting.

Aaron Moncur:

I'm Aaron Moncur, founder of Pipeline Design and Engineering. If you liked what you heard today, please share the episode to learn how your team can leverage our team's expertise developing advanced manufacturing processes, automated machines, and custom fixtures complemented with product design and R and D services. Visit us at Team pipeline.us to join a vibrant community of engineers online. Visit the Wave dot engineer. Thank you for listening. Being an engineer has more than 300 episodes, and you don't have to listen to them in order. If you're dealing with a specific challenge right now, there's a good chance we've already interviewed an engineer who's been through it. You can jump around, search by topic, and listen to what's most relevant to you. See you on the next episode.