2 ms·
I've worked with a lot of smart people in data-gathering fields (researchers, journalists, analysts)...the amount of human-hours wasted on cleaning up data that
by danso 14y ago
I've worked with a lot of smart people in data-gathering fields (researchers, journalists, analysts)...the amount of human-hours wasted on cleaning up data that was compiled by someone who didn't understand delimiting, normalization, or how operations can be repeated when we have a pattern (kind of like map-reduce) is near tragic.
Think if you worked at a publishing house in which you had a fantastic story-teller who was illiterate. This person could tell best-selling yarns, she just needed someone to actually put it down on paper. And then re-read to her outloud the sections (and entire chapters) when the material was edited and re-arranged.
Yes, you could still produce best-selling books this way. But it's not efficient. And the artist misses out on a lot of what could be done with more direct contact with the written text...and the worst part is, she doesn't know what she's missing out on.
edit: Note that I'm not saying that this hypothetical illiterate storyteller has to be a great writer (just like most people do not need to be excellent, best-practices programmers). She just needs to be good enough to re-arrange and re-read her own ideas and take a more active part in the editing process. Believe it or not, in the publishing business, there are amazing storytellers (or reporters) who are not very good writers.
- dietrichepp 14y ago1. Compare programming to home DIY. Sure, every year you'll have people who knock down load-bearing walls, get pesticide backwash into the drinking water, or turn a simple de-icing operation into a raging inferno. But people also assemble millions of shelves and beds, unclog millions of drains, and build thousands of greenhouses and planter boxes. 2. Professional programmers create awful messes too. They do it less often, but with greater consequences. Just like the contractors building a bridge are less likely to screw up than some goofball installing a new water heater at home, but a bad bridge is much more dangerous. Give people more training when the potential consequences of bad work are more severe, and less training when it's just not needed. 3. The value of someone with both domain knowledge and programming knowledge is usually immense. You can either teach a programmer about the domain, or you can teach a domain expert how to program. If you have a programmer with a bit of domain knowledge, then they know what kind of questions to ask the domain experts. If you have a domain expert with a bit of programming knowledge, then they know how to communicate technical requirements to a professional programmer. Let's take your analogy with the publishing house. If the fantastic storyteller can write but has major problems with grammar and continuity, then a good editor can clean things up.