On 8/19/2011 15:05, clipka wrote:
> 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's part of being sufficiently exact. If you're sufficiently exact, the 
translation step can be automated. (For example, we call that "a compiler". ;-)

> 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.

There is that. Altho I'd classify testing it (in terms of "does this meet 
the spec" and not in terms of "do the users like what we spec'ed enough to 
pay us") as part of the design. It's ensuring the design is right.

> doing the next merger already.

Heh.

-- 
Darren New, San Diego CA, USA (PST)
   How come I never get only one kudo?

Post a reply to this message