0
2

[–] Gargilius 0 points 2 points (+2|-0) ago 

Oh, but I was not talking about a rogue engineer pushing code without code review or qa blessing, the situation I was describing somewhat tongue in cheek is where the engineer is working with both hands tied in his back and only releases crap because this is the only thing that qa and code reviewers and management allows him to release.

Now, if someone has indeed snuck in rogue code on the sly, I'd say fuck him and good riddance, but I am willing to bet that this is not what happened,

0
3

[–] FlintRockBone 0 points 3 points (+3|-0) ago 

I get it, of course if QA and code reviewers were involved then it's not a rogue engineer. To be fair though I've pushed some shameful shit into releases before (when your choices are totally fucked software and mildly fucked software you always will error on the side of mildly fucked). Also I've also tweaked settings to make sure we got a high grade on certifications, but I've always made it so it worked the same during the certification and during the real world experience.

That being said the thought of a rogue engineer making a change to critical production code without sign off in a multi-billion dollar organization is just laughable. The fact the the CEO would testify to that means that he's either counting on congress not having a clue about modern dev workflows or he's unaware of how outlandish his statements are. Or he's just spouting off talking points that his lawyer prepared for him. None of those options sit well with me.

0
2

[–] Gargilius 0 points 2 points (+2|-0) ago 

counting on congress not having a clue

A pretty safe bet.