Well since I have to be a jack of all trades AND have a few details that I need to have for my particular project that are not generally as vital in most develo

Well since I have to be a jack of all trades AND have a few details that I need to have for my particular project that are not generally as vital in most development projects I have both a bit more complicated data structure as well as having the need to become sufficiently competent in a number of areas. One example is a need I have to do all or virtually all interactions between my heavily normalized back end with stored procedures as well as needing to have data protection built on both the front end and the back end. This redundancy is also something I need to deploy in a somewhat consistent manner if I am to keep a handle on what I'm doing. When there's replication in protecting the data on both sides, at least it's been my experience, that the going back and forth makes more moments for things to be forgotten, so I find that being very systematic in my approach is needed, but being systematic while working in a piecemeal manner, at least for me, is tough. Documenting my code helps some, but having my own linear, self directed narrative about what I've done, what I'm doing, where I'm going, written in a way that I understand and not encumbered by the preoccupation that should accompany, I believe, well documented code, helps a ton. If I can write and not worry about dotting all the I's or crossing all the proverbial T's then a few minutes reading/revising my narrative and I'm ready to jump back in to coding, even if I just got done feeding the baby, changing the diaper, paying the cell phone bill, putting the baby to sleep and then doing a 'honey-do' for my wife. I can sit down and quickly get oriented in the direction I need to go. I hope that was what you wanted when you asked for details and an example. If not I'll need you to elaborate more on exactly what you want to hear.