Finding nourishment vs. identifying poison An Article by Austin Kleon & Olivia Laing austinkleon.com A useful analogy for what [Sedgwick] calls ‘reparative reading’ is to be fundamentally more invested in finding nourishment than identifying poison. This doesn’t mean being naive or undeceived, unaware of crisis or undamaged by oppression. What it does mean is being driven to find or invent something new and sustaining out of inimical environments. I would like to adopt that line as a mission statement: “To be fundamentally more invested in finding nourishment rather than identify poison.” Because you can identify all the poison you want, but if you don’t find nourishment, you’ll starve to death. Poison sniffers hopereadinggoodness
Solution to evaluation and back again A second reason the systems engineer’s design is never completed is the solution offered to the original problem usually produces both deeper insight and dissatisfactions in the engineers themselves. Furthermore, while the design phase continually goes from proposed solution to evaluation and back again and again, there comes a time when this process of redefinement must stop and the real problem be coped with—thus giving what they realize is, in the long run, a suboptimal solution. Richard Hamming, The Art of Doing Science and Engineering: Learning to Learn Co-Evolution of Problem and Solution Spaces in Creative Design