feedback
Control and Correlation
The fastest way to learn something is to do something
An Article by David R. MacIverSuppose you have a problem to solve. What do you do?
Well, you sit down and think real hard, and after extensive and careful planning you try the well thought out and rigorous solution that you have thought up. Right?
No, wrong! Bad.
The correct thing to do when you have a problem is:
- Think for a short amount of time.
- Make sure it is safe to try things.
- Try something you think will work.
- Observe the result. If you succeeded, yay you solved the problem! If it didn't work, think about what that means for the nature of the problem and try again.
How can we develop transformative tools for thought?
A Research Paper by Andy Matuschak & Michael NielsenConventional tech industry product practice will not produce deep enough subject matter insights to create transformative tools for thought.
...The aspiration is for any team serious about making transformative tools for thought. It’s to create a culture that combines the best parts of modern product practice with the best parts of the (very different) modern research culture. You need the insight-through-making loop to operate, whereby deep, original insights about the subject feed back to change and improve the system, and changes to the system result in deep, original insights about the subject.
When Customer Journeys Don’t Work: Arcs, Loops, & Terrain
An Article by Stephen P. AndersonThinking [in terms of loops and arcs] allows us to let go of a specific journey or sequence, and imagine dozens of scenarios and possible sequences in which these skills can be learned. This doesn’t mean there aren’t more fundamental skills that other skills build upon, but we can let go the tyranny of how, precisely, a person will move through a system. We’re free to zoom in and obsess on these loops, which does two things for us:
- Approach the design of a system as the design of these as small but significant moments of learning.
- Consider the many ways these loops might be sequenced, with the exact order being less important.
Asynchronous Design Critique: Getting Feedback
An Article by Erin CasaliGetting feedback can be thought of as a form of design research. In the same way that we wouldn’t do any research without the right questions to get the insights that we need, the best way to ask for feedback is also to craft sharp questions.
It's All Over
It has come to seem to me recently that this present moment must be to language something like what the Industrial Revolution was to textiles. A writer who works on the old system of production can spend days crafting a sentence, putting what feels like a worthy idea into language, only to find, once finished, that the internet has already produced countless sentences that are more or less just like it, even if these lack the same artisanal origin story that we imagine gives writing its soul. There is, it seems to me, no more place for writers and thinkers in our future than, since the nineteenth century, there has been for weavers.
Into the system of flight
It seems this transformation, from physical object to vector of data, is a general and oft-repeated process in the history of technology, where new inventions begin in an early experimental phase in which they are treated and behave as singular individual things, but then evolve into vectors in a diffuse and regimented system as the technology advances and becomes standardized.
In the early history of aviation, airplanes were just airplanes, and each time a plane landed or crashed was a singular event. Today, I am told by airline-industry insiders, if you are a billionaire interested in starting your own airline, it is far easier to procure leases for actual physical airplanes, than it is to obtain approval for a new flight route. Making the individual thing fly is not a problem; inserting it into the system of flight, getting its data relayed to the ATC towers and to flightaware.com, is.
The gutting of our human subjecthood
Someone who thinks about their place in the world in terms of the structural violence inflicted on them as they move through it is thinking of themselves, among other things, in structural terms, which is to say, again among other things, not as subjects. This gutting of our human subjecthood is currently being stoked and exacerbated, and integrated into a causal loop with, the financial incentives of the tech companies. People are now speaking in a way that results directly from the recent moneyballing of all of human existence.
A performative contradiction
I have found myself coming away from discussions with my good PR people feeling vaguely guilty that I do not have enough followers on Twitter (five thousand is the cut-off, I think) to be considered an “influencer,” or even just a “micro-influencer,” and feeling dismayed to learn that part of what is involved in launching a book like this into the world is strategizing over how to catch the attention of a true influencer, for a retweet or some other metrically meaningful shout-out. You would be a fool to think that it is the argument of the book, the carefully crafted sentences themselves, that are doing the influencing.
And yet for me to try to insert myself into the metrics-driven system would be a performative contradiction, since the book itself is an extended philippic against this system. And so what I do? I play along, as best I can, until I start to feel ashamed of myself. I contradict myself.
The one reveals a subject and the other reveals an algorithm
My own book may be crap, but I am certain, when such an imbalance in profitability as the one I have just described emerges, between photojournalism and selfies, that it is all over. This is not a critical judgment. I am not saying that the photos of Pol Pot are good and the selfies are bad. I am saying that the one reveals a subject and the other reveals an algorithm, and that when everything in our society is driven and sustained in existence by the latter, it is all over.