3 ms·
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
by alabut 16y ago
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 wish we could start an HN book club, but I'm not sure how well the discussions would work virtually. I've attended and moderated a local UX design book club and gotten a lot out of it, so maybe a local HN chapter might work.
Also: HN won't let me add a reply to the bottom of this thread, maybe it's one of pg's new features to avoid flame wars?
- runevault 16y agoIt just came out a week or two ago, so it's brand new. I haven't started in on it yet (too many other things going on) but the table of contents screamed "Understand how to get past people's misconceptions/preconceived notions" which, I dunno about anyone else, but I could use all the time.