Hi Adrian thanks for your reply. I realise it was a mistake to tag this post as a beginner subject, as some of it may be too heavy for newcomers. I was thinking that it would be useful for beginners to see things to strive for that were not just technical. Thanks for the feedback - I have removed the beginner tag
I totally agree that not every point may be applicable to some environments, and that they are not mandatory to be successful. I usually notice a few of the traits stand out in people, but rarely do you see all of them in one person.
I agree, once you get the hang out of it, spending a few hours in an office you can notice the differences between "great developers" and the ones who are just there for "the job". They both are doing their job, but the first kind want to keep improving everything (themselves, their peers, their project) by changing everything (workflows, procedures, technologies, skills used ...).
A balance there always is, you cannot help everyone, be funny and still professional and do your tasks in the same time. So even if someone can have most of the skills, they don't apply to each situation, each day.
Future/new developers, don't worry, we are humans, we have bad days, we do mistakes.
You've made good points. Definitely, there is always a balance to be had. It may seem like some of the ideas contradict each other because of that balance. Like you say, there is right time and place for some things. Doing these things in the wrong situation could easily make you the opposite of great. :)
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.
Hi Adrian thanks for your reply. I realise it was a mistake to tag this post as a beginner subject, as some of it may be too heavy for newcomers. I was thinking that it would be useful for beginners to see things to strive for that were not just technical. Thanks for the feedback - I have removed the beginner tag
I totally agree that not every point may be applicable to some environments, and that they are not mandatory to be successful. I usually notice a few of the traits stand out in people, but rarely do you see all of them in one person.
I agree, once you get the hang out of it, spending a few hours in an office you can notice the differences between "great developers" and the ones who are just there for "the job". They both are doing their job, but the first kind want to keep improving everything (themselves, their peers, their project) by changing everything (workflows, procedures, technologies, skills used ...).
A balance there always is, you cannot help everyone, be funny and still professional and do your tasks in the same time. So even if someone can have most of the skills, they don't apply to each situation, each day.
Future/new developers, don't worry, we are humans, we have bad days, we do mistakes.
You've made good points. Definitely, there is always a balance to be had. It may seem like some of the ideas contradict each other because of that balance. Like you say, there is right time and place for some things. Doing these things in the wrong situation could easily make you the opposite of great. :)