5 ms·

This is so bizarre, what questions are you getting that require you to refer to the rfc - something with such detail that it covers things like how many bytes a

This is so bizarre, what questions are you getting that require you to refer to the rfc - something with such detail that it covers things like how many bytes are allocated to which field. If you're doing something so niche like some kind of network analysis tool, then your colleagues should already have the rfcs as a very basic reference. Otherwise, if someone is asking very practical questions like, how to add a cname or something, then rfcs are way too theoretical.

axaxs 5y ago
No offense, but this is a typical thought, and one that shows that you've no idea the hundreds of corner cases that trap you. There's a reason 'its always DNS' is a meme. A simple example. Someone makes a new domain name, cnames it to their previous domain for web, and adds an MX record for emails. Why doesn't it work? I'm sure you can Google the answer. But this stuff comes up -all- the time
- KronisLV 5y ago
  If people trip up with certain things all the time, then is the technology itself suited for the problems that people need to solve? Because at that point, it feels like people are serving the technology and its many quirks, not the other way around. But regardless of that thought, i think both your words and those of the parent comment have merit - different levels of detail fit into different pieces of text (RFCs, vs a "How To" blog post), which fit different purposes. The quality of the information in either, however, still remains in question (given that some popular implementations of technologies, don't always even respect RFCs fully).
- loopz 5y ago
  IT desk pro tip: 1) Have you checked DNS? It's usually a problem with DNS. 2. Have you tried turning it off and on again? 3) Is the power cable plugged in the socket? 4) Sigh, I'll travel up to look at it. Done! :)

5 ms·

This is so bizarre, what questions are you getting that require you to refer to the rfc - something with such detail that it covers things like how many bytes a

by preommr 5y ago

axaxs 5y ago
No offense, but this is a typical thought, and one that shows that you've no idea the hundreds of corner cases that trap you. There's a reason 'its always DNS' is a meme. A simple example. Someone makes a new domain name, cnames it to their previous domain for web, and adds an MX record for emails. Why doesn't it work? I'm sure you can Google the answer. But this stuff comes up -all- the time
- KronisLV 5y ago
  If people trip up with certain things all the time, then is the technology itself suited for the problems that people need to solve? Because at that point, it feels like people are serving the technology and its many quirks, not the other way around. But regardless of that thought, i think both your words and those of the parent comment have merit - different levels of detail fit into different pieces of text (RFCs, vs a "How To" blog post), which fit different purposes. The quality of the information in either, however, still remains in question (given that some popular implementations of technologies, don't always even respect RFCs fully).
- loopz 5y ago
  IT desk pro tip: 1) Have you checked DNS? It's usually a problem with DNS. 2. Have you tried turning it off and on again? 3) Is the power cable plugged in the socket? 4) Sigh, I'll travel up to look at it. Done! :)