HN user
"Bob"'s problem was counterproductive pride and being unteachable. There is no room for ego in a precise profession like ours, and none of us writes perfect code. If "Bob" had learned from his peers during code reviews, he would have been fine.
To answer your question: The Pragmatic Programmer by David Thomas and Andrew Hunt, Writing Solid Code by Steve Maguire, and Code Complete by Steve McConnell.
In these discussions about the importance of metadata, I'm surprised that Bitmessage is rarely mentioned. The Bitmessage protocol is decentralized, trustless, and hides metadata such as the sender and receiver of messages.
When I was a comp sci student in the 90s, I was testing some code where I used foo@bar.com as a placeholder. Amusingly, I got a reply from The Foo, and now I'm glad to know I wasn't the only one who accidentally emailed him/her.
As others have pointed out, username@example.com is a better choice for documentation and examples.
Could you give an example of such a comparison?
Are you saying rich people are better able to estimate the risks and trade-offs for their decisions?
Actually, rsync.net is owned by the same people who run JohnCompanies.com, which is an excellent FreeBSD virtual hosting company.