How Senior Developers ACTUALLY Write Code!

all right let's understand some standard differences between a junior and a senior engineer what happens if you stay in the industry for a long time don't go down the manager route remain an individual contributor still code what are the common traits you'll see these people exhibit compared to when they started I've myself started coding around 8 9 years ago and there are some standard things that I was doing wrong and eventually with time learned them myself through this video I want to share a few of these although a lot of these you will learn as you spend some time in the industry let's get right into it number one being strong from the inside and not from the outside no show off one common trait that I've seen in beginners is there's this very inherent need to prove something I know something special a good example of this is you'll always see beginner coders argue over random Technologies just because they read something somewhere versus usually you'll see Senior Engineers be extremely quiet for some reason they tend to stay to themselves and if you ask them a question they have a good answer to it but they never argue they're pretty complacent and happy with their knowledge and they don't necessarily impose that on other people so if you are a beginner learn to listen more and talk less this will serve you not just in your coding Journey but otherwise point two understanding business priorities as a beginner it feels extremely fancy to work on the best technology a good example here is during one of my live streams someone said har why are you using react next is the faster framework and the answer there was you don't really need next for this specific use case there will always be a fancier technology there will always be a faster framework but as a senior engineer there are a few things you keep in mind while picking up a technology some of these include do you really need a fancier technology or will this just mess up the code base is there enough engineering talent that you can get for example rust is extremely hard to hire for so if there is a use case that just works in not J it'll probably be easier to find cheaper engineers in node compared to rust and lastly speed Whatever Gets you off the ground as quickly as possible initially and as long as it can be maintained later on a lot of times especially in startups that's the right choice to take and you'll never see a senior engineer picking up the fanciest Technologies they are still writing extremely clean and maintainable code but a lot of times skipping out on a few things to get off the ground Point number three the job SL compensation anxiety this you will especially see in college including me I think there's a lot of anxiety around who got into Google who got the highest package and how I missed out on an extra 5 LPA I can tell you with time does not matter there are a few reasons for this reason number one is you prioritize a bunch of other things like family and health over money especially smaller increments and secondly you tend to reach some sort of a ceiling after a few years and the upside isn't too much if you're moving from 3 LPA to 10 that's a big jump 10 to 30 is a big jump 30 to 1 CR probably in India is a great jump after that the jumps are minimal and they don't change your lifestyle too much also Beyond a point people don't care too much about the money they tend to prioritize equity and where they're working on a little bit more Point number four incredibly calm and giving feedback one thing again I see Junior Engineers be extremely aggressive and and looking down upon and giving giving feedback to another engineer versus a senior engineer is extremely chill I don't know if you've ever had a conversation but I've had many one-on ones if you've made a mistake checked in some wrong code caused an outage you're never being scolded versus if you're a junior engineer or someone who has just began leading a team it feels very teachy and Powerful to you know throw your opinion at someone but in the end we're all humans and I think the best way at least in Tech to get the most out of humans is to be polite I think good Engineers are generally self-reflective if they've caused an outage they're already feeling pretty bad about it and a senior engineer knows that so you will never find them being extremely teachy that said uh if you do outperform a little too much I think they're the first ones to ask you to get fired Point number five being extremely calm and focused during an outage I don't know if you've ever had the pleasure of going through a real world outage but when that happens the worst thing you can do is panic the worst thing you can do is blame other people the goal is to fix it and bring it up as soon as possible during that time you will find a senior engineer being extremely focused at the same time extremely funny at least that's been my experience for the first time you'll find them being extremely happy funny and you know making a lot of jokes probably is some sort of a coping mechanism but during that time you'll see the best side of a senior engineer because they're very focused at the same time not blaming anything on anyone trying to fix the problem as soon as possible last point they code a little bit at least every day I think the best Engineers have known take a very big break like a six not a 6 week 2 week 3 week break from time to time and during that time they're usually with their families and you know chilling but other than that I've seen them being active a little too much I'm not saying this is good practice uh but you know you'll find them online on a weekend you'll find them checking in code sometimes on a weekend or reviewing code debatable if it's good or bad FMB call it's seen in a very bad light at least in the industry to work on the weekend because it forces everyone to work on the weekends anyways they would be coding on the weekend although they're generally cautious of not tagging people and aggressively telling other people okay please fix this but not on the weekend during the work although you'll always see them checking in code very quietly and not tagging anyone and in fact the opposite telling other people can please don't work on this during the weekend whenever your day starts on Monday please take some time to fix this issue you'll generally find these people as the as the papa personalities of the engineering team and it's gener pretty fun to be around such people because of a few things number one The Experience number two the humility number three how calm composed they are generally and number four uh their speed of checking in is also pretty nice cool with that that's all the point I had eventually aim to become this person a lot of these things you cannot force they come with time but if there's one thing you take from this video it's humility no matter how big of an engineer you think you are when you become a Serial engineer you'll see them be extremely humble when giving feedback and when reviewing other people's code with that let's end it I'll see you guys in the next one bye-bye

Channel: Harkirat Singh

Views: 63,064

Keywords: how senior programmers write code, programmers, programmer, senior programmer vs junior, how senior programmers code, how programmers write code, senior programmers, senior programmer code, senior programmer, self taught programmer, senior programmer vs junior developer, senior programmer vs junior programmer, senior programmer help, how to write better code, what makes a senior programmer, senior developer, junior developer, junior developer vs senior developer

Id: ZXCpGpxFYJI

Length: 5min 37sec (337 seconds)

Published: Tue Feb 13 2024