……拖慢你的节奏——比如写 unit tests、做自动化 build、搭建 bug 数据库等等。这本书可能并不完全针对你现在的情况，但你可以去看看 Terrence Ryan 写的《Driving Technical Change》，里面讲了怎么说服团队其他人接受你采用的新方案的优点。
…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.
想找点思路的话，建议翻翻 Terrence Ryan 的《Driving Technical Change》。短小精悍，直奔主题：http://pragprog.com/book/trevan/driving-technical-change http://www.amazon.com/Driving-Technical-Change-Terrence-Ryan...
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...
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.
…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…
Oh this is really cool, I never heard of Driving Technical Change. I could definitely use the tips because I've been instigating some technical changes at work recently: svn to git, php to rails, big product features to independent small focused apps, etc. EDIT: I…
……拖慢你的节奏——比如写 unit tests、做自动化 build、搭建 bug 数据库等等。这本书可能并不完全针对你现在的情况，但你可以去看看 Terrence Ryan 写的《Driving Technical Change》，里面讲了怎么说服团队其他人接受你采用的新方案的优点。
…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.
想找点思路的话，建议翻翻 Terrence Ryan 的《Driving Technical Change》。短小精悍，直奔主题：http://pragprog.com/book/trevan/driving-technical-change http://www.amazon.com/Driving-Technical-Change-Terrence-Ryan...
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...
这本也值得一读：http://www.amazon.com/Driving-Technical-Change-Terrence-Ryan...
also worth reading: http://www.amazon.com/Driving-Technical-Change-Terrence-Ryan...
去年打折时买了这本书。现在还没抽空看完，但就我读过的大概半本来看，真是本神书。最后我顺手入了《Driving Technical Change》，因为感觉它不仅是从技术角度有用，放在各种通用场景下都挺实用。
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.
……他们喜欢从内部去修修补补解决问题。不过这需要极强的心态、情商和抗压能力，所以不是人人都受得了这套搞法。有一本讲这方面内容的好书叫《Driving Technical Change》。有些人你永远改变不了，直接无视就好。只要你能影响到足够多的人，你就有机会带来改变。前提是你心理素质够硬，不被负面情绪……
…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…
哇这个太赞了，我以前从没听说过《Driving Technical Change》。我绝对用得上这些技巧，因为最近在公司搞了些技术改造：svn 转 git、php 转 rails、大功能拆成独立小巧的专属 app 等等。补充：我……
Oh this is really cool, I never heard of Driving Technical Change. I could definitely use the tips because I've been instigating some technical changes at work recently: svn to git, php to rails, big product features to independent small focused apps, etc. EDIT: I…