What are the worst programming habits?

[OriginalGriff]

var is handy in two places: 1) When using Linq and returning "An IEnumerable of something, gawddammit, but I have no idea what the compiler is going to call it" 2) To identify people whose code you can't trust because they have no idea or no interest in what type a variable should be. It may save five keystrokes to use var instead of IEnumerable<Customer> but it doesn't help understanding when you have to read the code later.

Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)

[OriginalGriff]

d@nish wrote:

When did Britishers took over MS?

We didn't. If we had, the Color class would be spelled properly!

Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)

[dan sh]

OriginalGriff wrote:

To identify people whose code you can't trust

:thumbsup:

My CP workspace: Incredibly trivial and probably useless code samples[^]

[dan sh]

Wait, that explains it. Those who have trouble typing a "u", can not type IEnumerable< Whatever the hell it is >. I now know the whole purpose of var. Enlightened.

My CP workspace: Incredibly trivial and probably useless code samples[^]

[PIEBALDconsult]

Eddy Vluggen wrote:

explain a junior ONCE

That's once too many.

You'll never get very far if all you do is follow instructions.

[Lost User]

Adding oil to the fire, a practical example;

using System;
using System.Threading;
using System.Windows.Forms;
using System.Timers;

namespace ConsoleApplication5
{
class Program
{
Timer t = new System.Threading.Timer(null); // will not compile, as it is unclear which Timer
Timer t2 = new System.Windows.Forms.Timer(); // is declared (as opposed to the type instantiated)
Timer pfld_SysTimrTimrt3 = new System.Timers.Timer(); // using hungarian systems with namespace prefix

    static void Main(global::System.String\[\]\[\] strSrgs)
    {
        global::System.Console.ReadLine();
    }
}

}

And yes, the "console application template" has an entry point which is implicitly private.

Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]

[Lost User]

Dave Kreskowiak wrote:

In C# the default is private while in VB it's Public. I absolutely hate that and really dont want to have to remember what the defaults ars supposed to be when scanning over code for problems.

I hate that it's public in VB.NET too, but it does not change the way I look at C#. Having tried it, for several months, in both languages, to me, the benefit outweighs the possible disadvantage of confusion.

Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]

[Gary Wheeler]

Hmm. I agree with Joel but I stand by my dislike of the common Hungarian notation, despite Simonyi's original intent.

Software Zen: delete this;

[Lost User]

Comments like this: i=6; //set i to six :)

[Simon_Whale]

My main bug bears are 1. Excessive whitespace between code lines 2. In code comment,for that complex method that are so short they are as useful as the var keyword.

Every day, thousands of innocent plants are killed by vegetarians. Help end the violence EAT BACON

[Chris Losinger]

1. incorrect bracket placement 2. if (2 == var) 3. not enough whitespace 4. globals

image processing toolkits | batch image processing

[Chris Losinger]

Eddy Vluggen wrote:

there's a keyboard shortcut to automatically reformat in the VS-IDE.

which is a total broken disaster in VS2013 (for C++ at least)

image processing toolkits | batch image processing

[David ONeil]

Currently dealing with a codebase that uses magic numbers and tucks them into the window's hMenu member (and uses them from there)! Ghhgh! The other nightmare offense in the code is using "m_" for: a) Some, but not all, member variables. b) Some, but not all, in function variables, including loop indexes. c) Some, but not all, passed function parameters. That was fun to get sorted - NOT. There were even a couple places where the same name was used in two or more different ways, so a project-wide replace would blow up. X| X| X| X| X|

My website :: My book revealing the forgotten astronomy of our ancestors.

[Forogar]

It's a pity that we can't use a condensed "new" format like:

CryptographicUnexpectedOperationException exception = new ();

which means the same as:

CryptographicUnexpectedOperationException exception = new CryptographicUnexpectedOperationException();

- I would love to change the world, but they won’t give me the source code.

[Forogar]

I use var when I have some method to call that returns a humungously long-named type. I then immediately change it with the "Make Explicit" option. That way I don't have to type it out in full or select from a potentially huge list of intellisense suggestions.

- I would love to change the world, but they won’t give me the source code.

[OriginalGriff]

Fine by me - it doesn't leave the var in the final code, or treat C# as if it was VB and "don't know, don't care" Dim

Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)

[Jorgen Andersson]

0. Systems hungarian.

Wrong is evil and must be defeated. - Jeff Ello[^]

[Duncan Edwards Jones]

-2. Swallowing an exception -1. Throwing an exception with no message and just the generic "Exception" class. 0. Using try-catch for normal program flow.. (And these are just the rules to the exception :-) )

[Sander Rossel]

Things that bug me... 1. Comments. Too often have I seen comments that made no sense, were outdated, wrong or overly obvious. In fact I've learned to ignore comments as they've never helped me in any way. I guess programmers can't write English... 2. Code that is copy-pasted. Often the cause of bugs. 3. Swallowing exceptions. 4. Non-Object Oriented code in Object Oriented languages. 5. Formatting, you've said it. Bonus: 6. Not using brackets in if statements. Very dangerous... I'm working for a company that has worked with VB since the start. The first employees have worked with VB even longer and used Clipper before that. I've seen 1 through 5 all to often :sigh: I've come to hate 6 when we started doing C# and outsourced a project to another company. HORRIBLE!!! I read the code and didn't know if they meant it that way or if they had introduced subtle bugs... A lot of samples I get from the internet have it too. I probably forgot some stuff, but these are a few of my least-favourite things.

It's an OO world.

public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}

[PIEBALDconsult]

Soooo... the class is private? :confused: How does that work? Even I avoid global:: -- by using an alias if necessary:

using MySqlClient=global::MySql.Data.MySqlClient ;

What the heck is a pfld_ ? A pointer to a fixed long double?

You'll never get very far if all you do is follow instructions.