Misinterpretation as inspiration A lot of people think dreams and drugs involve some magical inspiration. I think otherwise. I rarely get inspired by dreams or drugs, but I have my own secret source of inspiration: mishearing other people. Somebody says something, I misinterpret it, and the misinterpretation is quite interesting – more interesting than anything I would have come up with on my own if asked to generate an interesting idea. Maybe it’s a clever joke or turn of phrase. Maybe it’s a neat idea. Sometimes I misunderstand people’s entire positions, and end up with positions much more interesting than the ones they were trying to push. Scott Alexander, Negative Creativity slatestarcodex.com Mondegreen mistakesinterestdrugsdreamscreativitymondegreens
Poetic drugs In the final chapters Bachelard lets slip (a confession really) how if he "were a psychiatrist," he would recommend a poem by Baudelaire to treat "anguish." His squabble then is not with the purpose but rather the approach of a still-young profession. And of course, why not treat the power of great poems as something akin to "virtual 'drugs'"? Mark Z. Danielewski, The Poetics of Space psychologypoetrypaindrugs
Doubling Obetrolling didn't make me self-conscious. But it did make me much more self-aware. If I was in a room, and had taken an Obetrol or two with a glass of water and they'd taken effect, I was now not only in the room, but I was aware that I was in the room. In fact, I remember I would often think, or say to myself, quietly but very clearly, 'I am in this room.' It's difficult to explain this. At the time, I called it 'doubling', but I'm still not entirely sure what I meant by this, nor why it seemed so profound and cool to not only be in a room but be totally aware that I was in the room. David Foster Wallace, The Pale King drugsattention
Feature parity An Article martinfowler.com Whilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business. Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'. softwarefeaturesrepair