2 ms·
I grew up referencing RFCs in network software land. Then I got a few gigs with eletronics and the first years were the most depressive of my life. every step s
by gcb0 8y ago
I grew up referencing RFCs in network software land. Then I got a few gigs with eletronics and the first years were the most depressive of my life. every step started with a research for some standard, then the request to purchase it, then in some cases the mailing of some agreement contract, then the wait, to finally see the standard just referenced some other standard, so back to step one.
- Freak_NL 8y agoIt's the same in information technology too when you move beyond the actual protocols and languages (which tend to be free and open). You get the joy of having to buy some healthcare related standard from your national registry, only to find that it refers to the corresponding ISO standards with hardly a change, so you get to shell out some Swiss Francs for one of those. Sensibly enough, the Dutch government made a set of related healthcare IT standards free of charge when the legislature started mandating their use (NEN 7510, 7512, 7513), but they still reference loads of non-free ISO standards for the most trivial of things. You don't really know whether a reference is relevant or not without looking it up. When you read these things it is always a relief to find a reference to an IETF RFC; that at least means you get a searchable HTML document available at a reliable location for anyone to read.