4 ms·

This feels like a bastardization of the already questionable "Falsehoods _ believe about _" format.

by elaida73 26d ago

This feels like a bastardization of the already questionable "Falsehoods ___ believe about ___" format.

rcxdude 26d ago
How so? It's pretty within the format IMO.
- elaida73 26d ago
  Maybe I'm pulling at a fake distinction here but the progenitor blog posts of this format that I'm thinking of were incorrect models of constructs that almost everyone uses in their everyday life constantly ( names, dates, time etc ) Whereas I find it kinda unlikely that someone both knows what a DHCP server is, and holds a belief that there is only ever exactly one on their network?
  - rcxdude 26d ago
    Hmmm, In my experience programmers are often not particularly good at networking, and this can result in all kinds of bad assumptions (or awkward workarounds for things that could be much better solved at the network level).
- milch 25d ago
  Maybe I don't remember the names, dates, and others correctly but I don't think they had things like > Wi-Fi and Ethernet clients are equivalent peers on the LAN. > Wi-Fi and Ethernet clients aren’t equivalent peers on the LAN. To be honest I don't know what this is supposed to be telling me. They can or can't be on the same VLAN? They could have different or the same QoL? If we hammer traffic on both at the same time bad things may or may not happen? > Only IPv4 is running on my LAN. > Only IP is running on my LAN. > Okay, only IP, IPX/SPX, Phase IV, AppleTalk, VINES, NetBEUI, or SNA are running on my LAN. > Seriously? Practically I'm not sure how this affects someone writing a networked application. Sure, IPv4/IPv6, but if I get a bug report in the year 2026 that my application is broken because it doesn't work on the AppleTalk network, it gets a WONTFIX. Sure, maybe if I'm writing a low-level network driver or maintaining a mainframe application these are things I have to care about. I think that may be the difference between the other posts and this post - non-experts in Onomastics and Chronology deal with names and dates all the time, hence resulting in issues like government websites not accepting Ng as a last name because it is less than 3 characters or not allowing entering February 29th as a birthday.
_kb 26d ago
That format is considered harmful.
deleted 26d ago
[deleted]
throw0101a 26d ago
Falsehoods Programmers Believe about Weblog Posts

This feels like a bastardization of the already questionable "Falsehoods ___ believe about ___" format.

rcxdude 26d ago

How so? It's pretty within the format IMO.

elaida73 26d ago
Maybe I'm pulling at a fake distinction here but the progenitor blog posts of this format that I'm thinking of were incorrect models of constructs that almost everyone uses in their everyday life constantly ( names, dates, time etc ) Whereas I find it kinda unlikely that someone both knows what a DHCP server is, and holds a belief that there is only ever exactly one on their network?
- rcxdude 26d ago
  Hmmm, In my experience programmers are often not particularly good at networking, and this can result in all kinds of bad assumptions (or awkward workarounds for things that could be much better solved at the network level).
milch 25d ago
Maybe I don't remember the names, dates, and others correctly but I don't think they had things like > Wi-Fi and Ethernet clients are equivalent peers on the LAN. > Wi-Fi and Ethernet clients aren’t equivalent peers on the LAN. To be honest I don't know what this is supposed to be telling me. They can or can't be on the same VLAN? They could have different or the same QoL? If we hammer traffic on both at the same time bad things may or may not happen? > Only IPv4 is running on my LAN. > Only IP is running on my LAN. > Okay, only IP, IPX/SPX, Phase IV, AppleTalk, VINES, NetBEUI, or SNA are running on my LAN. > Seriously? Practically I'm not sure how this affects someone writing a networked application. Sure, IPv4/IPv6, but if I get a bug report in the year 2026 that my application is broken because it doesn't work on the AppleTalk network, it gets a WONTFIX. Sure, maybe if I'm writing a low-level network driver or maintaining a mainframe application these are things I have to care about. I think that may be the difference between the other posts and this post - non-experts in Onomastics and Chronology deal with names and dates all the time, hence resulting in issues like government websites not accepting Ng as a last name because it is less than 3 characters or not allowing entering February 29th as a birthday.

_kb 26d ago

That format is considered harmful.

deleted 26d ago

[deleted]

throw0101a 26d ago

Falsehoods Programmers Believe about Weblog Posts