Driving technical change

What Hacker News says

1. djKianooshJul 2016
   indeed, this is a path that is less frequently travelled. some people are wired in a way that they like fixing things from the inside. it takes a ton of emotional and psychological strength/aptitude though, so not everyone enjoys this approach.

   a good book that addresses some of this is Driving Technical Change. some people you will never change, and those you can ignore. if there are enough people that you can influence you have a chance to make a difference. as long as you're strong enough to not let the negativity bring you down, this all can be a rewarding path...

   Show morethread
2. mircealOct 2015
   also worth reading: http://www.amazon.com/Driving-Technical-Change-Terrence-Ryan...
   thread
3. dmlorenzettiMay 2014
   I would run through "Driving Technical Change" by Terrence Ryan for a few ideas. It's short and to the point:

   http://pragprog.com/book/trevan/driving-technical-change

   http://www.amazon.com/Driving-Technical-Change-Terrence-Ryan...

   thread
4. dmlorenzettiJan 2013
   Are you sure the problem is your programming skills, rather than, say, the way you manage expectations about your productivity? Or the way you present what you've done?

   If it was an honest performance review, they should have been more specific than "not completing enough work." Consider pressing for details about their performance expectations, and then either work to meet the metric they name, or work to convince them that the metric isn't the best one by which to measure your performance.

   It may not be a problem you can solve by just boning up on exciting new technologies. You may have to educate them on the merits of things you do that, in their opinion, slow you down-- like writing unit tests, automating builds, creating bug databases, or whatever.

   This book may not exactly address the situation you're in, but you might have a look at Terrence Ryan's "Driving Technical Change", which talks about how to convince others on your team of the merits of different approaches you've adopted.

   Show morethread
5. runevaultNov 2010
   Got this book in last year's sale. Still need to go back and finish it, but it's an amazing book from the ~half I read.

   Ended up picking up Driving Technical Change because it sounds useful in general, not JUST from a technical perspective.

   thread
6. mryanJul 2011
   Driving Technical Change sounds like an appropriate book. I have not read it, but it has been on my tech books wish-list for a while now:

   http://pragprog.com/book/trevan/driving-technical-change

   thread