meta_robert

Putting together a generic framework for building systems

“Framework” may be too generic a term, but that will become more clear as I develop this idea a bit further. I’ll start making posts as the bits and pieces float through my head (that could be once a year at the rate I post, and the rate at which ideas come to me sometimes!) What I’m hoping to do is to put together all of the ideas that are simply too many to remember while building systems. For example, the drive/partition configurations, the security concepts such as like registry tweaks fs changes, firewall settings, or things like relationships to other systems that are in the environment. This sounds simple, I know, but it’s not. At least if it’s done right from all levels. Anyone can build a system. Add value or you are just another of the monkeys launching installers. You might have a knowledge of business needs and apply that to design. You might know security and create inherently secure systems. You might understand the administrative needs in manageing the systems and build accordingly. To design systems is to take all of these things, and more, into account. If you don’t at least try to move in that direction, you’d better be really good at something specific that is in demand.