Developer on my team QUIT/FIRED

[torpid]

Since I work for the state here, my experience with contractors is the opposite. They are usually the skilled ones and FTEs are a mixed bag, though usually much better managers. This is true even in consulting companies themselves. Consulting companies also hire consultants and even then it somehow holds true.

Edit: The reason being, it is much, much easier to let a contractor go (for all intents impossible to let a state FTE go), so the ones who are there for any period of time usually are competent.

 

[MmmSkyscraper]

Originally posted by: jbourne77
LMAO... my case in point!

:thumbsup: :laugh:

He quit while he was ahead, oh wait a minute...

 

[mugs]

Originally posted by: jbourne77
LMAO... my case in point!

Heh... in the third comment on that one you'll notice someone mentioned "Paula Bean." That name comes up a lot on that site, as does the word "BRILLIANT!" (or "BRILLANT!")

This is where that comes from:
http://thedailywtf.com/Articles/The_Brillant_Paula_Bean.aspx

Some of the stuff on that site is truly amazing.

He does a monthly thing called Pop-Up Potpourri - a bunch of funny pop-up messages or graphics or what have you. That's always good.

Here's the most recent one:
http://thedailywtf.com/Articles/Pop-up_...ourri_0x3a__The_Really_Windy_City.aspx

Each one has a link to the previous month's installment at the top, so it's easy to go back through them.


And like true nerds, in the comments of every WTF there are dozens of people saying "the real WTF is _______", completely picking apart all of the code, and then there will be people who disagree about what is and is not a WTF... reading the comments is sometimes pretty enlightening, because you can see how other people do things differently from you.

 

[torpid]

See, those examples don't really mean much to me. As far as I am concerned, it's ok to be incompetent as long as you have the right attitude. The example I posted of my coworker was meant to demonstrate what she does when encountering her own incompetence. A sane person admits they don't know something or at least tries to fix a problem when confronted with it. This person just blames everyone else for doing silly things like refactoring, even to the point that basic .net things that she does wrong become problems with other people's code, even when that code is never being called or used.

made up example...

int32 x = 1/0 errors out

"Your code is not working. I can't do x = 1/0. I can't work in this environment. No one documents how to do x = 1/0. This is not .net, it's something on top of .net. Where do I put a breakpoint to find out why x = 1/0 is failing?"

 

[Stuxnet]

Originally posted by: torpid
"Your code is not working. I can't do x = 1/0. I can't work in this environment. No one documents how to do x = 1/0. This is not .net, it's something on top of .net. Where do I put a breakpoint to find out why x = 1/0 is failing?"

That would drive me INSANE. I haven't come across a developer like that, but the lady who does documentation pulls sh*t like this all the time. People like this basically just sit back and enjoy the free ride. When the time comes that they're being held accountable for their output, they panic and try to convince everyone - including themselves - that they're behind only because they are forced to work with inferior people.