Thanks for the Article @javinpaul
, do you have any advice for average developers, how they can get to the part where the automatically think like good developers.
@Peace Dube, good questions, while I am also an average programmer, but I can share a few things which I have seen good developers doing and learned from them
Think through ability - ask questions, even silly questions are ok, they make your mind think
Devil is always in detail and asking question help you to figure that out earlier
Don't commit time but ask for an analysis.
Be in good company - if you want to become better, spend time who is better than you.
I'm sorry, but "don't commit time" sounds like bad advice.
We have a junior dev that refuses to give story point estimates & his reasoning is always "I need some time for analysis first" (even when seniors & PMs have broken the task into simple statements that require no thought).
That dev has been parked on our documentation project, and if that ever dries up, they'll be fired.
A good developer needs to learn how to forecast time, manage expectations & deliver on time.
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.
Thanks for the Article @javinpaul , do you have any advice for average developers, how they can get to the part where the automatically think like good developers.
@Peace Dube, good questions, while I am also an average programmer, but I can share a few things which I have seen good developers doing and learned from them
And, you can also find some more tips on my article javarevisited.blogspot.com/2014/01...
And, May be other great guys here can chip in and advice so that we all can learn from each other.
I'm sorry, but "don't commit time" sounds like bad advice.
We have a junior dev that refuses to give story point estimates & his reasoning is always "I need some time for analysis first" (even when seniors & PMs have broken the task into simple statements that require no thought).
That dev has been parked on our documentation project, and if that ever dries up, they'll be fired.
A good developer needs to learn how to forecast time, manage expectations & deliver on time.