You actually did development? In my current IT job, 90% of it is installing/upgrading vendorware (closed or open, as long as it's Java-based). The other 10% i

You actually did development? In my current IT job, 90% of it is installing/upgrading vendorware (closed or open, as long as it's Java-based). The other 10% is writing the pieces of glue code needed to incorporate the new vendorware with the existing vendorware. That's not what I call development. It's closer to a web-centric, glorified sysadmin job. Now that I think of it, the real problem with enterprise software and the IT departments that rely on them is more about the fact that IT departments don't seem to actually create much software, thus they're not that good at it. This means that when talented people start working there with the hopes that they'll get to create something interesting (or at least in an interesting way) and they find out that the organization won't allow them to do anything novel, they leave.