Practice makes perfect. This is the key to success, but it's not enough. In fact, having solid technical chops isn’t the only thing needed to have ...
For further actions, you may consider blocking this person and/or reporting abuse
Utopia or dystopia? 😄
I've been a software developer practically my whole life, and I've never seen anyone with more than 2 or maybe 3 of those qualities. A person comprising all those 10 qualities could only be some form of advanced human.
In my opinion, there shouldn't be a list of any kind to distinguish people's qualities. There's more to it than a simple list, and human beings are already being treated as drones, especially in large companies.
Regarding the list, I can relate to the following numbers: 1, 4, 6 and 7.
I consider myself a perfectionist and am therefore never completely satisfied with my work.
Although I might be lacking in social skills, I enjoy helping my coworkers and expect the same in return.
It's quite common for developers to gain superficial knowledge and consider themselves experts in some particular field. I've seen lots of network "experts" who don't even know how TCP sequencing works. I strive for deep understanding of anything I might be working on. Sometimes the comprehension is beyond me, but that's not an excuse to quit trying or asking for help.
This closely relates to both 1 and 6.
Putting too much pressure on people or trying to reduce a person to a set of numbers is, in my opinion, just plain wrong and could eventually lead to burnout.
Thanks for the article, It's a good overview of highly praised developer skills. Although I personally don't agree with everything stated here, I always appreciate people investing their time in writing.
Thanks You
You've just contradicted yourself. You've never saw someone has more than 3 traits, then you say that you have 4 of these traits 🤔
You just need to open something called Youtube and search for Brackeys, Sykoo.... and you can easily see that these people have at least 6 of these traits.
I agree that big companies treat people as robots.
About the "expert" thing, it's others who have the right to judge whether you're an expert or not. You're right, some people say they're expert, while they miss a lot of information. This mentality prevents them from achieving huge success.
Thank you. Also, I appreciate your time reading the article and writing the comment.
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.
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.
There's more to life than being a devoper. When you hear people in their 30s dying of heart attacks, you begin to question your reasoning. It's unhealthy to strain yourself to the brink of death for the sake of some symbols on the screen. Everyone doing software development should learn to compartmentalise and devote some of their time to anything but sitting in front of the screen. I'm sorry if this is offensive to you, as an author of this article, but you're subtly encouraging young developers to take the path of self-destruction and burnout. When you're just starting, you tend to submit and work long hours to gain as much experience as possible. Doing all this just to impress your boss is unacceptable and I find it obnoxious. What you've written in this article would have been a benevolent guide for perfectionism striving developers in the 90s era. Things are different now, and CEOs and alike are asking way to much from their employees. The other day at work I had a pleasure of meeting a developer who can't even sit down. He's been neglecting his health, and now he has to go through physical therapy. Had he been more observant of his back pain, he would have taken action much sooner.
This is just the obvious and unfortunately realistic overview of how the word is setup in the 21st century.
Work to impress yourself only. Otherwise, you won't succeed.
The article seems like the continuation of a 10x Engineer discussion. Unfortunately, young unfledged minds can take some of your advice personally and think of themselves as failures because they are not "110% productive."
Or, you can think of it in a positive way and say: "this article will make every newbie to work harder every day, or just keep the same pace since he/she is on the right track"
I don't know that I can recommend being a legendary developer. If you call my references (the ones who will agree in the first place), you will hear "one of the smartest people I have ever met" and "truly a rockstar developer" but when asked if they would hire me again, "hell no." I don't every try to be an asshole, but apparently I sometimes come across as one and if I don't get the autonomy I need I guess I become I real pain in the ass. There's many things that make a great developer and lots of wildcard situations which can paint every good thing you did in two years in a bad light is what I have discovered.
It's their loss. Search for another job where they appreciate every single thing you do. And trust me, you will shine there and tell all the people who didn't accept you: "Fu** you"