I always think of the DB, as the last castle of a program. When everything else fails, the DB should function. Programs are maintained way more than they're wri

I always think of the DB, as the last castle of a program. When everything else fails, the DB should function. Programs are maintained way more than they're written. No matter how hard I try to keep my code-base clean, it gets cluttered. That's why I strive to create a powerful base structure and make them bulletproof. Whatever may come (depression, personal problems, fatigue, stress, deadlines, etc.) this skeleton keeps the app alive. In my experience code that is written now, will stay and that complete rewrite I've been dreaming about will never happen :D. So IMHO it's better to design the core funcionality exhaustively and try to create a failproof code-base. My intellectual capacity fluctuates and I'm never as productive as I want to be. I need a safety rope for my dumber version, who has forgotten about the code and has no idea where to start :) Indenting, and aligning helps a lot, when I try to load the code back into my memory.