"Jeffrey S. Sharp" wrote:
There's a big difference between writing code to
solve problems and being
a software engineer. Designing, coding, and compiling is only 40% of the
battle. Hopefully you're also spending some time planning and testing.
Also, don't forget the the heaping mounds of beaurocracy that you must put
up with, whether in the name of a software process or for just plain
corporate BS.
You mean like "If we needed it yesterday I'll ask for it
tomorrow"
--
Ben Franchuk --- Pre-historic Cpu's --
www.jetnet.ab.ca/users/bfranchuk/index.html