Re: Using refactoring to make code more testable Re: [refactoring] Using refactoring to make code more testable

--- On Tue, 10/13/09, Adrian Howard <[email protected]> wrote:

From: Adrian Howard <[email protected]>
Subject: Re: [refactoring] Using refactoring to make code more testable Re: [refactoring] Using refactoring to make code more testable
To: [email protected]
Date: Tuesday, October 13, 2009, 4:21 AM






 




    
                  On 13 Oct 2009, at 00:37, Schrecht wrote:



> Michael Charland <mike_ch_1@hotmail. com> wrote:

>

>> Along similar lines, how do i get people to add tests? Most of the  

>> people I work

>> with do not add any unit tests when submitting new code or fixing  

>> old bugs. It's

>> a pretty generic question, but any approaches would help.

>

> These people who work with you: do they work _for_ you, or _near_ you?

>

> If the former, obviously, you can command them.



Curiously enough I rarely find this works. You still need to do your  

option 2



> If the latter, you must convince them.

[snip]



Adrian
Yes, Adrian is correct. You can't command, you have to lead by example. As Richard has pointed out, you have a culture change, and culture changes take a very long time.If you are in charge: I would suggest starting with the most promising engineer(s) that report(s) to you, and if you have the skill, keep at it until that person is convinced; has had the 'aha' moment. Then have him/her train others, with you doing the same. Expect to take a couple of years; I'm not kidding. 
If you don't have the skill, get someone in that can actually do XP, it takes time and skill, but more than anything: patience and fortitude. Engineers aren't like factory workers, they will need to get 'there' on their own. But you have to be absolutely resolute on the direction; you have to know where you want to go and why. Most smart folks will eventually get it, if they respect your opinion and can see that you can 'walk the walk'.
If you have folks on staff that you try to help, and just aren't going to 'get it', you will have to 'manage them out'. This is really poisonous to an organization; and has to be done with care. Don't just give up on people, prepare to be surprised.
If they don't work for you: is the guy that everybody works for, 'on board'? If not, then you have a real problem.hope this helps,/h


http://quietstars. com  -  twitter.com/ adrianh  -  delicious.com/ adrianh




 

      

    
    
	
	 
	
	








	


	
	


      

[Non-text portions of this message have been removed]



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/refactoring/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/refactoring/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/