Improving the world with software
Better software. Better questions.
Essays on software development, teams and the craft of building things that last.
Essays from November 2006
3 essays from November 2006
-
Egineering truths, how to make better engineering decisions
Often in an engineering problem software developers tend to try and find the perfect solution and quickly fall in love with one idea that may work or then shoot down ideas that could work but not in all hypothetical circumstances (even if they are realistically not possible). Many discussions I’ve attended could have been cut …
-
Big Design Upfront = Design-in-progress = Less Productivity = Lost Money
Henrik Mårtenson has an excellent post on Design-in-progress (similar to work-in-progress in Lean Manufacturint). Really worth a read!
-
You cannot inspect quality into a document!
Inspections are a failed analogy.SEI writes in the page about software inspection: Software inspections provide value in improving reliability, availability, and maintainability. They don’t mention however that inspections improve reliability, availability and maintainability of the inspected artifact. In most software companies the inspected artifacts are: documents. This means that instead of improving the software itself …
Nothing matches that yet.
Keep the conversation going
The essays work best in company. Join the community to keep the questions coming.