Love
Love without ownership
Someone in the world awaits you
And thus the heart will break
The productions of time
You are what you love
We need an object for our affections
The people we love
For their own concealed passion
Perhaps one did not want to be loved so much as to be understood.
The significance of love's burden
We outgrow love
I marshmallow you
100% perfect
That delicate and complex instrument
When it goes wrong
Exploiting emotion
Upstream Color
Childe Harold's Pilgrimage
Narcissus and Goldmund
The Alchemist
500 Days of Summer
the speed of God
155-217-155
Trust beyond reason
An Article by David R. MacIverIn this sense, trust is a polarizing strategy, and it's one that is important to apply early on in the relationship before someone becomes important to you. If you trust someone excessively and it goes badly, but they don't matter to you, you can just kick them to the curb. In general, trusting someone at a level that seems slightly excessive for their level of importance to you will help you sort people in your life who you want to be more important to you than they are from those who you want to be less important than they are.
And it does need to be excessive. It needs to be trust beyond reason. Not beyond all reason, but somewhat beyond what currently seems reasonable. If it is not, then unless they are prepared to take the first move, you will never find the signs you need to move to a higher level of mutual trust.
Sometimes this will go badly, but you need to be able to try bad things.
The mortifying ordeal of being known
A Fragment by Tim KreiderYears ago a friend of mine had a dream about a strange invention; a staircase you could descend deep underground, in which you heard recordings of all the things anyone had ever said about you, both good and bad. The catch was, you had to pass through all the worst things people had said before you could get to the highest compliments at the very bottom. There is no way I would ever make it more than two and a half steps down such a staircase, but I understand its terrible logic: if we want the rewards of being loved we have to submit to the mortifying ordeal of being known.
Which Books You Truly Love
An Essay by Salman RushdieI believe that the books and stories we fall in love with make us who we are, or, not to claim too much, the beloved tale becomes a part of the way in which we understand things and make judgments and choices in our daily lives. A book may cease to speak to us as we grow older, and our feeling for it will fade. Or we may suddenly, as our lives shape and hopefully increase our understanding, be able to appreciate a book we dismissed earlier; we may suddenly be able to hear its music, to be enraptured by its song.
All There Is
A Song by Gregory Alan IsakovAnd I lied to you when I knocked upon your door.
See, I was nowhere near your neighborhood.The life and death of an internet onion
In her piece "A drop of love in the cloud" (2018), artist Fei Liu writes about the like/heart button as a flattening affordance of giving affirmation and love. The text-editor provides a much more expressive input.
But even people who can't communicate well because of language barriers can express love through actions, like cooking food. Can we create other "love inputs" that might allow us to "reach across the chasm of a seamless signal"?
What is expressing "real" love or affirmation about? Is it about effort, thoughtfulness, generosity, something else? What might a thoughtful or generous interface feel or behave like?
A Plea for Lean Software
Software's girth has surpassed its functionality, largely because hardware advances make this possible. The way to streamline software lies in disciplined methodologies and a return to the essentials.
Measured by the number of its features
A primary cause of complexity is that software vendors uncritically adopt almost any feature that users want. Any incompatibility with the original system concept is either ignored or passes unrecognized, which renders the design more complicated and its use more cumbersome. When a system's power is measured by the number of its features, quantity becomes more important than quality. Every new release must offer additional features, even if some don't add functionality.
Essential vs. nice to have
Customers have trouble distinguishing between essential features and those that are just "nice to have." Examples of the latter class: those arbitrarily overlapping windows suggested by the uncritically but widely adopted desktop metaphor; and fancy icons decorating the screen display, such as antique mailboxes and garbage cans that are further enhanced by the visible movement of selected items toward their ultimate destination. These details are cute but not essential, and they have a hidden cost.
/
Increased complexity results in large part from our recent penchant for friendly user interaction. I've already mentioned windows and icons; color, gray-scales, shadows, pop-ups, pictures, and all kinds of gadgets can easily be added.
Dependence is more profitable than education
A customer who pays—in advance—for service contracts is a more stable income source than a customer who has fully mastered a product's use.
Customer dependence is more profitable than customer education.
What I find truly baffling are manuals—hundreds of pages long—that accompany software applications, programming languages, and operating systems. Unmistakably, they signal both a contorted design that lacks clear concepts and an intent to hook customers.
The most rewarding iterations
Initial designs for sophisticated software applications are invariably complicated, even when developed by competent engineers. Truly good solutions emerge after iterative improvements or after redesigns that exploit new insights, and the most rewarding iterations are those that result in program simplifications.
Evolutions of this kind, however, are extremely rare in current software practice—they require time-consuming thought processes that are rarely rewarded. Instead, software inadequacies are typically corrected by quickly conceived additions that invariably result in the well-known bulk.
Never enough time
Time pressure is probably the foremost reason behind the emergence of bulky software. The time pressure that designers endure discourages careful planning. It also discourages improving acceptable solutions; instead, it encourages quickly conceived software additions and corrections. Time pressure gradually corrupts an engineer's standard of quality and perfection. It has a detrimental effect on people as well as products.