How I hate crap developers

[rwenzori]

http://www.algoafm.co.za/

Server Error in '/' Application.
There is no row at position 0.
Description: An unhandled exception occurred during the execution of the current web request. 
Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IndexOutOfRangeException: There is no row at position 0.

Source Error:

Line 387:            
Line 388:        'Check for 24:00 and replace with 00:00 - ShowFrom Field
[COLOR="#FF0000"]Line 389:        If rsCurrentDJSchedule.Rows(0).Item("ShowFrom").ToString = "24:00" Then[/COLOR]
Line 390:            dTimeFrom = "00:00"
Line 391:            dDayFrom = dToday + 1


Source File: C:\inetpub\wwwroot\AlgoaFM\default.aspx    Line: 389

How can there be no CurrentDJSchedule? I mean, it just HAS to be there, so piss on coding for the unexpected. And who needs to code for exceptions anyway?

 

[Adenoid Hynkel]

I hate burned bacon for breakfast

 

[S1ght]

http://www.algoafm.co.za/

Server Error in '/' Application.
There is no row at position 0.
Description: An unhandled exception occurred during the execution of the current web request. 
Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IndexOutOfRangeException: There is no row at position 0.

Source Error:

Line 387:            
Line 388:        'Check for 24:00 and replace with 00:00 - ShowFrom Field
[COLOR="#FF0000"]Line 389:        If rsCurrentDJSchedule.Rows(0).Item("ShowFrom").ToString = "24:00" Then[/COLOR]
Line 390:            dTimeFrom = "00:00"
Line 391:            dDayFrom = dToday + 1


Source File: C:\inetpub\wwwroot\AlgoaFM\default.aspx    Line: 389

How can there be no CurrentDJSchedule? I mean, it just HAS to be there, so piss on coding for the unexpected. And who needs to code for exceptions anyway?

VB.NET....*shudders

 

[zippy]

My pet "hate", ignoring exceptions.

Pl/SQL version:

Begin
... code
Exception
When others then
Null;
End;

Always an excuse to do this

 

[Hamster]

I find this one a lot:

try
{
  // do stuff
}
catch{}

..and the the little Philistines think their code is solid because it never breaks

 

[BandwidthAddict]

Most programmers on this planet are not actually cut out for the job. They're just not intelligent enough so they take "shortcuts" to try keep up with expectations. Same goes for IT/development managers. Anyone with an IQ less than 130 shouldn't bother with this field although at 130 it's mostly janitorial work.

 

[Hamster]

Most programmers on this planet are not actually cut out for the job. They're just not intelligent enough so they take "shortcuts" to try keep up with expectations. Same goes for IT/development managers. Anyone with an IQ less than 130 shouldn't bother with this field although at 130 it's mostly janitorial work.

To me the clock watchers are the most "dangerous". I'd much rather work with an average developer that takes pride in his work than with a genius that drops everything when the clock strikes 17:00. You'd get way more done with that eager less knowledgable dev.

 

[ToxicBunny]

Beyond the coding aspect...

WTF leaves their site in the default IIS web location?

And who leaves remote errors on.... BAD idea.

 

[Hamster]

Beyond the coding aspect...

WTF leaves their site in the default IIS web location?

And who leaves remote errors on.... BAD idea.

Same kinda people who have indexoutofrange exceptions in their code

 

[DominionZA]

To me the clock watchers are the most "dangerous". I'd much rather work with an average developer that takes pride in his work than with a genius that drops everything when the clock strikes 17:00. You'd get way more done with that eager less knowledgable dev.

I am a clock watcher. I have 3 clients I work for and as a contractor I have obligations. I have to stop work on one at a certain time to get my hours in for the next. If I don't, someone scores and someone loses.

Suppose it may be different for perm staff.

 

[stevenv]

public boolean isActive()
{
  if active
    return true;
  else
    return false;
}

 

[DominionZA]

public boolean isActive()
{
    return active;  
}

FTFY

 

[semaphore]

To me the clock watchers are the most "dangerous". I'd much rather work with an average developer that takes pride in his work than with a genius that drops everything when the clock strikes 17:00. You'd get way more done with that eager less knowledgable dev.

And what exactly is wrong with a guy wanting to leave work at 17:00 is it a sin to actually want to have a life beyond the job? Shame pretty brain washed mentality but i know it was very common there. Work smarter not harder and the job will be done faster.

 

[semaphore]

I am a clock watcher. I have 3 clients I work for and as a contractor I have obligations. I have to stop work on one at a certain time to get my hours in for the next. If I don't, someone scores and someone loses.

Suppose it may be different for perm staff.

Nah dude he is brain washed into thinking that is how the development world is, trust me everyone at that company is.

 

[kolaval]

Unfortunately I rule you all in that regard, i have to fix said k@k code continously.
I was swearing profoundly on friday, to the amazement of some colleauges because protocols are not being followed and some person moved code to LIVE but never bothered to run one test, and went on leave...

Or the '15 year old of the week' that runs SQL to check if a row exists and then opens the row as an object (intersystems cache db) to check if it exists

Or continously updating the same data in a while loop instead of e.g. setting a boolean in the loop and updating the rows if the boolean is true

No code comments, documentation, explenations...

And when the effing 15 year olds repeatedly ask you how to write a effing stream to a effing file, which after effing years of development on that platform they should do with their eyse closed.

Ag Nee, you okes have me ranting

 

[DominionZA]

Unfortunately I rule you all in that regard, i have to fix said k@k code continously.
I was swearing profoundly on friday, to the amazement of some colleauges because protocols are not being followed and some person moved code to LIVE but never bothered to run one test, and went on leave...

Or the '15 year old of the week' that runs SQL to check if a row exists and then opens the row as an object (intersystems cache db) to check if it exists

Or continously updating the same data in a while loop instead of e.g. setting a boolean in the loop and updating the rows if the boolean is true

No code comments, documentation, explenations...

And when the effing 15 year olds repeatedly ask you how to write a effing stream to a effing file, which after effing years of development on that platform they should do with their eyse closed.

Ag Nee, you okes have me ranting

Watch that blood pressure man. Not worth it.

I think the calm comes with age. I have been coding 25 years now. I don't see point in ranting when someone does something in a way I don't think is the right way (I used to though). I just fix it, test, and move on. More often than not the devs will ask why I changed it and I will explain. Everyone learns something and none of us have high blood pressure.
And even after 25 years I learn new stuff all the time from my colleagues. No-one can ever know it all and you should rather help build the skills instead of flipping your lid. You may just live longer

 

[Hamster]

And what exactly is wrong with a guy wanting to leave work at 17:00 is it a sin to actually want to have a life beyond the job? Shame pretty brain washed mentality but i know it was very common there. Work smarter not harder and the job will be done faster.

Nothing wring with being a clock watcher. To them it is just a job. I'd still rather work with someone that is willing to put in some extra effort and who takes pride in his job. I'd rather work with a rough diamond than a polished turd.

 

[Kosmik]

Shew, some ego's in this thread.

 

[Necuno]

Shew, some ego's in this thread.

It's bad being the small man

 

[semaphore]

Nothing wring with being a clock watcher. To them it is just a job. I'd still rather work with someone that is willing to put in some extra effort and who takes pride in his job. I'd rather work with a rough diamond than a polished turd.

So let me get this straight... you would rather work with someone that is inefficient as opposed to someone that is? Yes of course that makes perfect sense But lets get some thing straight first people have families they need to be with, that does not make them a clock watcher they have just prioritized things which are more important, it however doesn't mean that the job means less to them or that its a means to an end. When you've worked for 12+ years in the industry you will understand or settle down whichever comes first.

But yes i was like that in the beginning of my career i worked stupid hours and loved it. But that is all in the past i will do research in my own time because this is a passion of mine, and i know at the end of the day the effort i put in will reflect in the product i produce. I however will NOT work late when other people are just because of pure guilt, i will also not be forced into the position of being told to work late. The second that happens (again) i tell that person to go get fukt.