practice
Thinking in situations
Naturally, practice is not preceded but followed by theory.
Such study promotes a more lasting teaching and learning
through experience. Its aim is development of creativeness
realized in discovery and invention – the criteria of creativity,
or flexibility, being imagination and fantasy. Altogether
it promotes “thinking in situations,” a new educational concept
unfortunately little known and less cultivated, so far.Reaching 95
Reaching 95%-ile isn't very impressive because it's not that hard to do. I think this is one of my most ridiculable ideas. It doesn't help that, when stated nakedly, that sounds elitist. But I think it's just the opposite: most people can become (relatively) good at most things.
Note that when I say 95%-ile, I mean 95%-ile among people who participate, not all people (for many activities, just doing it at all makes you 99%-ile or above across all people). I'm also not referring to 95%-ile among people who practice regularly. The "one weird trick" is that, for a lot of activities, being something like 10%-ile among people who practice can make you something like 90%-ile or 99%-ile among people who participate.
Practice before theory
Instead of mechanically applying or merely implying laws and rules
of color harmony, distinct color effects are produced
– through recognition of the interaction of color –
by making, for instance,
2 very different colors look alike, or nearly alike.The aim of such study is to develop – through experience
– by trial and error – an eye for color.
This means, specifically, seeing color action
as well as feeling color relatedness.As a general training it means development of observation and articulation.
This book, therefore, does not follow an academic conception
of “theory and practice.”
It reverses this order and places practice before theory,
which, after all, is the conclusion of practice.Things you didn't know you can be bad at
An Article by David R. MacIverI wonder how many things we're all going around doing badly because the idea of not knowing how to do them well seems too ridiculous to admit to.
...You've probably never been taught to have a conversation. I've had exactly one class on it and it was in the last six months. I know damn well that many people have not self-taught this well... In general there's this entire class of implicit skills that we mostly don't think of as skills, that we're entirely self-taught on, and that we practice sufficiently non-demonstratively that we can't easily watch what other people do. The result is a very personal skill idiolect.
The Helsinki Bus Station Theory
An Article by Arno Rafael MinkkinenStay on the bus. Stay on the f*cking bus.
Why? Because if you do, in time you will begin to see a difference.
The buses that move out of Helsinki stay on the same line but only for a while, maybe a kilometer or two. Then they begin to separate, each number heading off to its own unique destination. Bus 33 suddenly goes north, bus 19 southwest.
...It’s the separation that makes all the difference, and once you start to see that difference in your work from the work you so admire (that’s why you chose that platform after all), it’s time to look for your breakthrough.
Suddenly your work starts to get noticed. Now you are working more on your own, making more of the difference between your work and what influenced it.
Your vision takes off.
Touch the keys
An Article by Rach SmithIn his course Being Productive: Simple Steps to Calm Focus, Kourosh Dini emphasises the importance of taking a moment to “be with” the work every day (or however frequently you need to tackle a project). “Being with” your work is to be fully present and intentional about that activity and doing nothing else.
This idea was inspired by Dini’s piano teacher, who encouraged him to sit at his piano and touch the keys every day. Even on the days that he felt he had no time or inclination to practice. Sometimes touching the keys would lead to a good practice session, even when he didn’t feel like it would before he actually gave it a go.
Just like Dini, I find that once I give the task my full attention and be present, the actual doing of it turns out to be much easier and more enjoyable than my mind had been expecting. As usual, the resistance to getting started is far more uncomfortable than actually doing the thing.
I completely ignored the front end development scene for 6 months. It was fine
An Article by Rach SmithWhat I’ve learnt through experience is that the number of languages I’ve learned or the specific frameworks I’ve gained experience with matters very little. What actually matters is my ability to up-skill quickly and effectively.
If you focus on:
- learning how you best learn, and
- practicing effectively communicating the things you've learned
you can't go wrong.
Writing and Speaking
An Essay by Paul GrahamBeing a really good speaker is not merely orthogonal to having good ideas, but in many ways pushes you in the opposite direction...there's a tradeoff between smoothness and ideas. All the time you spend practicing a talk, you could instead spend making it better.
Long Form Study: Why Photographers Should Repeatedly Revisit a Scene
An Article by Scott ReitherI learned years ago how important it is to shoot the same subject and location over and over again.
The practice teaches a photographer how to form deeper relationships with the subject, and better understand how the primary subject interacts with secondary elements – like the way high tide may introduce a stunning new reflection, or how a blaze of stars in a dark sky might be the missing element that lifts the image to new heights.
Revisiting a subject also serves as valuable “practice.” You cannot develop your skills in anything without a healthy (or obsessive) amount of practice. It always surprises me to find out aspiring photographers think that they can simply photograph their two-week vacations once or twice a year and come home with compelling imagery! It doesn’t work that way.
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.