Name: What is a "senior" software engineer? The difference between junior and senior engineers.
Uploaded: 2020-03-27T19:08:07.000Z
Duration: 10 min 19 s
Description: Thousands of YouTube videos with English-Chinese subtitles! Now you can learn to understand native speakers, expand your vocabulary, and improve your pronunciation...

The imperative

Gerund

I am the attack lead, and today we're back to drinking classic Lacroix.

I wanted to talk today about the difference between a junior engineer and the senior engineer.

You may be a junior engineer right now, and you may be struggling and trying to figure out Well, how can you take that next big step and ramp up your career growth?

I can take these the next level hacking and skyrocket your career growth.

And I have a few excellent tips to help propel you into the light of success into a senior software engineer like myself.

So now what most junior engineers don't realize is how difficult it is to be a senior software engineer.

It is a ton more work, a ton more responsibility, and it may be a level of demand and pressure.

One thing to realize is just the sheer amount of responsibility that senior engineers like myself have to handle is just mind boggling.

There's just so much responsibility that I need to opposed.

Um there's probably nobody more responsible than myself.

I am the most responsible person that I know.

Have anybody ever asked, Well, who wants to be responsible?

I'm more than ready to say, Yeah, I'll be responsible.

So just being responsible is a huge factor and being a senior engineer now, the other thing I've got going from myself, which you may not have going for yourself and that qualifies me to be a senior software engineer is my age.

So just that additional age should bring him with that years of additional experience, wisdom, knowledge know how In general experience if you're in your low twenties, you're probably a junior engineer.

Once you get into your thirties like me, well, naturally, I'm a senior software engineer Now.

The other thing you can do to get yourself into the row of a senior software engineer is to start re factoring coat.

The more code you re factor, the more senior you become.

One thing I've seen some people do is re engineer everything into a plug INS based architect er such that every single feature is created like a plug in.

Everything is done using adapters, mixing plug ins, and just coming up with this system can qualify you to become a senior software engineer.

See, let me tell you about the problem with you and the problem.

Why you're a junior software engineer and it's because the identity has locked onto you.

You identify yourself as a junior saw for engineer, and you can't break out of that because the people around you everyone you know has reinforced that identity of junior software.

Engineer onto yourself, and it's very difficult to break out of that.

I would say that this problem is very difficult to overcome, because even if you yourself came, grow beyond that and view yourself as non junior, other people will still view you as a junior engineer.

What some people might do in this scenario is just start switching jobs.

And the more jobs they switch, the more senior they become because they can redefine their identity as senior, even though they're not.

Some people just keep shooting jobs, and eventually you can get to CT else that that's just by doing this simple little trick, you may have noticed that I have some book, and this is intentional because this additional book that I've built onto myself has helped establish my authority.

It makes me look like a more dominant figure, like a silverback gorilla and this body book that you can build up to if you were to drink like protein shakes and milk and just a lot, maybe drink some beers because even heavy a beer belly can help establish that size.

And the size is a big factor in helping you establish your credibility on authority within the workplace.

Now, this might be more challenging if you were working remotely, but thankfully, most companies forbid you from working remotely so you can go into the office show off the size of your body, the book, and that could just make you a more dominant figure.

We humans we like to think that we're so sophisticated, but the truth is, we're just animals were like gorillas and gorillas respect this over back.

And the little known fact is with that's the truth with humans as well.

We'll know a trick I like to do is join the startup, and that started.

It's easier to get nice titles like and one start up.

Every single person was named member of Technical Step.

If you're in the one or two persons started, you could essentially call yourself CTO because that's essentially what you are.

One key trade of a senior software engineer is to win arguments, and you know you can win these arguments using any number of tactical tricks as you can.

You want to study up on policies like personal attacks, selection, bias, sampling, bias, survivorship bias, the railing conversations, microaggression, rambling strawman attacks, hiding information, personal threats and any number of other tricks you can use for your arsenal to win arguments.

And you want to be careful about this because if you lose enough technical arguments, you can actually demote yourself back to junior a software engineer and lose that senior software engineer status.

You want to shut those junior software engineers down and let them know who's bus.

One key difference between senior software engineers and junior software engineers is senior engineers.

Don't just coat if our you're doing this coding, even if you're coding a lot and really high quality coat.

You're not really at the senior level yet.

Spend more time strategizing and thinking broadly about overall direction, which is why you want to lower your code output.

If you're pushing out too much coat, people start to think, Well, you're just spending all your time coding.

You're not doing anything else, even if you are.

You want lower your code output, and the more you lower, the more senior you will become.

Along with that, you want to reduce the amount of time you're spending at your desk.

If you're sitting at your desk, everyone knows what you're doing.

Don't just say Well, yeah, I see Patrick.

But if I'm not at the desk, what people don't really know what I'm doing.

I could be working are strategizing about some high level coterie factor you don't really know when you leave a little to the imagination.

People's fears take over and they start to understand.

Well, this person may be more dominant, maybe more superior than me you want.

Just let that fear playing their minds and let that work to your advantage.

One other thing you can do is start a YouTube channel.

I've seen a lot of junior engineers start YouTube channels, and soon they're calling themselves senior software engineers.

Just having a platform to spew out your verbal garbage can help establish a sense of authority for yourself.

And soon after, you'll find yourself surrounded by people who can't even coat who have no idea what code even.

You start buying into that story, and pretty soon you're seeing yourself or engineer senior suffer.

Initiative is the game, and what I like to do is just initiate things like it's not so much about finishing anything.

It is about starting something so well I'd like to do is just start calling meetings.

And I would just schedule weekly meetings scheduled as many meetings as I can.

Once everyone gets into the meeting and the meeting starts well, I mean, I'm not really sure what's supposed to happen.

Then it's It's not my problem than you know, Like I just started the meeting.

I initiated that, and my job is over by that point.

Senior engineers also have a reputation of bringing things up, a level such that were not deep into the weeds, talking about technical, nitty gritty details.

Anytime I see my co workers start talking about little technical details here and there, I would just stop them and say, Hey, I know you guys love talking about these little technical details.

Let's bring the discussions up a level and talk about the overall strategy.

The overall planned the road map, and we don't need the details.

So what I'd like to do is I work without my headphones on so that I can hear anybody talking.

And as soon as I hear a technical discussion that's going into little nitty gritty details, I'll nip that conversation in the butt.

I would just go there and just stop that conversation right there.

That helps us keep focused on the overall wider strategy.

If the project succeeds, then you can bet that I would be there to take credit for, and that will help celebrate and be self congratulatory and every regard that I can to make sure that I get as much credit as I can for my team success.