http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Even 'no brainer', obvious improvements that don't require learning investment can cause problems. I recently made a political mistake introducing CI to a codebase that is shared with developers from another company. They freaked out big time (despite agreeing to it in a meeting) and demanded that I remove it as It was 'nearly Christmas', so we must carry on using ad hoc builds from their developer machines to avoid problems. The code they produce really is the most stereotypical late 90s vb6 voodoo stuff 'intValue as string = false' 800 line methods levels of horror. The worst of of is that they don't even know how bad they are, choosing to spin necessary basic improvements to process and technique as dangerous so they can stay in their comfort zone. Mr ludd is still alive and well in the north on England and is working in IT http://ayende.com/3714/implementing-methodologies#comment4http://ayende.com/3714/implementing-methodologies#comment4Sun, 23 Nov 2008 16:11:29 GMTyes, you are right. But have you ever seen a methodology that works with an incompetent team? or put differently, have you ever seen an incompetent team succeed? http://ayende.com/3714/implementing-methodologies#comment3http://ayende.com/3714/implementing-methodologies#comment3Fri, 21 Nov 2008 22:25:17 GMTI agree. It is one thing for one developer to understand the gains from following a certain practice, but it is a completely different thing for that developer to make his colleagues understand the gain. It can take a while for some people to understand the value of thorough unit testing, although it is my impression that most people can understand this. But stuff like TDD, IoC, SOLID and even continuous integration seem to be more difficult to grasp, and I don't think all developers will understand and/or accept it all. I have certainly experienced this by working with my own colleagues. But I also think that if we give up on those colleagues, we are copping out. If we see ourselves as good software developers, we need to get better at passing on that learning we believe makes us good to people who might not seek out that learning by themselves and I think the notion of software apprentice could be really useful for this. http://ayende.com/3714/implementing-methodologies#comment2http://ayende.com/3714/implementing-methodologies#comment2Fri, 21 Nov 2008 21:51:57 GMTAre you seriously carrying your Air to bars with you now? http://ayende.com/3714/implementing-methodologies#comment1http://ayende.com/3714/implementing-methodologies#comment1Fri, 21 Nov 2008 19:54:47 GMT