Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 


 
     
Recent Posts
   
Popular Topics
Home   
Search
    Members    Calendar    Who's On

Home » SQLServerCentral.com » Editorials » Who's At Fault
Add to briefcase
21 posts, Page 1 of 3
123»»»

Who's At Fault Expand / Collapse
Rate Topic
Display Mode
Topic Options
Author
Message
Steve Jones - SSC Editor
Posted Wednesday, June 10, 2009 8:12 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 5:09 AM
Points: 31,526, Visits: 13,864
Comments posted to this topic are about the item Who's At Fault






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #732714
AndrewJacksonZA
Posted Thursday, June 11, 2009 1:38 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, June 10, 2013 3:41 AM
Points: 165, Visits: 1,027
In the meantime, the best defense, as always, is making sure you save often and make backups.

On another disk.

On another continent.
Post #732804
Tom Brown
Posted Thursday, June 11, 2009 3:26 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, May 24, 2013 9:02 AM
Points: 1,196, Visits: 1,320
Ten years ago I was team leader in a small software house. When things went wrong there was a bit of a 'blame' culture - and to stop developers squabbling over fault I used to admit responsiblity - especially when the MD (CEO) used to come down looking for a head to put on a pike.
It got to a stage where I'd come accross a group of developers gathered around a PC and say "Its all my fault - what's the problem" - It got a little out of hand, and code comments follows like "Fixed developerX's bad coding". All very well for compiled code - but a customer found some comments in stored procedures and raised a complaint to the MD. We then had a long and protracted exercise in cleaning up all code comments (in both compiled code and SQL) to make sure nothing referred to individuals or customers.

The offending comment. - slightly changed here

-- Fixed xxxx's stupid mistakes. Thats what you get when employing an obvious donkey to do a real developers job.
Post #732850
paul.gregory
Posted Thursday, June 11, 2009 4:20 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, May 11, 2012 3:24 AM
Points: 16, Visits: 95
Losing data? As a developer, I have always taken the approach of delete nothing. Delete is not an SQL command I use. Instead, use an additional column such as 'active'. Then, when the s/&t hits the fan, it's probably a selection issue or some such. Easy to analyse and fix.

And of course, not deleting anything also means I can respond to complaints of the "I didn't do it" sort by looking at the active column of the row and the last user who updated the row, and replying "oh yes you did"

Is it panto season yet?
Post #732888
Someguy
Posted Thursday, June 11, 2009 6:20 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, May 07, 2012 10:39 AM
Points: 153, Visits: 565
All I know is that is wasn't my fault...

___________________________________________________
“Politicians are like diapers. They both need changing regularly and for the same reason.”
Post #732977
arussell_10
Posted Thursday, June 11, 2009 6:32 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, June 11, 2013 7:49 AM
Points: 96, Visits: 1,047
Weird thought Software companies, how about instead of being first to market, try being the best on the market.... I used to work at a telecom company that was more interested in being first to market with a product instead of being the best on the market. Now, year after year, they are usually in first place on bad customer satisfaction...
Post #732985
bob.willsie
Posted Thursday, June 11, 2009 6:44 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, October 02, 2009 6:43 AM
Points: 57, Visits: 151
My second worst frustration in working with an ERP system written in .NET and running on SQL Server is encountering intermittent data loss or corruption.

When you trace through the code, everything looks clean, but somehow out of clean code, and clean input, data was lost or garbage was created.

My absolute worst frustration is that these occurences are considered "acceptable."

Our ERP vendor once supplied a patch and noted that installing it would "make data loss less likely." (actual quote)

So, my question to the group is: What, if any, is an acceptable error rate for data loss or corruption on SQL Server?
Post #732989
GSquared
Posted Thursday, June 11, 2009 7:06 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: 2 days ago @ 1:45 PM
Points: 15,442, Visits: 9,572
I dislike the whole concept of fault. I prefer responsibility. It's the responsibility of those who can repair the problem. Fault and blame are usually just attempts to dodge responsibility.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Post #732999
cy-dba
Posted Thursday, June 11, 2009 7:26 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Wednesday, August 17, 2011 7:09 AM
Points: 869, Visits: 963
I sometimes think trying to find out "who" is to blame just adds fuel to the fire. The goal should be to find out "what" is to blame and then fix it. It's been my experience when you point fingers at a specific person, the result is an environment where people are more concerned about covering up mistakes instead of trying to write high quality software.
Post #733010
bmitchell
Posted Thursday, June 11, 2009 7:48 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, June 13, 2013 7:04 AM
Points: 1,220, Visits: 136
We certainly live in a liability crazy society. There's probably a fortune to be made in writing iron-clad, lawyer-proof disclaimers. A new cottage industry, perhaps...

It seems people are more interested in finding fault than finding solutions. I mean, whose fault is it really if I spill a cup of hot coffee in my lap or I decide to use the blow dryer in the shower?

Responsibility (as mentioned earlier) and accountability are important elements of improving software development.

Along the lines of writing better software, my manager sent out this piece by Charles Fishman yesterday. He notes that errors are ultimately the result of the process.

http://www.fastcompany.com/node/28121/print?
Post #733023
« Prev Topic | Next Topic »

Add to briefcase
21 posts, Page 1 of 3
123»»»

Permissions Expand / Collapse

 
 
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.