Understanding
From a roving viewpoint
A state of quietness
In a state of reverberation
Practice before theory
When we say we know Hamlet
You only understand something relative to something you already understand
Mondegreen
Understanding its essence
How our understanding is working
Perhaps one did not want to be loved so much as to be understood.
Everything that can be said
Agents of thought and experiment
For one who can see
I don't think you understand
I think very well of him indeed
Admitting ignorance
Dead cities
Up and Down the Ladder of Abstraction
99% Invisible
Understanding Understanding
To Make a Book, Walk on a Book
When their salary depends on not understanding it
A Quote by Upton SinclairIt is difficult to get people to understand something, when their salary depends on not understanding it.
Keep digging
An Article by Ryan SingerThe hardest thing about customer interviews is knowing where to dig. An effective interview is more like a friendly interrogation. We don’t want to learn what customers think about the product, or what they like or dislike — we want to know what happened and how they chose... To get those answers we can’t just ask surface questions, we have to keep digging back behind the answers to find out what really happened.
Clues for software design in how we sketch maps of cities
An Article by Matt WebbGiven there’s an explosion in software to accrete and organise knowledge, is the page model really the best approach?
Perhaps the building blocks shouldn’t be pages or blocks, but
neighbourhoods
roads
rooms and doors
landmarks.Or rather, as a knowledge base or wiki develops, it should - just like a real city - encourage its users to gravitate towards these different fundamental elements. A page that starts to function a little bit like a road should transform into a slick navigation element, available on all its linked pages. A page which is functioning like a landmark should start being visible from two hops away.
How am I doing, wonder?
A Quote by Louis KahnForm comes from wonder. Wonder stems from our 'in touchness' with how we were made. One senses that nature records the process of what it makes, so that in what it makes there is also the records of how it was made. In touch with this record we are in wonder. This wonder gives rise to knowledge. But knowledge is related to other knowledge and this relation gives a sense of order, a sense of how they inter-relate in a harmony that makes all things exist. From knowledge to sense of order we then wink at wonder and say How am I doing, wonder?
Pellucidity
A DefinitionFree from obscurity and easy to understand; the comprehensibility of clear expression
What 80% Comprehension Feels Like
An ArticleOne of the major principles of extensive reading is that if a learner can comprehend material at 98% comprehension, she will acquire new words in context, in a painless, enjoyable way. But what is 98% comprehension?
The case for rereading
An Article by Mandy BrownReread a book enough times, or often enough—keep it at hand so you can flip to dog-eared pages and marked up passages here and there—and it will eventually root itself in your mind. It becomes both a reference point and a connector, a means of gathering your knowledge and experience, drawing it all together. It becomes the material through which you engage with the world.
How to Make a Complete Map of Every Thought You Think
An EssayWhat we have known since long
A Quote by Ludwig WittgensteinThe problems are solved, not by giving new information, but by arranging what we have known since long.
Making sense
A Quote by Pablo PicassoThe world doesn’t make sense, so why should I paint pictures that do?
I am an explorer
A Quote by C.S. LewisI do not sit down at my desk to put into in verse something that is already clear in my mind. If it were clear in my mind I would have no incentive or need to write about it. I am an explorer…We do not write in order to be understood, we write in order to understand.
The Fidelity Curve
How do we choose which level of fidelity is appropriate for a project?
I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing.
I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing.
Four levels of fidelity
Suppose we have four levels of fidelity…
- Rough sketch (on paper or an iPad)
- Static mock-up (eg. Photoshop or Sketch)
- Interactive mock-up (eg. Framer, InVision)
- Working code prototype (HTML/CSS, iOS views)
Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained
Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it.
Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.