Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase ««12

Trusting Systems Expand / Collapse
Posted Thursday, May 23, 2013 1:06 PM

SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Tuesday, September 23, 2014 7:42 PM
Points: 635, Visits: 2,215
OCTom (5/23/2013)

All employees like to think their work is high priority. The reality is that very few systems and employees are mission critical. If you have identified the mission critical systems and operations that must be working within a reasonable time period, you can address those first.


And any employee that is mission critical should strive to find a way not to be.

It is better for their health and well being as the employee can have the down time to vacation and take care of the personal stuff without expecting to be on call. It is also better for the company because if that employee was to be hit by a beer truck what would the company do.

Jim P.

A little bit of this and a little byte of that can cause bloatware.
Post #1456187
Posted Friday, May 24, 2013 2:02 AM



Group: General Forum Members
Last Login: Tuesday, November 29, 2016 2:33 AM
Points: 148, Visits: 1,105
Knowledge Draftsman (5/23/2013)
This reminds me of an article I came across earlier in my career... The gist of the piece was that every employee should know how to do their jobs without the use of an automated system. So, that when (not if, but when) the system goes down, the business can continue to function. Granted it won't be at the same productivity level, but business continues none the less. I know there are jobs now, where that's just not possible. However, I think, that too many workers don't know how to do their jobs without the aid of a computer. And, I think, there's real value in knowing how to actually do your job without a computer, as oppose to relying on one. If you can do it without a computer, that signals to me that you truly understand the process; instead of just knowing which buttons to push.

As system professionals I think most of us would be able to implement limited hacked procedures at short notice with off line systems - (web systems apart). Mainly because we can hardly design systems without really understanding the guiding principles of the system.

My default position on one system critical application is make sure the machines are on and recording even if nothing is being calculated. Results can be calculated later from the raw information in excel if needs be but if it ain't recording all the computing power in the world won't help. If I couldn't do that I'd be reduced to smiling and being very calm while quitely informing responsible parties that well nobody is going to die (I would press for multiple true backup alternatives in systems were this was an issue). In some applications I may be able to revert to paper and pen but that won't be possible in a lot of cases.

As fewer and fewer of us make systems for greater and greater numbers of users there is a risk of the end users not understanding the underlying principles because the level of abstraction is so great.

I think this was a problem with the financial crisis. Management didn't fundamentally understand the weaknesses inherent within the procedures the systems promoted. Surely the auditors should have picked up on this. Sadly I think they were so abstracted from the ground level that the combined weight of the accounting world sailed right across the reef for years.
Post #1456318
Posted Friday, May 24, 2013 4:03 PM



Group: General Forum Members
Last Login: Yesterday @ 10:35 PM
Points: 42,070, Visits: 39,452
Knowledge Draftsman (5/23/2013)
However, I think, that too many workers don't know how to do their jobs without the aid of a computer.

Ironically, I've found a great number of workers that don't know how to do their jobs even when the computer is up and running.

As a wise-man once said, anyone can make a mistake but to really screw something up, you need a computer.

--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

Helpful Links:
How to post code problems
How to post performance problems
Post #1456709
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse