It's a jungle in there

[Br Bill]

I find it brilliant. 100% bug-free!

[Sander Rossel]

I blame VB 1, 2 and 3. I was a toddler at that time so I wouldn't know, but this is what I heard. VB became object oriented at version 4, but to be backwards compatible MS had to support the non-object oriented style. As a result many VB programmers kept on programming like they always did and still do so today. Why not C#? Because the first C# came at around the same time as VB4 and was object oriented right from the start. On a side note, try to call any PUBLIC member of a Form in VB without having an instance of the Form. It will work, you can call them as if they were Shared (static). I recently found out and was shocked, backwards compatibility with VB1... X| Anyway, I don't really blame VB, I blame the programmers who were not willing to learn object orientism right after VB3 :sigh: Does that sound about right or am I really way off here?

It's an OO world.

[Sander Rossel]

Or my favourite:

Try
' (Lots of) code here.
Catch ex As Exception
LogError(0, ex.Message, "SomeClass.SomeMethod")
End Try

Yes, we did not pass the Exception Object to the LogError Method, we provided some parameters as Strings. I still don't know what the first parameter is. It is always 0... "SomeClass.SomeMethod" is not fetched from the Exception Object, but passed as a fixed String. It gets worse, because this piece of code is copied in EVERY Try Catch block (except the empty ones of course). See how copying "SomeClass.SomeMethod" does not work for "SomeClass.OtherMethod"? :) So our logging is often not very reliable. And even if it is (it is not ALL bad) it usually does not say very much because we don't log stacktraces etc. A log that says "Reference not set to an instance of an Object" in a Method with some 100 lines of code is really not very helpful :) Next to that there is a Try Catch block in almost EVERY Method, but NEVER a ReThrow or a MessageBox.Show to the user. What a way to handle Exceptions! :thumbsup: It annoyed me so much I decided to write an article about it :)

It's an OO world.

[User 7736130]

Maybe he didn't know about code snippets....

[Fabio Franco]

Naerling wrote:

VB became object oriented at version 4

Not fully, still lacked lots of OO principles, even VB 6 (like something as basic as inheritance).

Naerling wrote:

I blame the programmers who were not willing to learn object orientism right after VB3

I actually seen that in action on VB.Net.

Naerling wrote:

Does that sound about right or am I really way off here?

Yes, it does. But in my opinion that's not the full story and the full story about all the VB infame does not apply to everyone and to all scenarios. But yes, the word VB gives me goose bumps, specially when I learn I have to work with existing code.

"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson

[Sander Rossel]

I had to work with lots of existing VB code... Code that goes as far back as being coded in VB6 and imported to .NET (when I started to learn programming there I learned from seeing what NOT to do) :omg: Luckily my hard studies got me to a point where my boss actually lets me write new classes and libraries for every programmer in the company (that's 4 people including me...) to use (and yes, I am one of those VB programmers who DOES know what an Interface (other than GUI) is and how to use it) :D

It's an OO world.

[Fabio Franco]

Naerling wrote:

my boss actually lets me write new classes and libraries for every programmer in the company to use

Now, that's really cool. It's a very nice role to have.

Naerling wrote:

and yes, I am one of those VB programmers who DOES know what an Interface (other than GUI) is and how to use it

Some may consider you a mythical character :laugh:

"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson

[Sander Rossel]

Fabio Franco wrote:

Some may consider you a mythical character

Thanks! :laugh:

It's an OO world.

[RobCroll]

I feel your pain. I've just finished going through a similar process. After a while you stop getting annoyed and start laughing. The one that made me laugh most was:

public class OrderName
{
public String getName {
return "Order";
}
}

That was the class in totality. One method that returned a hard coded value. [EDIT] I just found a better one:

for (int i = 1; i < 2; i++) {
//Code was here
}

"You get that on the big jobs."

modified on Sunday, August 14, 2011 10:23 PM

[GibbleCH]

Reminds me of things like this...

for (int i = 0; i < 5; i++) {
switch (i) {
case 1: {

    }
    case 2: {

    }
    case 3: {

    }
    case 4: {

    }
    case 5: {

    }
    default: {

    }
}

}

[richard_k]

This code feels like some Zen koan or something.. If a tree falls in the forest but no one is around, does it make a noise?

[cpkilekofp]

Fabio Franco wrote:

Is it just me or everytime someone talks about bad code, "VB" shows up? :sigh:

It's just you - the worst code was (and may still be) written in C/C++ by former BASIC, COBOL, and FORTRAN programmers still new to Dykstra's "GoTo Considered Harmful" dictum...which didn't prevent them from abusing every feature in the language. I spent years cleaning such code, and still don't think I got everything fixed the way it should be (e.g. readable). BASIC, COBOL, and FORTRAN all allowed really bad code to be developed, real "spaghetti" code, but recasting the same engineering in C (or, worse by two or three orders of magnitude in this age of templates, C++) permits monstrosities to be created that even the coders may not be able to understand after a month or two working on other projects. Worse, with macros, you can make C/C++ look like BASIC or FORTRAN...perhaps even COBOL, though I've never seen anyone sick enough to try that (yes, I've seen examples of the other two practices, and it just makes you ill to see it if you ever loved C). As for On Error Resume Next....what other language system can anyone name that is as ubiquitous as BASIC, COBOL, FORTRAN, or C that allowed a non-in-line interrupt-style error handler to be constructed? Yes, the only one that comes to my mind, as well, is BASIC. On Error GoTo was a huge advance for its time; On Error Resume Next was, really, just a way to allow "old-fashioned" error handling (checking output variables and return values for error conditions) to be used or not. Most of the cocks-of-the-progamming-walk who complain about the foibles of this feature just weren't around to complain about it in 1968 when Dartmouth BASIC was released; if it seems a dated feature now, well, OF COURSE IT IS. Hmmm, does this count as a rant? :laugh:

[Fabio Franco]

cpkilekofp wrote:

Hmmm, does this count as a rant? :laugh:

Oh definitely :laugh: . Please don't take this personally :)

cpkilekofp wrote:

the worst code was (and may still be) written in C/C++

Nobody said that the worse code seen was in VB. The joke was about how often the name Ugly Betty comes up whenever we are talking about ugly girls.

"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson