LWers try to figure things out from relatively simple principles
If you only do this you are going to fail. This is why Aristotle got physics so badly wrong, right? Reasoning has to be a cyclical process of compressing complex realities into sets of simple principles and only then are you licensed to decompress those principles into making statements about reality.
Addressing common misconceptions is worthwhile, and lists are a good way to do it. You can find similar lists in the academic literature for many different subjects, e.g., here's an article about common misconceptions in thermodynamics. I've also mentioned math books listing counterexamples before. Many counterexamples address common misconceptions.
I like to create Anki cards for common misconceptions, to make sure I don't makes these mistakes myself. One issue with this is whether correcting specific cases causes my brain to recognize a more general case....
So while many of these false beliefs are worth noting, it's worth thinking why programmers make these mistakes in practice. While it might be the case that names can include numbers, it's probably also going to be the case that the majority of numbers get into names via user error. Depending on the purpose of your database, it might be more valuable to avoid user error, than avoid a minority of users being excluded.
The reason I mention this is a lot of things in life are a study in trade offs. Quantum mechanics isn't very good at describing how big things work, and classical mechanics isn't very good at describing how small things work.
Weirdly, there is no list of falsehoods programmers believe about html (or at least a fast search didn't turn anything up).
A lot of programmers believe they can parse HTML with regular expressions.
From Falsehoods Programmers Believe About Names:
anything someone tells you is their name is — by definition — an appropriate identifier for them.
There should be a list of false things people coming from common law jurisdictions believe about how choice of identity works on the rest of the globe.
Sometimes a user puts something in a "name" field that they do not actually intend to be used to identify themselves.
They may be trying to get that string displayed to other users in a highlighted fashion. If someone puts "Wal-Mart Sucks" in the name field on a blog comment, it isn't because they seriously want to be identified by the surname of Sucks. They're just saying that Wal-Mart sucks, in a dramatic way.
They may be trying to break the system in one way or another. If someone puts their name as "Robert'; drop table students; --" then depending on the social and technical context they might be giving themselves a clever alias; or they might be trying to attack the database.
I think it's worth noting that, yes, if you want your database of names/addresses/times/etc. to be fully robust, you need to essentially represent these items as unconstrained strings of arbitrary length (including zero).
However, in practice, most likely you're not building a fully robust database. For example, you are not solving the problem of, "how can I fully represent all of the marvelous variety of human names and addresses ?", but rather, "how can I maximize the changes that the packages my company is shipping to customers will actual...
Also, there is a place where the sun rises in the west and sets in the east.
(Gur fha evfrf orpnhfr bs gur Rnegu'f ebgngvba, ohg rira va gur nofrapr bs gur Rnegu'f ebgngvba vg jbhyq evfr naq frg bapr n lrne orpnhfr bs ubj gur Rnegu'f nkvf cbvagf. Vs lbh ner pybfr rabhtu gb gur Abegu Cbyr, gur ebgngvba unf artyvtvoyr pbagevohgvba gb gur fha'f evfvat naq frggvat naq gur fha evfrf naq frgf cerggl zhpu bayl orpnhfr bs gur nkvf. Tb gb gur Abegu Cbyr, frr jurer gur fha evfrf, naq tb njnl sebz gur cbyr n fubeg qvfgnapr va n qverpgvba fhpu gung guvf cbvag vf gb gur jrfg.)
A problem of believing something wrong could also be a problem of classification or problem of language. There is so much lost in translation and as far as a programmer is concerned they deal with a very formal language. So they are not as good at informal languages and nuances.
I'm not a programmer, so my view may be a little bit skewed.. but this seems like a list of things that may or may not be correct (and I'd like to put things in a continuum, or percentages, or some other more practically observable other than a list) but it doesn't really get any further than that. How substantial many of the claims are?
I honestly doubt "programmers" get all these wrong. I'm not going to link to a post (I've seen some people replying with a post as if it's a substitute for actually saying what's wrong) or even say that "prog...
Could you turn the tracking links into direct ones?
They are not support, they are examples.
OK, understood.
Firstly, baseless discrimination is market-inefficient.
True, but (1) if the group you're discriminating against is a minority then the inefficiency may not be large and (2) if your other (potential) customers happen to approve of your discrimination then the gain in their custom may outweigh the loss in the others'.
You may recall the recent case of a pizza place -- was it called Memories Pizza? -- whose owners made the mistake of admitting on camera that they would be reluctant to cater for a hypothetical same-sex wedding. They got a lot of adverse comments. They closed up shop. They put up a page on GoFundMe or some such site. ... And then they got, I would guess, comfortably more money from donations in a few weeks than the profits their pizza restaurant could have produced in, say, a year.
What proportion of stores [...]
Understood; as I said, "This argument works only in so far as there's enough prejudice [...] that the groups in question really do suffer substantial systematic harm". I don't think the issue is that if it were legal then all the shops would put up "No members of group X" signs and members of group X would starve and freeze to death; it's more an Overton window thing. Some shops would put up those signs; lots of employers would quietly decline to hire people they thought were black/Jewish/female/gay/trans; it would be universally understood that discrimination against those people is normal; people would feel virtuous for being somewhat less prejudiced against them than average; and so members of the group in question would face a constantly harder life than the rest of us. A law saying "nope, not allowed to do that" about the most blatant kinds of discrimination, I think, reduces the subtler kinds too.
I could be wrong. You refer to a "fair amount of literature"; are there studies out there that investigate this and find that anti-discrimination laws don't have any such effect?
I'm not talking about the sign of the argument to the function, I'm talking about the nature of the function itself.
As you say, intolerance is perennial. It seems to me that what's changed over the last few decades is the sign (or phase, or something) of the argument, not the function. In other words, I really don't think what we're looking at is an increase in mandatory enforcement of politeness-and-decency, it's a change in what sort of thing counts as politeness-and-decency.
And if the victims of that now are (e.g.) the opponents of same-sex marriage, it seems clear to me that they have it a lot better than the previous victims did. Brendan Eich can't be CEO of Mozilla, apparently, but at least he can get married if he wants and no one is sending him to jail or forcing on him a course of chemical treatment designed to change his opinions. Life is more comfortable for opponents of same-sex marriage now than it was for gay people ten years ago, and vastly more comfortable than it was for gay people sixty years ago. So: yeah, intolerance is perennial, and its distribution is changing, but there's a good case to be made that there's less of it now and its consequences are milder than before.
I could be wrong.
To be wrong, first you need to take a falsifiable position :-)
I really don't think what we're looking at is an increase in mandatory enforcement of politeness-and-decency
Well, that's the issue in dispute here. It's a complex problem and requires analysis too serious for a few LW comments, but I don't think you can simply handwave it away. In the UK in particular the recent focus on criminalizing certain kinds of speech is quite troubling.
There are some long lists of false beliefs that programmers hold. isn't because programmers are especially likely to be more wrong than anyone else, it's just that programming offers a better opportunity than most people get to find out how incomplete their model of the world is.
I'm posting about this here, not just because this information has a decent chance of being both entertaining and useful, but because LWers try to figure things out from relatively simple principles-- who knows what simplifying assumptions might be tripping us up?
The classic (and I think the first) was about names. There have been a few more lists created since then.
Time. And time zones. Crowd-sourced time errors.
Addresses. Possibly more about addresses. I haven't compared the lists.
Gender. This is so short I assume it's seriously incomplete.
Networks. Weirdly, there is no list of falsehoods programmers believe about html (or at least a fast search didn't turn anything up). Don't trust the words in the url.
Distributed computing Build systems.
Poem about character conversion.
I got started on the subject because of this about testing your code, which was posted by Andrew Ducker.