I know, 3 of the easiest things there are.

Probably because, unlike network-knowledge-first folks, like sysadmins and those in the networking specialty fields, developers were not exposed to the lower level concepts of things like DNS, TCP/IP, etc. So they just assume one puts in a domain name in a few places, and it all should just work. And generally, when people in the appropriate specialties are in charge of things like DNS, it does. Unfortunately, this all falls apart when the dev wants to migrate/move services, or when things do break, and their networking people aren't around to fix things. Then, they go looking up the inner workings of DNS, and get overwhelmed with jargon, and assume its complicated.

Its the same idea as the fact that we all live/work in buildings of some sort, and yet, only the architects really know precisely how big a load-baring wall has to be in order the building doesn't collapse. Its no one's fault, our brains are just wired to know what we really need to know.

Some didn't get the joke.

It’s not DNS
There’s no way it’s DNS
It was DNS

@lrosa @nixCraft If you hadn't posted this haiku, I would have.

indeed. It's just a next level phonebook ;)

and serial off-by-one errors

Have you ever seen developers working on a project argue discuss about how to name a function? Pity their wives when it comes to naming their children.