• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Does this seem a little harsh to you?

Status
Not open for further replies.
For KLin, here's another article: http://www.google.com/hostedne...2eH7csTqH04IQD961P3GO0

He was fired Oct. 24 from his computer programming job at Fannie Mae's data center in Urbana, about 35 miles from the company's Washington headquarters, where he had worked since 2006, according to the Justice Department. He was fired for erroneously writing programming instructions two weeks earlier that changed the settings on the servers, according to an FBI affidavit.
 
Originally posted by: her209
For KLin, here's another article: http://www.google.com/hostedne...2eH7csTqH04IQD961P3GO0

He was fired Oct. 24 from his computer programming job at Fannie Mae's data center in Urbana, about 35 miles from the company's Washington headquarters, where he had worked since 2006, according to the Justice Department. He was fired for erroneously writing programming instructions two weeks earlier that changed the settings on the servers, according to an FBI affidavit.
Was he supposed to be writing programming instructions that changed the settings on the servers?

 
I guess it might have been the first mistake he ever made, but I doubt it.
 
Originally posted by: her209
For KLin, here's another article: http://www.google.com/hostedne...2eH7csTqH04IQD961P3GO0

He was fired Oct. 24 from his computer programming job at Fannie Mae's data center in Urbana, about 35 miles from the company's Washington headquarters, where he had worked since 2006, according to the Justice Department. He was fired for erroneously writing programming instructions two weeks earlier that changed the settings on the servers, according to an FBI affidavit.

So he was fired for negligence? Were there rules to not make changes to the server without previous testing? Was there any testing? Did the error cause irrecoverable data loss? Did it cause downtime? How much did it cost to fix?
 
Originally posted by: mundane
So he was fired for negligence? Were there rules to not make changes to the server without previous testing? Was there any testing? Did the error cause irrecoverable data loss? Did it cause downtime? How much did it cost to fix?
Exactly! What/where are the processes and procedures?
 
Originally posted by: her209
For KLin, here's another article: http://www.google.com/hostedne...2eH7csTqH04IQD961P3GO0

He was fired Oct. 24 from his computer programming job at Fannie Mae's data center in Urbana, about 35 miles from the company's Washington headquarters, where he had worked since 2006, according to the Justice Department. He was fired for erroneously writing programming instructions two weeks earlier that changed the settings on the servers, according to an FBI affidavit.

You don't know what further record of incompetence and inability or unwillingness to follow direction this jamoke had racked up in the two short years he was there before he was finally fired, but perhaps his feloniously asshole reaction to his termination can give you some idea, no?
 
Originally posted by: her209
Originally posted by: mundane
So he was fired for negligence? Were there rules to not make changes to the server without previous testing? Was there any testing? Did the error cause irrecoverable data loss? Did it cause downtime? How much did it cost to fix?
Exactly! What/where are the processes and procedures?

Shouldn't you know that if it's causing you angst?
 
Originally posted by: her209
Originally posted by: mundane
So he was fired for negligence? Were there rules to not make changes to the server without previous testing? Was there any testing? Did the error cause irrecoverable data loss? Did it cause downtime? How much did it cost to fix?
Exactly! What/where are the processes and procedures?

Which is why I still can't form an opinion based on a news article.
 
A guy who worked here nearly got fired for changing code 'because he knew a better way to do something'... He suggested a change of code, was told it was not a good idea, and that the current solution was put in place for a reason. He then wanted to prove he was right, and in order to do so he changed the sources in SourceSafe without telling anyone. This was a day before a major release would be tested for release. On the big day it would not compile at all anymore, and they had to spent hours to find out what was wrong (since he didn't come clean when the problem was noticed). After that he couldn't access SourceSafe anymore. Oh, and the release had to be delayed. Since his behavior didn't get much better in the months after that he was basically given the choice of leaving or be fired later on, so he left.

Oh, and note that when he changed the code he was working here less than a week.
 
Originally posted by: Skyclad1uhm1
A guy who worked here nearly got fired for changing code 'because he knew a better way to do something'... He suggested a change of code, was told it was not a good idea, and that the current solution was put in place for a reason. He then wanted to prove he was right, and in order to do so he changed the sources in SourceSafe without telling anyone. This was a day before a major release would be tested for release. On the big day it would not compile at all anymore, and they had to spent hours to find out what was wrong (since he didn't come clean when the problem was noticed). After that he couldn't access SourceSafe anymore. Oh, and the release had to be delayed. Since his behavior didn't get much better in the months after that he was basically given the choice of leaving or be fired later on, so he left.

Oh, and note that when he changed the code he was working here less than a week.

Wow, he should have been taken out back and shot.
 
Originally posted by: TallBill
Originally posted by: Skyclad1uhm1
A guy who worked here nearly got fired for changing code 'because he knew a better way to do something'... He suggested a change of code, was told it was not a good idea, and that the current solution was put in place for a reason. He then wanted to prove he was right, and in order to do so he changed the sources in SourceSafe without telling anyone. This was a day before a major release would be tested for release. On the big day it would not compile at all anymore, and they had to spent hours to find out what was wrong (since he didn't come clean when the problem was noticed). After that he couldn't access SourceSafe anymore. Oh, and the release had to be delayed. Since his behavior didn't get much better in the months after that he was basically given the choice of leaving or be fired later on, so he left.

Oh, and note that when he changed the code he was working here less than a week.

Wow, he should have been taken out back and shot.

We couldn't find a gun in time 😛

The funny part of it was that he (end 20s, early 30s) started at the same time as a female programmer (end 40s). The department which picked him got first choice, and wanted him because he was younger (and therefor more likely to stay a while), and because he would be less stuck in old ways of coding. After that first week they basically begged the other department to trade, but they refused. She stayed with the company for about 8 years or so, quite a bit longer than he did, and was an extremely good programmer (and very good at learning new methods) 😉
 
Status
Not open for further replies.
Back
Top