Am 19.08.2011 19:22, schrieb Darren New:
> On 8/19/2011 9:40, clipka wrote:
>> It makes more sense to think of a piece of Software as a mold, or a
>> blueprint.
>
> Exactly. Software is 100% design. Once you have determined *exactly*
> what you want to build, you're already done. :-)

Well, not precisely - you still have to translate the design of what you 
want to build into a computer-palatable language. And it so happens that 
often you find out during this phase that you weren't clear about what 
*exactly* you wanted to build.

That aside, IT as a whole is about much more than just design; once you 
have the software, you need to test it, install it, teach people to use 
it, and other less exciting stuff. Sometimes business people forget 
about these things. It's like they pay an architect to design a new 
building for them, but forget the budget to actually build that thing 
(let alone to move from the old building to the new one).

But hey, they also seem to forget about all this stuff when it comes to 
company mergers. Yeah, sure, in the long run you may indeed get "synergy 
effects", but until then you're in for a lot of organizational overhead 
minimizing your productivity. And once you're breaking even you're 
possibly doing the next merger already.

Post a reply to this message