I’m working with Esther this week on the book. We’re editing (and continuing to pair-write and pair-edit). Today, one of the things we addressed were the comments dealing with the people we name in the book. We hadn’t done a good job drawing our readers in to care about the people. So we’re fixing […]
A reader sent me email with this question: “We have a group of four people (3 developers and a tester). We work on 4 products, releasing one about once a month (each product is released once a quarter). The developers are devoted to one product when they’re developing, but have to fix problems immediately if
I just received this in email: Pledge Our company is completely and absolutely committed to quality. * * Except on time-critical projects and during adverse cash-flow situations. When else would you need to be committed to quality? (Not to zero defects, but to an appropriate level of quality for the product you’re trying to
I’m catching up with my blog reading, and discovered these two gems: Staying Awake has links to comparing the lack of sleep with too much alcohol. Since I’m a one-drink-one-drunk person (well, ok, not drunk, but certainly not sober), this one resonated with me. And via Steve Norrie’s blog, I discovered this oldie-but-goodie, Personal Chemistry
I’m excited to announce that Roy Osherove’s interview with me is now posted on IT Conversations. Here’s the link to the interview. Roy interviewed me about the hiring book, and of course we segued into project management and management issues. Enjoy!
In Greg’s provocative comment, he says, “The idea that contributor initiatives are a drag on an organization speaks more to the insecurity of the management than to its skills.” I’ve been noodling that comment since I received it. I agree with Greg that some managers are insecure enough to insist that they make all
Read The Graphing Calculator Story. (Thank you to Obie Fernandez for finding this gem. Some ideas that stood out for me: The secret to programming is not intelligence, though of course that helps. It is not hard work or experience, though they help, too. The secret to programming is having smart friends. …he told
I’m looking for a reference to something I thought I read but can no longer find. Technical people can work up to 6 hours a day on technical work. They may be at work longer, reading email, going to meetings, getting coffee, but they can only effectively do 6 hours of technical work a
I’ve had several discussions about maintenance in the past few days. I’m beginning to think I have a different definition of maintenance than other people do :-). For me, maintenance is fixing problems in code. Maintenance is short, small, well-contained and code-based, and should be fixed by the developer(s) who created the problem. So
Due to incredible volume of spam comments, I’m moving to a new commenting system. The new one is installed. I’m working on importing the old comments to this system. In the meantime, it’s ok to leave comments here.