DEV Community

Discussion on: Top 10 Traits of Legendary Developers

Collapse
 
scriptmunkee profile image
Ken Simeon

You've certainly got a Pie-in-the-sky view on things when defining Legendary Developer Traits. And with this kind of definitions you're touting, you are setting up newbies & junior engineers for unrealistic achievements.

Most of the top 10 traits you describe relate to engineers that have been within the same company, technology stack and code base for many many many years. I've worked with engineers that resemble your list of traits, but not everyone has lived up to or could achieved this level of glory as you describe.

Two of the biggest follicles you've pointed out are # 5 & # 8. Because when you boil everything down to the drive of your legendary developer, they are so engulfed in learning & never giving up that they can't or wont meet a timeline they've predicted for a delivery.

Plus, its very rare for a top level engineer to be engage with customers or clients. The majority of Sr Engineers will never engage with a customer or client even if they have good communication skills. Not to say that I haven't seen plenty engaged with service providers because they are working on an integration. But a well engaged and commutative legendary engineer doesn't have much time for project delivery.

Collapse
 
hussein_cheayto profile image
hussein cheayto

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.

Collapse
 
scriptmunkee profile image
Ken Simeon

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}.

Thread Thread
 
hussein_cheayto profile image
hussein cheayto

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.

Thread Thread
 
scriptmunkee profile image
Ken Simeon

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.