Teamwork and Failures
There's more than just a programmer in a running system.
My current project (well, the latest project, since it ends yesterday) involves an ad hoc team during development and usage. Since most of the development task are mine, I didn't really feel the team until the system needs to be deployed and run.
Development and deployment are a piece of cake, since using Visual Studio 2005 and ClickOnce technology really simplifies both. But running the system have its own problems.
The problem mostly came from unknown (until now) network performance hit using WCF NetTcpBinding. I've been digging the whole code to find out the annoying line (or lines) to no avail. Hence, the system developed wasn't able to serve its purpose.
Several team member got a morale hit when the system crashed after 10 minutes of usage, which never happens during testing. But some other still have a strong confidence that the system will work, assuming that many conditions during testing is fulfilled. The whole team structure supported each other until the end, thus ensuring the whole system running.
So, team members aren't there for blaming only. Sometimes there are other factors that could be targeted (such as hardware failures, user usage patterns, etc.)
My (almost perfect) team members: Yulistiawati Andriani (Team Manager), Nelly Nurmalasari (Model Verifier), Marcellus Aryanto (Infrastucture Administrator), Aris Suryamas (Interface Designer), Ima Nurbani Rahmah (um... PR?), Mohamad Bisri (Tester), Mutiara Sari Parida Hutabarat (Tester), and myself. It's nice to have you guys supporting each other!