Great video, Thanks! Conclusion from the final part: 1. Be patient with the time in the trenches 2. Develop your soft skills 3. Develop your technical skills 4. Become a decision maker 5. Practice interacting with others on the team.
Something that is really important to keep in mind when moving onto the "decision making" phase as a jr developer looking to take on more sr roles: Do it in a way that does not outshine those above you. I hate that this is a thing, but people get jealous and threatened when an inexperienced upstart begins trying to call the shots. There are ways to sound confident and capable, but also subtly so, with humility. Do not overrule anyone who is more senior than you, and when you make suggestions, word them as just that: suggestions (taking on the structure of "here are some ideas rolling around in my head, but what are your thoughts?" so they always have room to provide input on your ideas). Be participative and eager to contribute, and don't shy away from suggesting ideas, but tread very carefully if your eagerness ever puts you at a crossroads against your seniors. It's unfortunately the game we have to play, but if you participate by uplifting other people's ideas while contributing your own, and at the same time making sure you think hard before you disagree with your seniors or do anything that outperforms them, and I think your path to seniordom will be less rocky.
Coding is not enough. You’re soft skills will go a long way. You can be a JavaScript/Python/C/C++/Java god, but without the soft skills… You’re not going to go far.
This video is very realistic and i personally learnt a lot from it. You know that part when you said at the end of the meeting you then unmute your mic and say 'Alright bye everyone😂😂😂' I could totally relate. Thanks for the advice man. Much appreciated
Thank you Travis as always!❤ Someone told me "Smile will put you way ahead of the competition". Soft skills aren't emphasized enough, thanks for doing it!!
As softskill and in written explanations i use following technique: I use the technique from novels/history, I start with the action and only after involving the reader I start explaining backgrounds. Means not like Dickens where he explains first the weather, the way, the hills and gets to action only after 5 pages. Like I start first with conclusions and then details and how I got from some assumptions to the conclusions. Means i formulate everything to reach the conclusions, then rewrite it with the practical things in the beginning and then the boring details step by step.^^
I always love your content as a software engineer myself, it has been like more than 2 years since me wanting to start a RUclips channel myself but I'm still in doubt. or should I say procrastinating.
Great video. For all of these tips though, I think you kinda need a base line level of technical knowledge to pull off any of them effectively. For example, you can interact with your colleagues and ask them "How's your work? What've you been up to? Are you stuck at something?" But without a certain level of knowledge, once they answer your questions, you would have no idea what they're really talking about, and how to follow up, and the convo would be over. Same with decision making and soft skills. You need knowledge to even start speaking up and saying things that do matter. I myself am far from a "good talker", but I find that when I do have the relevant knowledge and experience, it becomes much easier for me to just speak up what I know and what I think - I don't have to fake any particular emotion or try to come up with something to say when I don't have anything to say. Which is why, I totally agree with the idea that you really need to possess firm fundamentals, and to acquire a breadth of knowledge. Even though the idea is try to improve upon all these areas at the same time, I think a good starting point would still be to first work on your techincal knowledge.
I want to ask you about the "promotion ladder" in IT, from your perspective, how long after being a junior can you become a mid, then mid -> senior, then an architect? One year for each position is a good way? We discuss our information bubble, so I'm reaching for the opinion of an outside "expert" ;)
I think in this vid you're explaining some stuff but in my opinion it's far from reality, or in my team it's done differently because of some prerequisites. If I will have time will return and explain in more detail.^^
Senior developers if not lead developers, are the real problem the software industry has become so impossible to get your feet into. Your video will not make sense because you might have 4 years in a project then after you switch job you understand you are a junior again. It has nothing to do with time, it has everything to do with the process. Soft skills are not needed at all. Technical skills are also not needed because once you switch job and project, you will soon realize you will not be able to understand most of the stuff. Also decision making and interaction those are not a problem at all, in fact I have met seniors who rarely interacted and did most of the job. The only skill you need, is to learn how to read someone else's code. Everything else is not that important, because probably someone else has already been hired in the company and has been working for years there, so you just need to read their code. Just try to start with small open source projects.
idk man. In my humble opinion as discussed in the video, everything comes back to soft and hard skills. If you don't have technical skills, how would you read others' code? If you don't have soft skills then how would you ask others to explain you their thought process when working on that snippet or feature, because it is soft skills that makes you look as an interrogative (some called it asshole) or curious during these phases.
Great video, Thanks!
Conclusion from the final part:
1. Be patient with the time in the trenches
2. Develop your soft skills
3. Develop your technical skills
4. Become a decision maker
5. Practice interacting with others on the team.
Something that is really important to keep in mind when moving onto the "decision making" phase as a jr developer looking to take on more sr roles: Do it in a way that does not outshine those above you. I hate that this is a thing, but people get jealous and threatened when an inexperienced upstart begins trying to call the shots. There are ways to sound confident and capable, but also subtly so, with humility. Do not overrule anyone who is more senior than you, and when you make suggestions, word them as just that: suggestions (taking on the structure of "here are some ideas rolling around in my head, but what are your thoughts?" so they always have room to provide input on your ideas). Be participative and eager to contribute, and don't shy away from suggesting ideas, but tread very carefully if your eagerness ever puts you at a crossroads against your seniors. It's unfortunately the game we have to play, but if you participate by uplifting other people's ideas while contributing your own, and at the same time making sure you think hard before you disagree with your seniors or do anything that outperforms them, and I think your path to seniordom will be less rocky.
Very true
Coding is not enough. You’re soft skills will go a long way. You can be a JavaScript/Python/C/C++/Java god, but without the soft skills… You’re not going to go far.
soft skills what u mean?
Yup, it takes so much time to become extremely skilled dev. I see people doing so much better with just soft skills.
You are a great lecturer. I like pauses in your speech and how you present your logic.
Excellent, Crisp, clean, usable talk to take from point A to Point B. Good job expert. Thank you.
This was a great video!!!! I'm in that phase of wanting to rush the process of being a mid-developer. Great insight!!
This video is very realistic and i personally learnt a lot from it. You know that part when you said at the end of the meeting you then unmute your mic and say 'Alright bye everyone😂😂😂' I could totally relate. Thanks for the advice man. Much appreciated
Thank you Travis as always!❤ Someone told me "Smile will put you way ahead of the competition". Soft skills aren't emphasized enough, thanks for doing it!!
As softskill and in written explanations i use following technique:
I use the technique from novels/history, I start with the action and only after involving the reader I start explaining backgrounds. Means not like Dickens where he explains first the weather, the way, the hills and gets to action only after 5 pages.
Like I start first with conclusions and then details and how I got from some assumptions to the conclusions.
Means i formulate everything to reach the conclusions, then rewrite it with the practical things in the beginning and then the boring details step by step.^^
I tried to explain why I used mongoDB once and I panic, started shaking and thought I was gonna faint! For me soft skills are the hardest
Thanks a lot for this coding insight..Am still new to programming and now learning JavaScript .Am energized by this video
Great videos .I could relate to almost all of the thing you said as jr.developer.
I always love your content as a software engineer myself, it has been like more than 2 years since me wanting to start a RUclips channel myself but I'm still in doubt. or should I say procrastinating.
Start it up! And I’ll subscribe 👍🏾
Just do it
Great video.
For all of these tips though, I think you kinda need a base line level of technical knowledge to pull off any of them effectively. For example, you can interact with your colleagues and ask them "How's your work? What've you been up to? Are you stuck at something?" But without a certain level of knowledge, once they answer your questions, you would have no idea what they're really talking about, and how to follow up, and the convo would be over. Same with decision making and soft skills. You need knowledge to even start speaking up and saying things that do matter. I myself am far from a "good talker", but I find that when I do have the relevant knowledge and experience, it becomes much easier for me to just speak up what I know and what I think - I don't have to fake any particular emotion or try to come up with something to say when I don't have anything to say.
Which is why, I totally agree with the idea that you really need to possess firm fundamentals, and to acquire a breadth of knowledge. Even though the idea is try to improve upon all these areas at the same time, I think a good starting point would still be to first work on your techincal knowledge.
Thanks for the tips ❤
Good 👍 video
Thank you so much for always inspires
I want to ask you about the "promotion ladder" in IT, from your perspective, how long after being a junior can you become a mid, then mid -> senior, then an architect? One year for each position is a good way?
We discuss our information bubble, so I'm reaching for the opinion of an outside "expert" ;)
amazing knowledge thank u so much
Great content, thank you
Great video thanks
The video which I was looking for
I think in this vid you're explaining some stuff but in my opinion it's far from reality, or in my team it's done differently because of some prerequisites. If I will have time will return and explain in more detail.^^
Please do!
Please what are your recommendations for books on soft skills or communication
Hi thanks for valuable tips, how old was you when you started coding?, because i want to do same as you did but i feel like i am over age
I was 34
Ty 🙏🏾
There you go, 500 on the likes 👍
Thank traves ❤
very good vid
So i was a Sr Jr just in first day 😅
❤❤
Senior developers if not lead developers, are the real problem the software industry has become so impossible to get your feet into.
Your video will not make sense because you might have 4 years in a project then after you switch job you understand you are a junior again.
It has nothing to do with time, it has everything to do with the process. Soft skills are not needed at all.
Technical skills are also not needed because once you switch job and project, you will soon realize you will not be able to understand most of the stuff.
Also decision making and interaction those are not a problem at all, in fact I have met seniors who rarely interacted and did most of the job.
The only skill you need, is to learn how to read someone else's code.
Everything else is not that important, because probably someone else has already been hired in the company and has been working for years there, so you just need to read their code.
Just try to start with small open source projects.
idk man. In my humble opinion as discussed in the video, everything comes back to soft and hard skills. If you don't have technical skills, how would you read others' code? If you don't have soft skills then how would you ask others to explain you their thought process when working on that snippet or feature, because it is soft skills that makes you look as an interrogative (some called it asshole) or curious during these phases.