It's still lossy! Maybe it isn't lossy to the human ear, but what is the data going to be used for? There are assumptions you're building in here. What if I'm now interested in using the data for a bat ear model? All of a sudden, that information is now of limited use.
She's saying "be aware of your assumptions." Her entire screed is a call to take a step back, and recognize that programming is reifying assumptions and systems of control. Be aware of what those happen to be. Make those choices conscious, rather than unconscious.
When I'm creating a UI, am I assuming the viewer has 20/20 corrected vision on a 1920x1080 monitor with the full set of rods and cones? Am I considering folks that are colorblind, might need to have different zoom levels, or might use screen readers?
When I'm creating a tool for data analysis, am I making it for other programmers? Or can I maybe widen its usage to the business analysis side, thereby making the tool more useful to more people. When I change a tool, is it breaking someone else's workflow?
She's saying "be aware of your assumptions." Her entire screed is a call to take a step back, and recognize that programming is reifying assumptions and systems of control. Be aware of what those happen to be. Make those choices conscious, rather than unconscious.
When I'm creating a UI, am I assuming the viewer has 20/20 corrected vision on a 1920x1080 monitor with the full set of rods and cones? Am I considering folks that are colorblind, might need to have different zoom levels, or might use screen readers?
When I'm creating a tool for data analysis, am I making it for other programmers? Or can I maybe widen its usage to the business analysis side, thereby making the tool more useful to more people. When I change a tool, is it breaking someone else's workflow?