"Don’t tell people what to do, show them. Do what you expect other people to do, yourself, first, and then let them see why what you are doing is beneficial.
"You can argue and try to cajole people until you are blue in the face, but if you really want to inspire people, if you really want to move them to action, you have to lead by first showing them the path to take and generate the results to prove that your way is best.
"If you want developers on your team to write better code, you have to start writing better code yourself and you have to write such good code that the effort you put into that code is apparent. Only then can you credibly produce a set of coding standards that will help others to write good code as well. Once they see your code, they should be inspired to write code of the same quality and understandability.
"If you want developers on your team to write unit tests or practice test driven development, you had better be not only doing the same, but having tangible results that show what you are recommending is the best way to proceed. This will require some commitment and pragmatism, so that you aren’t just preaching something because you heard or read this was the best way to do things.
"If you want developers on your team to work on developing their skills and personal development, you had better be a shining example of the same. You should spend more hours than anyone else learning new things and sharing what you have learned with others. You should be the one writing up blog posts that share what you are learning and inspiring others to do the same."
Great advice, read the rest here:
http://simpleprogrammer.com/2015/05/25/some-advice-on-becoming-a-lead-developer/
"You can argue and try to cajole people until you are blue in the face, but if you really want to inspire people, if you really want to move them to action, you have to lead by first showing them the path to take and generate the results to prove that your way is best.
"If you want developers on your team to write better code, you have to start writing better code yourself and you have to write such good code that the effort you put into that code is apparent. Only then can you credibly produce a set of coding standards that will help others to write good code as well. Once they see your code, they should be inspired to write code of the same quality and understandability.
"If you want developers on your team to write unit tests or practice test driven development, you had better be not only doing the same, but having tangible results that show what you are recommending is the best way to proceed. This will require some commitment and pragmatism, so that you aren’t just preaching something because you heard or read this was the best way to do things.
"If you want developers on your team to work on developing their skills and personal development, you had better be a shining example of the same. You should spend more hours than anyone else learning new things and sharing what you have learned with others. You should be the one writing up blog posts that share what you are learning and inspiring others to do the same."
Great advice, read the rest here:
http://simpleprogrammer.com/2015/05/25/some-advice-on-becoming-a-lead-developer/
No comments:
Post a Comment