You’ve got a solid foundation as a junior developer. You know your way around the code, and maybe you’ve even shipped a few features. But when you’...
For further actions, you may consider blocking this person and/or reporting abuse
This was truly much needed post. The world is moving so fast, especially in Tech.
So true, glad you liked it!
many old devs that only use 1 framework think they are seniors for having 10 years coding, but actually they have 1 year experience 10 times
15 years ago you was senior if your code does work. Why do we increase requirements? What for?
This is 100% untrue. Senior have always been people that not only write code that works, but code that is performant, concise, easy to read and understand, and documented. Where do you get the idea that seniors only needed to get the job done, no matter how sloppy? This has never happened.
Mister, I worked with seniors and I know how they code. I don't mind if what you say would be true. Probably, we have different understanding of a good code.
Ok, so you probably work with self-proclaimed seniors that just because they've coded for 5 years they think they earned the title.
Mister, build your arguments on something provable or falsifiable, or you don't know how to argue.
I don't see a problem with my argument: There are people out there that think time (experience on the job) is what make a senior. This is only true if time is well spent. Maybe you don't know how to read English?
If that is your argument then you AGREE with my initial statement ;)
Who are you, MexiKode? I was arguing with Taqmuraz.
you are arguing in my comment, idioto 🤣😂
And? Does that mean I'm talking to you? I'm not.
get deported out of my space and notifications then
Each comment has its own "Reply" button. If I did not use the "Reply" on your comment, it is you the one who needs to get out of my space, idiot. You replied to me, I did not reply to you.
you don't know how threads work, uh genius?
How Threads Work
Simple, right? This is regardless of whatever notifications you received, "genius".
People who have life are tired running to just keep up with guys who live in computers.
Slow back, let us enjoy living. Or we end up living in the world where job requirements are too high for people with 50+ years experience
Great post thank you for this idea!
Glad you liked it!
That's good advice, thank you for your effort!
Glad you liked it!
Awesome advice✍🏾
Thanks!
Hello, I am the operator of servbay. I feel that your articles on techniques are very good. I would like to ask you to write some articles for us. Could you give me an email address to contact you?
I think this is a great article and covers a lot of ground, but lacks a little practicality. A junior Dev couldn't read this and implement everything and just become a senior.
The most important point for me that I think you've missed is 'Make mistakes and learn from them'. That is how you become senior on all your points above. Try, fail, retry. You get paid the big bucks for the mistakes you've already made. Because you won't make them again.
Further, from my experience building worldwide systems with infrastructure as code, seniority is also about being able to write code that others can use easily. If I build a system, it will likely outlive my tenure. It is therefore a signature of my work. Someone else will come along and have to refactor or extend and I want that to be as easy as possible for them, using effective coding best practices.
To summarize, you could add the following practical advice:
Make mistakes but learn from them. Don't make the same mistake twice. Document and admit failure and teach others so everyone can learn (comes into mentoring)
Implement and use coding best practices to keep your code readable and easy to maintain.
I’m so happy to see an element in business being covered. When I have mentored in the past, I taught not just business but the art of sales. It’s not the product the student was selling, it was their skills and ability to “find” the problem and already have the solution outlined.
Wonderful article
The important thing is to improve the code quality and reduce complexity in simple matter. Having a bulky and complex code is just unmaintainable and very costly for time efficiency in debugging. By making it more simple, your performance jumps and can help with your team when handling the code
@balrajola
Hello! I am a software engineer in Japan.
Thank you for your excellent article!
I would like to translate it into Japanese and share it on Zenn, an information-sharing community for engineers in Japan, is that OK?
If you don't mind, I'd appreciate a word of comment.
Very good post!
Man it is mind blowing thanks for this
Amazing article thank you 😊
Thank you for your wonderful post. really helpful.
So well explained!!
Bookmarking this for future reference .
This is the reality i needed and I've gotten, thank's @balrajola, remain blessed for this information.
I can only thank you for writing exactly what I am thinking!
Thank you!
This is really good. That part about emotional intelligence should be taken very serious.
This is some inspiring post you have!
Great post, thanks for this!
imagine telling this to a real estate dev lol
clarity at its peek. Thanx
Can you go from mid-level to senior in 6 months?
Helpful and recommendable 👏
Great advice
Amazing blog post. Thanks for sharing
What a great post. I should share this post to my colleagues.
Thanks:)
Actually very helpful post
Tweaking me at the next level, there is so much more to do
informative post, Thanks for sharing valuable information.
Great advice
thanks its a good read.
Nice content