Comments on: Why Your Manager Doesn’t Like To Throw Away Work (And You Do) http://www.codesqueeze.com/why-your-manager-doesnt-like-to-throw-away-work-and-you-do/ Ideas for building efficient developers and software Mon, 30 Jan 2012 11:03:44 -0500 hourly 1 By: Jeremy N http://www.codesqueeze.com/why-your-manager-doesnt-like-to-throw-away-work-and-you-do/#comment-971 Jeremy N Mon, 14 Jan 2008 16:49:43 +0000 http://www.codesqueeze.com/why-your-manager-doesnt-like-to-throw-away-work-and-you-do/#comment-971 Lack of Trust = Micro-management = Ineffective. Lack of Trust = Micro-management = Ineffective.

]]> By: devtrench http://www.codesqueeze.com/why-your-manager-doesnt-like-to-throw-away-work-and-you-do/#comment-970 devtrench Mon, 14 Jan 2008 14:47:24 +0000 http://www.codesqueeze.com/why-your-manager-doesnt-like-to-throw-away-work-and-you-do/#comment-970 Nice post, Max. For me it's always been #1, lack of visibility that is the most problematic. I used to work for a university where my manager knew more about corn than he did software (it was an Ag campus). It was quite frustrating, especially when he was the one making software decisions. That was one of the main reasons I quit :) I guess that kinds of ties in with your last paragraph: Managers-Trust-Visibility+Ego = No Employees Nice post, Max. For me it’s always been #1, lack of visibility that is the most problematic. I used to work for a university where my manager knew more about corn than he did software (it was an Ag campus). It was quite frustrating, especially when he was the one making software decisions. That was one of the main reasons I quit :)

I guess that kinds of ties in with your last paragraph: Managers-Trust-Visibility+Ego = No Employees

]]> By: ActiveEngine Sensei http://www.codesqueeze.com/why-your-manager-doesnt-like-to-throw-away-work-and-you-do/#comment-969 ActiveEngine Sensei Mon, 14 Jan 2008 12:51:43 +0000 http://www.codesqueeze.com/why-your-manager-doesnt-like-to-throw-away-work-and-you-do/#comment-969 I think your issue about developers learning to pick their battles is well thought out. Many developers have unfortunately isolated themselves from what drives people's decision making process. Many times their desire to refactor have the worst timing. I had a very talented developer fall into the chronic "we'll make it extensible and it will save us money" syndrome, and nearly kill a project because all the easy things that the customer wanted to see early were eschewed because it was not important for the future. Had the customer seen a few screens and some of their process modeled quickly, they would have gotten on board with the other ideas that the developer wanted to pursue. His ideas were well worth, but his timing and ability to see what was important to the person paying the bills was way out of whack. I have some similar posts concerning this issue: http://activeengine.wordpress.com/2007/11/21/clarity-of-thought-only-comes-from-practice/ http://activeengine.wordpress.com/2008/01/10/the-art-of-letting-bad-things-happen/ I think your issue about developers learning to pick their battles is well thought out. Many developers have unfortunately isolated themselves from what drives people’s decision making process. Many times their desire to refactor have the worst timing.

I had a very talented developer fall into the chronic “we’ll make it extensible and it will save us money” syndrome, and nearly kill a project because all the easy things that the customer wanted to see early were eschewed because it was not important for the future. Had the customer seen a few screens and some of their process modeled quickly, they would have gotten on board with the other ideas that the developer wanted to pursue. His ideas were well worth, but his timing and ability to see what was important to the person paying the bills was way out of whack.

I have some similar posts concerning this issue:

http://activeengine.wordpress......-practice/
http://activeengine.wordpress......gs-happen/

]]>