Everything Can Go Wrong At Once
Just when you can’t think anything can’t get worse it can and will. Anything possible can and will go wrong working on a project almost seemingly at once. These are a list of the possible reasons why everything can go wrong at once when working on a project.
- Not Enough Information - Have you tried to program blind? It does not work. If you do not understand the task at hand there is no way that you can successfully code a project to completion. Trying to code with just a vague understanding of the task does not work. I have tried countless times to code blind but I always end up having to ask a ton of questions to successfully get the needed info to complete the project.
- The Chain Of Information – Knowing who to ask for the right information can be downright confusing sometimes. If you’re stuck on something you may have to ask a ton of people just to get the right answer to your question or something fixed. This is not fun at all. For example I was on a chat the other day where 10 people were involved over a 5 hour time frame just to get the answer to something which impacted my project from succeeding
- Configuration Hassles - In large companies dealing with improperly set up configurations and broken configurations sometimes happens more often than not. It’s not surprising when there are dozens of people working on different aspects at a time of the same system.
- Too Many Dependencies – I have worked on complicated systems where many components are so tightly coupled that if one component breaks it breaks the rest of the system. This is not really a good idea to code to that degree. It is not smart to code like that in critical systems.
These are just some of the many reasons why everything can go wrong at once.
Thursday, October 22nd, 2009