Experience is NOT a lie. Just because you encountered one developer with over 10 years of development with such incompetence and not be able to do basic stuff like running unit tests or remote debugging, you cannot make a general consensus that every other developer who is doing just "backend" stuff for X amount of years hasn't evolved. There are developers who constantly try to continue to learn even after years of experience and there are others who are have just plateaued which is what your co-worker is. Conversely, you cannot declare yourself to better because you have been doing backend, frontend or what is called today a "full stack developer"...one could be, but not a generalization...From the words of Bruce Lee: "I fear not the man who has practiced 10,000 kicks once, but I fear the man who has practiced one kick 10,000 times."
I agree with a lot of what you said. There's currently a senior engineer in my team that went from contractor to full time and the reason why he got the title senior software engineer was because of the amount of years he had in his resume. I find it weird because we have the scope of work , influence on the team and amount of contribution . Obviously my company has no clear definition to what a Senior Engineer means, aside from the amount of years you have... Thanks for the insight, it really showed me that I can be a senior engineer, I just need someone to see that in me and for me to continue doing what I'm doing. Subbed.
Sadly what you will find at a lot of companies, especially when converting contractors to full timers, is that they strictly look at results. That is mostly all the business folks are worried about. Results. Quality and Craftmanship are not on their radar. One thing you have to remember is that you have to be your own cheerleader. Don’t look for someone to hype you up. Hype yourself up. Be proud of the work that you do and let others know about it.
A huge problem lies on the interviews, where you are being asked "do you know this? do you know that?" but very few actually check how you write. The result is that it's easier for developers who know a lot of technologies to land a job regardless of whether they know how to write good code than others who know how to write good code, know their material, but do not have the time to explore all these available tools and utilities
Regarding "don't look at just one" stack overflow answer. It reminds me of "measure twice, cut once". Timeless advice, applies to all sorts of stuff. I'm still a noob and not yet a working developer, but this concept has helped me really nail down errors and edge-cases; having two/three designs and comparing and contrasting why one is better than the other. This then leads to the question, if I now know why something is "better", what is the best way of achieving that "better" output. Measure twice, cut once. So useful to keep in mind. Saves a lot of time but unfortunately good design/problem de-composition is an invisible boon, you don't notice the time you haven't lost to refactoring and debugging. Just got to have faith that diligently following the process is the best approach to take.
These are facts! Videos like these are the hidden gems of You Tube. Too much SE fluff videos out there. Refreshing to hear from an experienced craftsman
I once worked with this one guy who had 3-4 yo exp and he was "writing" the new app in a different language than the company used. I put "writing" in quotes because it hardly had any code in it. Our true senior engineer had to come and fix it all and he had to be taken off a different team to do that.
Agree with you on all this , pretty amazing how incompetent many “sr” devs can be … also how some play the offers game vs really leveling up (frustrating from mgr angle)
Well said. My definition of a master craftsman is someone who not only understands and practices the craft, but also works to improve the craft. This usually happens in the form of training up and exchanging ideas with other practitioners of the craft. 'talking shop' is what the old timers used to say. I think that's what you are doing with this channel. I've met too many jerks who claim to be senior level but are territorial with their experience. A truly confident engineer in any industry wants to share their love of the craft and improve it by learning from their heros (uncle bob rules!) and training/sparring with their crew regardless of what the organization chart says.
This is so true I have been working over 2 years and still feel like a newbie but it’s because 70% of my time I am in the lab testing or working on a review of code. Very little coding being done. But my LinkedIn is flooded with recruiters from big and small companies
Your topic is amazing , since i have been promoted as a senior developer i ask myself this question , do i deserve to be senior developer or it just a number of fake experience i wish you to complete it is a very important topic
This channel is so underrated. It is nice to listen to intelligent people, like developers for example. But listening to wise people is on a totally different level! :) Good luck!
Remote debugger is a thing huh? I learned something new today! Thank you. Sometimes, I don't even bother setting up local debugger, just print print print print, it does (almost) exactly the same thing. But I understand that setting up debugger once makes debugging much faster later.
This is so true. My first dev job was mid-level. I also see a lot of friends I knew actually got their first jobs as senior engineers. What makes us different were the technical communication skills and being able to dive deep to solve hard technical problems. If you can do that, then you are already at senior-level.
i read lots of senior role's job description are actually just lke normal software eengineer its also wont have huge gap for 1year experience developer to be qualified in terms of his/her skills
Great work on the video! The premise is spot-on. I like your argument about the "3 year senior dev" but I'm going to disagree. I don't think seniority should use the entry level as the meter stick, and I also don't think that 3 years is enough time to get exposed to enough facets of engineering to make someone effective in a senior role. That said, I'm one of the jerks that say developers should have working knowledge in development, devops/cloud, front-end developer, back-end development, database design, UI/UX...
I got a deleted scene where i go on a rant about a "full-stack developer", may have to post that sometime in the future. The 3 year senior was more to show that at that point in time, you are at the top of the food chain in your enterprise domain. I should have emphasized more on a Senior at this company is just that, a senior knowledgable person on the domain.
If you are looking for more "career starting" content, I would look up Traversy Media's channel. Once you got a few projects and years under your belt, all this content here will hold more value.
"8 years of experience in one area" - you are deep expert in that area. "8 years of experience in different projects" - you are wide area specialist. Something like Full Stack Developer versus Back-End Developer. What is better - depends on project. Once in asp.net project I have tried to set up Remote Debugging at a Production server, but was blocked by security limitations of the server. I was farce to debug an issue by 20 commits to Git with comments like "Debugging". Silly, but finally, the issue was solved. Sometimes even experienced developers do silly mistakes. We all are still humans. About me: 12 years experience in asp.net (full stack).
This is definitely the experience of someone who has been in the game for a while. The honesty is appreciated.
Experience is NOT a lie. Just because you encountered one developer with over 10 years of development with such incompetence and not be able to do basic stuff like running unit tests or remote debugging, you cannot make a general consensus that every other developer who is doing just "backend" stuff for X amount of years hasn't evolved. There are developers who constantly try to continue to learn even after years of experience and there are others who are have just plateaued which is what your co-worker is. Conversely, you cannot declare yourself to better because you have been doing backend, frontend or what is called today a "full stack developer"...one could be, but not a generalization...From the words of Bruce Lee: "I fear not the man who has practiced 10,000 kicks once, but I fear the man who has practiced one kick 10,000 times."
I agree with a lot of what you said. There's currently a senior engineer in my team that went from contractor to full time and the reason why he got the title senior software engineer was because of the amount of years he had in his resume. I find it weird because we have the scope of work , influence on the team and amount of contribution .
Obviously my company has no clear definition to what a Senior Engineer means, aside from the amount of years you have...
Thanks for the insight, it really showed me that I can be a senior engineer, I just need someone to see that in me and for me to continue doing what I'm doing.
Subbed.
Sadly what you will find at a lot of companies, especially when converting contractors to full timers, is that they strictly look at results. That is mostly all the business folks are worried about. Results. Quality and Craftmanship are not on their radar. One thing you have to remember is that you have to be your own cheerleader. Don’t look for someone to hype you up. Hype yourself up. Be proud of the work that you do and let others know about it.
A huge problem lies on the interviews, where you are being asked "do you know this? do you know that?" but very few actually check how you write. The result is that it's easier for developers who know a lot of technologies to land a job regardless of whether they know how to write good code than others who know how to write good code, know their material, but do not have the time to explore all these available tools and utilities
I love to hear experienced developer war stories. Especially when they have a good delivery like you are giving.
Regarding "don't look at just one" stack overflow answer. It reminds me of "measure twice, cut once". Timeless advice, applies to all sorts of stuff.
I'm still a noob and not yet a working developer, but this concept has helped me really nail down errors and edge-cases; having two/three designs and comparing and contrasting why one is better than the other. This then leads to the question, if I now know why something is "better", what is the best way of achieving that "better" output.
Measure twice, cut once. So useful to keep in mind. Saves a lot of time but unfortunately good design/problem de-composition is an invisible boon, you don't notice the time you haven't lost to refactoring and debugging. Just got to have faith that diligently following the process is the best approach to take.
These are facts! Videos like these are the hidden gems of You Tube. Too much SE fluff videos out there. Refreshing to hear from an experienced craftsman
I once worked with this one guy who had 3-4 yo exp and he was "writing" the new app in a different language than the company used. I put "writing" in quotes because it hardly had any code in it. Our true senior engineer had to come and fix it all and he had to be taken off a different team to do that.
UA-cam recommended me part 5 and went straight to this. Great recommendation and can't wait to watch them all
I swear the production quality gets a little better; thanks for watching.
It's great to hear from someone that's been in the field and seen some shit. Thanks for your input!
Thanks for checking out the channel
Agree with you on all this , pretty amazing how incompetent many “sr” devs can be … also how some play the offers game vs really leveling up (frustrating from mgr angle)
Well said. My definition of a master craftsman is someone who not only understands and practices the craft, but also works to improve the craft. This usually happens in the form of training up and exchanging ideas with other practitioners of the craft. 'talking shop' is what the old timers used to say. I think that's what you are doing with this channel. I've met too many jerks who claim to be senior level but are territorial with their experience. A truly confident engineer in any industry wants to share their love of the craft and improve it by learning from their heros (uncle bob rules!) and training/sparring with their crew regardless of what the organization chart says.
This is so true I have been working over 2 years and still feel like a newbie but it’s because 70% of my time I am in the lab testing or working on a review of code. Very little coding being done. But my LinkedIn is flooded with recruiters from big and small companies
Really great video. I've always felt kind of behind and this video really help me put things into perspective
Your topic is amazing , since i have been promoted as a senior developer i ask myself this question , do i deserve to be senior developer or it just a number of fake experience i wish you to complete it is a very important topic
I love this video! a fresh take on what up and coming devs want to know-- can't wait to see what info the rest of the videos have!
This channel is so underrated.
It is nice to listen to intelligent people, like developers for example. But listening to wise people is on a totally different level! :)
Good luck!
Thanks for checking out the channel!!!
Remote debugger is a thing huh? I learned something new today! Thank you.
Sometimes, I don't even bother setting up local debugger, just print print print print, it does (almost) exactly the same thing.
But I understand that setting up debugger once makes debugging much faster later.
This is so true. My first dev job was mid-level. I also see a lot of friends I knew actually got their first jobs as senior engineers. What makes us different were the technical communication skills and being able to dive deep to solve hard technical problems. If you can do that, then you are already at senior-level.
thankyou for the information
as i expected but (im such a doubt person) needed to know or hear from a real person saying that
i read lots of senior role's job description are actually just lke normal software eengineer
its also wont have huge gap for 1year experience developer to be qualified in terms of his/her skills
Despite only being mentioned briefly, I enjoyed finding out that the contractor was converted full-time✌❤
I hope I can press the like button multiple times. Thank you for sharing this
So good! Thanks for sharing!
Very real software engineer experience, I feel you, but still not a senior software engineer
I surely learnt a lot from the playlist.
I have been using clean code architecture for past some years
I love this channel. You have my sub sir.
Very Insightful, Thanks for sharing.
Bro 🔥🔥🔥
thanks for your advice
This is great video, thank you
Great work on the video! The premise is spot-on.
I like your argument about the "3 year senior dev" but I'm going to disagree. I don't think seniority should use the entry level as the meter stick, and I also don't think that 3 years is enough time to get exposed to enough facets of engineering to make someone effective in a senior role.
That said, I'm one of the jerks that say developers should have working knowledge in development, devops/cloud, front-end developer, back-end development, database design, UI/UX...
I got a deleted scene where i go on a rant about a "full-stack developer", may have to post that sometime in the future. The 3 year senior was more to show that at that point in time, you are at the top of the food chain in your enterprise domain. I should have emphasized more on a Senior at this company is just that, a senior knowledgable person on the domain.
Low key really funny in a sarcastic way lmao great video
Important to know
But the years of experience on resume are sometimes necessary to get an interview
I needed this, thanks
Great video! Will you make a series as to how to became a developer and a skilled one at that?
If you are looking for more "career starting" content, I would look up Traversy Media's channel. Once you got a few projects and years under your belt, all this content here will hold more value.
@@618Developer ty
How did the contractor become a full time employee? What did you ask him on the interview?
Insightful.
Great video!!!!
The number of developers double every FIVE years, not on a yearly basis.
Correct, got my words mixed there
TRUTH BOMB. 💣
To be honest, you were already senior
Emmmmm......
When this channel goes viral never forget me because I need help
@Bacon Pancakes lol
You know who you are😂😂
"8 years of experience in one area" - you are deep expert in that area.
"8 years of experience in different projects" - you are wide area specialist.
Something like Full Stack Developer versus Back-End Developer.
What is better - depends on project.
Once in asp.net project I have tried to set up Remote Debugging at a Production server, but was blocked by security limitations of the server.
I was farce to debug an issue by 20 commits to Git with comments like "Debugging". Silly, but finally, the issue was solved.
Sometimes even experienced developers do silly mistakes. We all are still humans.
About me: 12 years experience in asp.net (full stack).
google stuff !
hehe, yep
Boring
How do I just get a 100k job in like 3 weeks? I know this stuff isn’t too hard to learn. I have basic development experience. Self taught.