What Corporate Projects Should Learn from Open Source

Aside

OnLamp had an excellent article yesterday called What Corporate Projects Should Learn from Open Source. The articles pretty long, but well worth the read. While there are obvious differences in the two types of projects (like budgets and deadlines), I still believe that corporations can move closer to the OSS model of development and get major productivity increases.

Transparent Commodity Infrastructure and Web 2.0

Tom the Architect pointed me over to this article called Transparent Commodity Infrastructure and Web 2.0. Excellent piece.

I especially like this quote here:

Let me use an example: back in 1998 if you were building a web-based startup, you were probably running on Solaris/SPARC and using an Oracle database. You were also likely to be running on some sort of a Java servlet engine (though there were exceptions, this was again the leading edge). This huge apparatus usually required at least 1 of the following: DBA, sys-admin, release manager, and build manager– nevermind all of the consultants and vendor people that it took to solve problems that arose from trying to get everything working together.

Fast forward to 2005. Anyone still using Solaris/SPARC for web apps is either a moron or a depressed Sun shareholder. MySQL and Postgres are now considered “enterprise-grade,” and if you should be so masochistic as to still want to do Java development on the app-tier, you’ve got Tomcat, Jetty, and even JBOSS available to you on your platform of choice.

I couldn’t agree more. So many companies stuck in the 90’s … excellent article and worth a full read.