
08-16-2009, 07:14 PM
|
Registered User
|
 |
Join Date: Jan 2009
Posts: 611
|
|
I'm not development-stupid if that is where you're getting at. It always depends on the severity of the problem. If a car gets a scratch, I doubt its easier to change that entire section, rather than just having the body shop "repair" the location of the scratch.
Now if a car had several severe issues and is a burdon, it'd be easier to buy a new car rather than fix that one.
Same with Era, Era has problems, but isn't at the point where it'd be easier to make a new Era, rather than repair this one. This is what separates the constructors, from the conductors. Developers will often do unnecessary, insignificant and often mundane things if left to work based on their will. Most of you need people to tell you what to do, and how it all fits together.
This is why I'd prefer my manager either be a conductor, or both a constructor and a conductor. Never just a constructor, the ability to assess a situation, finding the problem and formulating the most efficient way of amending the matter. Whether he amends it himself, or directs a "constructor" to do so.
Sales is a constructor
Ocelot is a conductor
Neither is both. |
|
|