3 ms·
Simple solution: if you ever run into this, blog about it and mark it as a freak occurrence, because it is. Don't ever in real work worry about stupid edge case
by cornel_io 2y ago
Simple solution: if you ever run into this, blog about it and mark it as a freak occurrence, because it is. Don't ever in real work worry about stupid edge cases like this or you're wasting your employer's money. I'd reprimand an engineer for spending more than an hour on this, it serves nobody unless you're working on extremely widely used library code.
- TeMPOraL 2y agoThis is why Unix practice of being so thoroughly stringly-typed is bad, especially when combined with advice like yours. At every stage, someone is going to cut corners and don't parse just that one "freak occurrence". Then someone wants to wire a bunch of things together and they start to fail, as with so many corners cut on the way, you're bound to hit one. And it all starts with stringly typed data and asking everyone to make half-baked parsers and serializers on the fly.