Software design is akin to the chef building a great recipe, not the cook following the recipe. Many of us are so used to cooking from recipes, that sometimes we forget what goes into creating the recipe in the first place. 

In software design, we are creating the recipe, not cooking from it. We prepare different combinations of ingredients (prototypes) and call friends (testers) over to try them and give their opinions. When we're done, what we've produced is the Recipe (Requirements Document). Then it's the users that cook from the recipe. What chefs don't do is write down the first ingredients they plan to use and then put those ingredients into their cookbook without any taste tests, so why do we?

Posted
AuthorPete Oliver-Krueger
CategoriesLean Enterprise

"The time of maintenance on a project will increase in direct correlation to the number of steps between your View and your Model."

When estimating the amount of work required for any change to a system, you can estimate the time required to change the model or the view, and then multiply that time by the number of Degrees of Maintenance in the task to get a better estimatation of the total time of the task.

Posted
AuthorPete Oliver-Krueger

A fast-forward history of object-oriented programming, leading to a new programming standard called Property-Invocation (Pi) Programming. By following 4 basic rules, you can gain infinite flexibility and power with your object-oriented architectures. Every object operates as a plugin for any other object, facilitating reuse and promoting "encapsulation" in your objects.

Posted
AuthorPete Oliver-Krueger
CategoriesPresentation