4 ms·
Yeah, being able to distinguish these cases is an important skill. One case I learned the hard way (once!) is parsing/writing CSV files. It seems so simple. Bu
by BurningFrog 11y ago
Yeah, being able to distinguish these cases is an important skill.
One case I learned the hard way (once!) is parsing/writing CSV files. It seems so simple. But there are 3-5 special cases that are hard and rare enough that you always should use the standard library written for your language.
Perhaps admitting your original decision didn't work out and and starting over is the real important skill...
- userbinator 11y agoParsing standard CSV isn't that hard (I've written one) when you have a spec to follow: https://tools.ietf.org/html/rfc4180 https://tools.ietf.org/html/rfc4180 But in my experience, a lot of generated CSV is non-standard, and in that case finding a library to do it doesn't help --- you need to write your own parser so you can adapt it to the quirks of the variant(s) you're consuming.
- wnoise 11y agoAlthough cleaning filters and a standard parser works well too.
- Chris2048 11y agoHmm, I'm not sure I like this. It would ultimately be an assessment of your own ignorance of a subject. Maybe coding based on researching solutions is a good way to do things - we just need to make it more efficient. Looking for an existing implementation, when a "10m implementation will do" - How do you know it will do if you've not researched more? When do you stop? I think risk-assessment should be more of a thing in software development. We can't really know where the bugs might be, but we can know where we'd like them the least?