So yeah, let's go ahead and get started. I was a project engineer. I've trained probably thousands, I'll just mention hundreds at this time. I love the position, and I learn from them a lot. Let me talk to you about the biggest consideration, number one, ask more questions. However many questions you're asking, multiply that by 10, and you're barely to where you need to be when it comes to asking questions. Here's the key, and let me go ahead and draw this. The concept is, if you're a project manager and you have a project engineer, you don't know what the project engineer doesn't know. So if you get a question every now and then, great, but what about answering all the questions? If I'm a project manager, I don't care about answering more questions because now I know they know the right way. The other thing is, a project engineer, you think, if you have assignment a that you get delegated that task, then you have to be done, start to finish, and that's when you show your project manager and set eyes on it. That is not the way to do it, ladies and gentlemen, you start and you get an iteration, and then you check in with the project manager, get their eyes on it. Then you do another iteration, check in with the project manager, get their eyes on it, multiple iterations faster, and you will get to the final product sooner, and it will be more correct. You cannot assume that the project manager is too busy to train you and mentor you, and if they say they are, you are 100 million, billion, trillion, gazillion percent at the wrong company, because that person is a jerk monkey, and you don't want to be dealing with them. They need to be mentoring and training you as a project manager. So ask more questions, more iterations, faster, and it will make all the difference. Number two, this is a big one. Don't disappear. Let me go ahead and draw you as a project engineer, and I'm not being insulting, and I know you're gonna love my skills here, right? This is you at your computer and at your desk. It's pretty clear. That's a pretty good I mean, come on, that's a pretty good sketch. Don't disappear if you see that the PE is just always there, always typing behind emails. So don't disappear behind emails. Don't disappear behind busy work. Don't disappear behind isolation. Don't disappear behind introversion. Now I'm not trying to be offensive here. A project engineer that disappears behind emails, busy work, isolation and introversion will not get promoted. That is a fact. I don't care what they say, nobody else is in charge of their career. Nobody else is in charge of digging in to find out how quality their work is. Nobody else is in charge of seeing their inherent value. It is up to this person to be transparent, to communicate, to volunteer for tasks, to be out in the mix, to build the team and to be out with a craft and to show their value do not disappear. The worst thing that can happen to a project engineer is being victim to emails and to then not show up. You should be stepping on your PMS toes. You should be out in the open number three, like I said, step on the PMs toes if you've got a pm and he or she is jamming out and doing these tasks, and you're a PE do not say, okay, these are my roles. I'm doing this the whole job. No, you're not. I want the PMs toes to hurt once you've got these in order. Hey. PM, can I do this? Hey? PM, can I run the next OAC meeting?