Comments for Katherine Cook

Comment on Effective Developer/Management Communication by Charles Mack

Charles Mack — Tue, 24 Jan 2012 17:29:29 +0000

Obviously communication is key. If you have read the Mythical Man Month, I highly suggest it. It is cornerstone for any software engineer, despite being written in the 70s. There is constantly a juggling act between paying down technical debt for existing systems and creating new functionality. Developers typically want to reinvent the entire wheel in an effort to pay down the technical debt. Version 2 is always over-promised, under delivered, and often a failure. Non-technical management only cares technical debt if it is slowing development of new functionality or if customers are complaining about non-functional requirements (speed, accuracy, etc).

I think this can be balanced with test suites. With large test suites in place, including but not limited to GUI functional, unit tests, or regression suites, one can move a light speed taking high risk of paying off that technical debt. While it does feel like steering a ship while rebuilding its hull, at least the ship is reaches its destination.

I have always committed to being as open and communicative as possible and willing to take risks to meet a goal, either internal or external. If development is not taking risks, developers, thus the company, are not innovating. If a company is not innovating, management is failing.

Comment on Summer by Richard

Richard — Mon, 29 Jun 2009 19:57:28 +0000

More Blogging please!!!!!

Imagine the old ovaltine commercials except for blogging!

Comment on Effective Developer/Management Communication by Luke Barton

Luke Barton — Wed, 24 Jun 2009 08:39:37 +0000

Perfect. Absolutely spot on. I have seen this problem more than I’d like to.

I’d like to draw attention to the fact that I’ve seen more developers able to identify these issues; including the causes, than managers.

Comment on Effective Developer/Management Communication by bagherra

bagherra — Mon, 22 Jun 2009 20:22:28 +0000

That was absolutely amazing. Everything you have to say is spot on. I think it is a tricky balancing act to determine what level of granularity is just right for communicating intent up, though. If you give too little, you are accused of being lazy…you give too much and they feel inundated with information that is intended to confuse them (often termed “gobbledy-gook”).

Very poignant and well thought out.

Comment on Effective Developer/Management Communication by Promises and White Elephants :: Robert Stackhouse

Promises and White Elephants :: Robert Stackhouse — Mon, 22 Jun 2009 19:44:48 +0000

[...] student I know penned a very eloquent article on the failures of communication between development and management. The only thing I have to add [...]