51–60 of 139 posts
This is a good list, but it would be so much better with some (brief) pointers to counter-examples to the beliefs.
The original one ( http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-b... ) left me bafled. Then I realized you have to strike a balance; otherwise you cannot deal with names at all. The point where drawing the line depends on your industry/customers, but I'd safely say that it's too restrictive nowadays so these lists are useful somewhat and of course they are interesting.
Interlaced video files should no longer exist.
Seriously, fk interlaced video.
> upscaling algorithms can invent information that doesn’t exist in the image
That's not a falsehood. Upscaling does invent information that doesn't exist in the image.
it is true, video is a nightmare mess littered with weird functionality nobody needs. (limited range only just disappeared in rec 2100, optionally??? really??? i'm not worried about my electron gun in my CRT from 1975 these days...nor do i want to know what a Y or a Cb or a Cr means because everything is RGB and B&W TV is long dead... and 4:2:2 is not exactly compression so much as computational overhead etc.. etc.)…
Try experimenting with chroma subsampling in JPGs, but note that not all image viewers have good chroma upscaling. MPV can display still images as well as video and you can choose the chroma scaling algorithm.
Earlier quoted context omitted.
That's easy, it's to make better marketing materials. "Dear [first name]," flows better than "Dear [opaque string],".
That's what the marketing department may believe, but in reality that's super creepy. Let's not pretend that I'm on a friendly first-name basis with corporations, or that in reality I'm anything more than an autogenerated numeric ID in a database as far as the corporation is concerned. Furthermore, nobody but my mother calls me by my real first name, and this holds for half of my cohort. And why does any company thin…
Really? I've been assuming that addressing people by first name--even people you've just met--is now the default, at least for the United States and Canada. Are you in the USA/Canada, by the way?
I know that it used to be rude to address someone by their first name unless you knew them well. You had to say, Mr. last-name or Mrs/Ms./Miss last-name. I know this from old movies.
But I thought that the etiquette has changed completely: First name is fine and last name sounds rather formal. Do others have a different experience?
> interlaced video files no longer exist Interlaced video files should no longer exist. Seriously, f k interlaced video. > upscaling algorithms can invent information that doesn’t exist in the image That's not a falsehood. Upscaling does invent information that doesn't exist in the image.
The original one ( http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-b... ) left me bafled. Then I realized you have to strike a balance; otherwise you cannot deal with names at all. The point where drawing the line depends on your industry/customers, but I'd safely say that it's too restrictive nowadays so these lists are useful somewhat and of course they are interesting.
It's true that you have to draw a line somewhere based on technical and business constraints, but an important takeaway of the names article is that you almost certainly don't need to do anything with a name other than treat it as an opaque string that can be displayed back to the user. For example, I'm struggling to think of a good reason why user registration would require separate first name and last name fields,…
I've no direct experience with, say, Russian or Latin American governments, but cultures that use explicit patronymic or matronymic names might expect that broken out as well.
If you ever need to submit user data to the government (e.g. for tax reasons), and you don't ask your user to break the name apart, then you will necessarily be guessing, which seems strictly worse than just asking them how their name might split.
At the end of the day, if you operate in a given culture, then you need to address those cultural norms. Bending over backwards to support every possible edge case seems unwise if they also happen to disagree with those norms.
This is a good list, but it would be so much better with some (brief) pointers to counter-examples to the beliefs.
This unfortunately follows the conventions of the genre called "Falsehood programmers believe about X": http://spaceninja.com/2015/12/08/falsehoods-programmers-beli... I honestly think this genre is horrible and counterproductive, even though the writer's intentions are good. It gives no examples, no explanations, no guidelines for proper implementations - just a list of condescending gotchas, showing off the superio…
A better approach would be to pick the list up and turn them into a collaborative work. Wiki, maybe?
> interlaced video files no longer exist Interlaced video files should no longer exist. Seriously, f k interlaced video. > upscaling algorithms can invent information that doesn’t exist in the image That's not a falsehood. Upscaling does invent information that doesn't exist in the image.
The upscaled image does not have more information than what was in the original image; you can reconstruct the upscaled image given only the information available in the original image, the output resolution dimensions, and upscaling algorithm.
> interlaced video files no longer exist Interlaced video files should no longer exist. Seriously, f k interlaced video. > upscaling algorithms can invent information that doesn’t exist in the image That's not a falsehood. Upscaling does invent information that doesn't exist in the image.
Perhaps that author was being pendantic, but from an information theroetic perspective it is correct that you cannot invent information with upscaling. The upscaled image does not have more information than what was in the original image; you can reconstruct the upscaled image given only the information available in the original image, the output resolution dimensions, and upscaling algorithm.