Into bad habits
-
Bah, for a second I thought this was about real software. Then I saw the name "MelonCard", and "techcrunch" and realized they were talking about web "programming". Next they be crying about the time they found out that they were not in fact visited by magical flying unicorns.
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
LOL But c'mon, the topic is about real software and how, as you put it, web "programming" can impair one's ability to right one.
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
LOL But c'mon, the topic is about real software and how, as you put it, web "programming" can impair one's ability to right one.
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
Yes, and another reason why using a stateless protocol for applications, especially applications that specifically *need* state, is such a horrible idea. Bring on Web 4.1! But I did go back and read more - and even learned something new about JS!
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
-
Strict languages help a lot - if you listen to the warnings they give. (Personally I run with "treat warnings as errors" set on). For example:
if(myInt & 0x80 != 0)in C# is an error - the result is not bool. In C++ it just doesn't do what you expect... This one caught me in an answer in Q&A because I had got so used to C# telling me off that I assumed the operator precedence was correct when C++ didn't give me a warning or error...Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
OriginalGriff wrote:
if(myInt & 0x80 != 0)When I first saw this I was tempted to reply with a: "Whats wrong with this on C#?" Since I'm not used to perform bitwise ANDs on my dayly work I didn't realize that comparison operators had precedence over bitwise operators. I guess in C++ the result would be false (0) if myInt is different from 1?
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
Yes, and another reason why using a stateless protocol for applications, especially applications that specifically *need* state, is such a horrible idea. Bring on Web 4.1! But I did go back and read more - and even learned something new about JS!
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
The very word "stateless" creeps me out...
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
OriginalGriff wrote:
if(myInt & 0x80 != 0)When I first saw this I was tempted to reply with a: "Whats wrong with this on C#?" Since I'm not used to perform bitwise ANDs on my dayly work I didn't realize that comparison operators had precedence over bitwise operators. I guess in C++ the result would be false (0) if myInt is different from 1?
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
Yep! Annoying that, isn't it? As a result, I always used brackets - which made the code messy - until I got well into C# where they aren't so necessary. So I stopped. :doh: That's also why I always use redundant brackets for
ifandforconstructs:if (condition)
{
statement;
}Because in the old days (pre auto formatting)
if (condition)
statement;
statement;Looked too much like it executed both on the condition...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
Yep! Annoying that, isn't it? As a result, I always used brackets - which made the code messy - until I got well into C# where they aren't so necessary. So I stopped. :doh: That's also why I always use redundant brackets for
ifandforconstructs:if (condition)
{
statement;
}Because in the old days (pre auto formatting)
if (condition)
statement;
statement;Looked too much like it executed both on the condition...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
Oh yeah, those kind of things can make you run around in circles for an unpleasant amount of time :sigh:
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
Oh yeah, those kind of things can make you run around in circles for an unpleasant amount of time :sigh:
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
I was sooooo happy when compilers started giving a warning on
if (condition);
{
statement;
}:laugh:
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
I was sooooo happy when compilers started giving a warning on
if (condition);
{
statement;
}:laugh:
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
Oh yes, received a couple of those myself. Bless the little green underline. :)
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
So, today I saw this on CP's daily news: How One Missing `var` Ruined our Launch[^] There's always been endless discussions that it's not about the language, but about the programmer when bad practices arise. Like endless flaming wars against languages VB and JS. Now, to add some more fuel to the debate I'd like to ask: Why some mistake like that happened? It was a simple mistake with serious consequences. The first thing that came to my mind was that, I'd never make such a mistake (ok, maybe 0.00000001% of chance to make it). To me it's like driving without seat-belts. There's no way I'd do it because Brazilian traffic laws are so strict about it that I got very used to it, the same way I'm used to wear clothes when I leave home. Now, by programming on strict languages for the most part of my professional life, declaring variables became the same way, it's just natural, it would feels wrong and just the thought of it bothers me. Would it be the same if I got used developing on more forgiving languages like JS? Do forgiving languages make us more sloppy? I think the forgiving languages may shape us to acquire bad habits. That's one of the reasons I favor C# to VB.Net. There were countless times that I heard: "Bad code can be written in any language". But that's not the point. I'm sure that if I had done more work in more forgiving languages I'd be much more likely to commit mistakes like that. That's why I favor strict languages more. They help you develop good habits that are independent of the fact of a good or bad programmer. Thoughts?
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
Except the problem here really wasn't with 'var' but with scope and scope can get you in most languages. Of course, if you want to start a list of what's wrong with javascript, it's going to get mighty long.
-
Except the problem here really wasn't with 'var' but with scope and scope can get you in most languages. Of course, if you want to start a list of what's wrong with javascript, it's going to get mighty long.
Joe Woodbury wrote:
Except the problem here really wasn't with 'var' but with scope and scope can get you in most languages.
But clearly for what the author said, he didn't have the intention to declare a global variable and that he had forgotten to use the var keyword. Combining that with JS behavior generated the problem. But again, the root of the problem is that javascript does not enforce variable declaration, creating a big potential for bad habits.
Joe Woodbury wrote:
Of course, if you want to start a list of what's wrong with javascript, it's going to get mighty long.
Couldn't agree more. This makes even more important having good habits.
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
Strict languages help a lot - if you listen to the warnings they give. (Personally I run with "treat warnings as errors" set on). For example:
if(myInt & 0x80 != 0)in C# is an error - the result is not bool. In C++ it just doesn't do what you expect... This one caught me in an answer in Q&A because I had got so used to C# telling me off that I assumed the operator precedence was correct when C++ didn't give me a warning or error...Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
That's why I never bother learning the precedence rules in a programming language, and fully parenthesize expressions. Yeah, the hoi polloi will look down their noses at my pansy-assed, belt-and-suspenders way of doing things, but then I don't have to debug stupid mistakes like in your expression.
if ((myInt & 0x80) != 0)
My mistakes are far more intelligent, and only make me want to stab someone in the face with a spoon. For example, today I had a project that kept getting unresolved references at link time, even though the import library was in the correct location, and a number of other projects linked to it with no problems. I spent four hours playing with linker options, copying the import library to various locations, and so on, before I finally found the problem. The compiler on the DLL project was set to not treat
wchar_tas a builtin type, while the compiler on project using the DLL was set to do so. The function signatures in the DLL therefore didn't match because of name mangling differences. Grrr... BTW: I was the one who screwed this up and had the compiler set differently in the two projects. One spoonicide, coming up.Software Zen:
delete this; -
Bah, for a second I thought this was about real software. Then I saw the name "MelonCard", and "techcrunch" and realized they were talking about web "programming". Next they be crying about the time they found out that they were not in fact visited by magical flying unicorns.
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
-
Joe Woodbury wrote:
Except the problem here really wasn't with 'var' but with scope and scope can get you in most languages.
But clearly for what the author said, he didn't have the intention to declare a global variable and that he had forgotten to use the var keyword. Combining that with JS behavior generated the problem. But again, the root of the problem is that javascript does not enforce variable declaration, creating a big potential for bad habits.
Joe Woodbury wrote:
Of course, if you want to start a list of what's wrong with javascript, it's going to get mighty long.
Couldn't agree more. This makes even more important having good habits.
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
Yep! Annoying that, isn't it? As a result, I always used brackets - which made the code messy - until I got well into C# where they aren't so necessary. So I stopped. :doh: That's also why I always use redundant brackets for
ifandforconstructs:if (condition)
{
statement;
}Because in the old days (pre auto formatting)
if (condition)
statement;
statement;Looked too much like it executed both on the condition...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
I really don't like indented braces. Just saying.
-
I was sooooo happy when compilers started giving a warning on
if (condition);
{
statement;
}:laugh:
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
I look forward to the day when compilers give a warning because you've indented the braces... ;)
-
I look forward to the day when compilers give a warning because you've indented the braces... ;)
:laugh: Tough!
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
Strict languages help a lot - if you listen to the warnings they give. (Personally I run with "treat warnings as errors" set on). For example:
if(myInt & 0x80 != 0)in C# is an error - the result is not bool. In C++ it just doesn't do what you expect... This one caught me in an answer in Q&A because I had got so used to C# telling me off that I assumed the operator precedence was correct when C++ didn't give me a warning or error...Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
OriginalGriff wrote:
if(myInt & 0x80 != 0)When I first saw this I was tempted to reply with a: "Whats wrong with this on C#?" Since I'm not used to perform bitwise ANDs on my dayly work I didn't realize that comparison operators had precedence over bitwise operators. I guess in C++ the result would be false (0) if myInt is different from 1?
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
I don't have a choice, I have to use C, but I do like using the easier languages. You can get more done with less pitfalls than with hard languages. But I think you are right. Yo need exposure to the hard ones to know how the machine realy works. That way you write better code in easy languages.
============================== Nothing to say.
I think that's a different issue. C++, used as a better C, issues a lot more type warnings, forcing you to check usage of types and catching certain classes of errors at compile time. A language can be low- or high-level, but still enforce type-checking to various degrees. Static typing can help catch a whole class of errors before running the program.
