On Thu, Jun 4, 2009 at 7:23 AM, David Smith <[email protected]> wrote: > I'm likely being really naïve here, but the whole 'best practices' thing > really turns me off. I can understand if a company doesn't have experienced > IT folks and needs something to help them get a complicated device like a > server up, running and protected than a BP doc could be really handy. > Usually though I see it used more as a weapon than a tool, often by > 'outsiders' who don't appreciate the intricacies of what's going on 'inside' > in terms of budget constraints, oddball requirements, legacy software > requirements and so on. The BP's I've read assume a level of equipment and a > willingness to invest in IT infrastructure that is frighteningly out of > touch with reality. A BP doc often comes off like a sales pitch instead of > useful IT guidance. I'm not saying a BP is a bad thing; I guess I just > haven't seen enough of the good ones... Maybe it's just me :) -------------------------------------
I tend to agree with you and in this document I am stating what the best practices of the day are, and how we aer hamstrung by our software partner, the, vendor of the application we sell, in know isses where they are perpendicular to the flow. This is an application under HIPPA rules, so when I see items that are out of line with that I am stating what is incorrect and why we are doing it that way. I see this doc as a CYA for this VAR, that if anything stupid happens in the future they can wave this and say "It's their fault. Here are the reasons" I am putting in timing tests for each clients data recovery. This way we can state that it takes X hours to restore your data at this amount of data. we all know that in our business data grows so my time today won't fit your request in 1,2,3 years from now. That being said, I am finding a lot of OBTW, and this is a real problem. I am NOT allowed to fix any of them yet. Unless it is super critical. My job is to uncover all the gotchas they have and then make them go away. -- Stephen Russell Sr. Production Systems Programmer Web and Windows Development Independent Contractor Memphis TN 901.246-0159 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
