Igor's Computer Blog

*This post is a work in progress, in the madman/architect phase, if you'd like to help flesh it out, I'd love the help.  please add comments or ping me.* Why mortality software? To be satisfied we need to live in accordance with the person we want to be. Unless we know who we want to be, and act deliberately to achieve it, our satisfaction will be infrequent, and often accidental. Mortality software helps you understand who you want to be, and supports you in being that person. In a nutshell, making your satisfied. The first step for mortality software is helping you figure out the person you want to be and your values. Who do you want to be? What are your values? To figure out who you want to be, write your eulogy.  To make it easier, figure out the roles in your life. Imagine the person who would speak to each role of your life during your funeral.  What would you want each person to say?   That eulogy is the person you want to be. Now imagine how ...

This post is in  devpreview - skip if you're not passionate about this topic, leave comments if you are.  I read lots, and often forget what I wrote about.  To help me remember, I’m going to take notes on my blog. Feel free to discuss what you've seen in the comments. Terminology Term Definition Entity The "thing" to which principles are applied. Client An entity which consumes this entity . Dependent The entity on which this entity depends to function. Summary of Principles At 10,000 feet, design principles ensure that changes to a software entity, due to bugs or requirement changes,  have minimal impact on clients.  Principle Elevator Pitch SRP: Single Responsibility Entities should have one and only one reason to change. OCP: Open Closed Entities should be closed to changes, but open to extension LSP: Liskov Substitution...