> Programming a library referencing an RFC seems kind, the rules are already there. Depends. Is there a reference implementation? A format/protocol validator?

> Programming a library referencing an RFC seems kind, the rules are already there. Depends. Is there a reference implementation? A format/protocol validator? An interoperability matrix? What's the ratio of SHOULDs and MAYs to REQUIREDs, SHALLs, and MUSTs? Does the RFC reference other RFCs? What are the answers to these questions regarding those? I mean, I wouldn't ever describe the task of implementing a SOAP[0] or WebDAV[1] library as 'kind'. Oh, and if you're working at a sufficiently large org, be prepared to battle it out with a competing internal implementation for the coveted position of 'company standard'. Note that you (or your boss) may not actually want to win that battle, as internal customers will make all sorts of unreasonable demands[2], and implementing them all will cut into your real work and negatively affect your evaluations and career advancement. Also, refusing to implement those requests will get you labelled as "not a team player" and negatively affect your evaluations and career advancement. Fun times! [0] https://www.shlomifish.org/humour/by-others/s-stands-for-simple/ https://www.shlomifish.org/humour/by-others/s-stands-for-sim... [1] https://www.slideshare.net/mobile/tobyS/webdav-the-good-the-bad-and-the-evil https://www.slideshare.net/mobile/tobyS/webdav-the-good-the-... [2] https://dilbert.com/strip/1995-11-17 https://dilbert.com/strip/1995-11-17