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.
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.