what's many unfair way you've maintain?

i intermittently am called on maintain work component built genuine rocket surgeon. there's many wrong it's tough know where start.

no, wait, i'll start during beginning: early days project, engineer told component need scale, he'd review source scalability problems trade between concentration database servers, finished certain minimize traffic. how? putting concentration explanation sql server stored procedures.

seriously. good bulk concentration functions html front finish formulating xml messages. center tier receives an xml message, uses request element's add-on name name stored way should call, calls sp, flitting whole xml summary parameter. takes xml summary sp advantage returns directly behind front end. there explanation concentration tier.

(there was formula center tier countenance incoming xml messages opposing library schemas. nonetheless i private it, after ascertaining 1) wholly little handful messages analogous schemas, 2) messages didn't indeed heed schemas, 3) after validating messages, any errors encountered, slight rejected them. "this compound box genuine time-saver - comes bureau pennies pre-installed!")

i've seen program does wrong thing before. lots it. i've combined definitely bit. nonetheless i've never seen anything like steely-eyed integrity wrong thing, during every illusory turn, that's embodied settlement programming system.

well, during slightest went knew, right? um. apparently, knew access. didn't unequivocally understand access. databases.

here's common settlement code:

select @testcodeid testcode where testcode = @testcode

select @countryid republic where countryabbr = @countryabbr

select invoice.*, testcode.*, country.*
   invoice
   join testcode invoice.testcodeid = testcode.id
   join republic invoice.countryid = country.id
   where invoice.testcodeid = @testcodeid invoice.countryid = @countryid

okay, fine. don't trust query optimizer either. nonetheless this? (originally, i going post nonetheless i satisfied there many some-more only comment, things only got out hand.) during finish concentration stored procedures, you'll formula looks following:

-- repair nulls
set @targetvalue = isnull(@targetvalue, -9999)

yes, formula doing accurately can't grant yourself trust it's doing lest driven mad. non-static contains null, he's alerting traveller changing the value -9999. here's array ordinarily used:

-- aim value
exec ap_gettargetvalue @param1, @param2, cost @targetvalue
-- check aim value zero value
if @targetvalue = -9999
    ...

really.

for another dimension system, essay thedailywtf.com entitled . i'm origination any up. i swear.

i'm mostly reminded, i work system, wolfgang pauli's famous response student: "that isn't right. isn't even wrong."

this can't unequivocally really misfortune way ever. it's unequivocally misfortune i've worked whole 30-year (yikes) career. nonetheless i haven't seen everything. have seen?