Very detailed comment Ken. I see that you've read all the article, that's great.
Your comment is divided into 4 paragraphs, for paragraph #:
1- If junior and newbies are getting frustrated due to my article, then there's 2 options:
a- close the tab and read another LaLaLand article
b- read it and keep working until they achieve these traits, and they will be surely happy with what they will see.
2- No, they are not in the same company. Besides, it depends on how ambitious these engineers are and how smart they are and how they behave.
3- They are so engulfed, but with great time mamagement, they know how to manage their time and meet up with clients. Besides, an engineer that doesn't know how to communicate with people, will have great issues my friend. At work, it's not about how good you are, it's all about connections.
4- Once an engineer is in the Senior level, if he's ambitious enough, he should think about a managerial level.
Developing software solutions for too many years. The majority of my time has been either Managing Software Development efforts or as a Software Quality Engineer.
Sorry, but no I didn't read all the articles linked. I used my 20+ years of experience as a reference for this discussion. Now I'm not saying that individuals shouldn't strive to fall into these buckets. All i'm saying is that most developer will not achieve 60% of these traits and still have a successful career.
For the entry level, bootcamp enrolled or graduates or 1-to-3 year junior software developer you've set a bar that is 10 to 15 years out for an individual. Bolstering "Traits" like this need to come with a warning label that you are talking about developers that have been performing the work for a decade plus. And some of those developers will go by a title of Architect, Staff or Senior developer.
Another fallacy to drop is Senior developers should eventually move into management. If you are at the right company there is a technical growth track and a management growth track. There is no reason to fall in to the management world because traits 5 & 8 are strong, but you have a passion to stay a Keyboard Cow{boy|girl}.
What comes easily, goes easily.
Newbies, junior or even Senior should know that they must do the hard things in order to grow. Therefore, this list should motivate them. If you think it doesn't, then this is your opinion and I respect it. We can keep arguing till tomorrow. But I'm busy, I have more important things to do.
With 20 years of exp and you respond with such a comment, well..., let me teach you something:
There's 2 types of experience:
A- Routine, keeps repeating the same task each and every day.
B- out of the comfort zone. Always learning new stuff, and accept new challenges.
Notice, that both will have the same number of years of experience.
Developing software solutions for too many years. The majority of my time has been either Managing Software Development efforts or as a Software Quality Engineer.
I thought this was an open discussion of opinions of how to grow as a developer? But if you want to end the discussion because it is below your time allotments, then so be it.
As for your lesson . . . there was no teaching.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Very detailed comment Ken. I see that you've read all the article, that's great.
Your comment is divided into 4 paragraphs, for paragraph #:
1- If junior and newbies are getting frustrated due to my article, then there's 2 options:
a- close the tab and read another LaLaLand article
b- read it and keep working until they achieve these traits, and they will be surely happy with what they will see.
2- No, they are not in the same company. Besides, it depends on how ambitious these engineers are and how smart they are and how they behave.
3- They are so engulfed, but with great time mamagement, they know how to manage their time and meet up with clients. Besides, an engineer that doesn't know how to communicate with people, will have great issues my friend. At work, it's not about how good you are, it's all about connections.
4- Once an engineer is in the Senior level, if he's ambitious enough, he should think about a managerial level.
Sorry, but no I didn't read all the articles linked. I used my 20+ years of experience as a reference for this discussion. Now I'm not saying that individuals shouldn't strive to fall into these buckets. All i'm saying is that most developer will not achieve 60% of these traits and still have a successful career.
For the entry level, bootcamp enrolled or graduates or 1-to-3 year junior software developer you've set a bar that is 10 to 15 years out for an individual. Bolstering "Traits" like this need to come with a warning label that you are talking about developers that have been performing the work for a decade plus. And some of those developers will go by a title of Architect, Staff or Senior developer.
Another fallacy to drop is Senior developers should eventually move into management. If you are at the right company there is a technical growth track and a management growth track. There is no reason to fall in to the management world because traits 5 & 8 are strong, but you have a passion to stay a Keyboard Cow{boy|girl}.
What comes easily, goes easily.
Newbies, junior or even Senior should know that they must do the hard things in order to grow. Therefore, this list should motivate them. If you think it doesn't, then this is your opinion and I respect it. We can keep arguing till tomorrow. But I'm busy, I have more important things to do.
With 20 years of exp and you respond with such a comment, well..., let me teach you something:
There's 2 types of experience:
A- Routine, keeps repeating the same task each and every day.
B- out of the comfort zone. Always learning new stuff, and accept new challenges.
Notice, that both will have the same number of years of experience.
I thought this was an open discussion of opinions of how to grow as a developer? But if you want to end the discussion because it is below your time allotments, then so be it.
As for your lesson . . . there was no teaching.