It’s Software – And I Helped!Filed Under Human Factors
Software is not Shake & Bake…
Projects are continually plagued with poor choices due to something I have just now coined – Shake and Bake Syndrome.
Every single individual involved in a project sincerely cares about the best possible outcome; however as a result of caring – we pollute the purity of designs and implementations by adding a small amount of our personal opinions to the project.
Here are a few common examples of this in action:
- Feature lists driven by a committee of people
- DBAs enforcing their application database schema
- Non-UI developers making UI
- Customers modifying professional designs
- New feature creep labeled as bugs by QA personal
- Developers assuming they understand the domain
So in short, here is what happens – everyone wants to help, everyone throws in their 1 big idea, the project becomes a mashup of disjoint ideas.
Seriously, what would a Frank Lloyd Wright house look like if he gave into the “design by committee” mentality? I guarantee that it would have not had the same artistic beauty.
Since we could (and have) debate whether software is a science or art, the question comes to mind – are the only pure pieces of software art those done by a single person? Or, is the single developer always doomed to imperfection since we can never master everything?
Regardless, I highly value my teammates because I know that they compliment me in my weaknesses; however, I am growing ever-so-more tired of the non-stakeholders adding in their 2 cents.
It’s time to make some Scrum chicken Shake & Bake…and no, you can’t help.