Craig Mod
Brilliant Hardware in the Valley of the Software Slump
An Article by Craig ModThanks Doc
An Article by Robin Rendle & Craig ModA couple of months back, Craig mentioned in a video that he has a doc filled to the brim with snippets of text—nice words, compliments, and thanks that had been sent his way for his work. Whenever someone says something nice he just copy/pastes it into that doc.
It sounds silly at first and perhaps a little egotistical. Behold! I have a document that proves how great I am!
But I started doing it just to see what it feels like and…hey…actually? It’s so great! When I’m feeling low (often) or whenever the world feels unstable (extremely often) it’s so very nice to return to a few kind words about my work. It reminds me just how much these words of praise mean, it reminds me that I ought to pass that favor along.
Delight is constraints, joyfully embraced
An Article by Craig ModAnd what is delight? For me, delight is born from a tool’s intuitiveness. Things just working without much thought or fiddling. Delight is a simple menu system you almost never have to use. Delight is a well-balanced weight on the shoulder, in the hand. Delight is the just-right tension on the aperture ring between stops. Delight is a single battery lasting all day. Delight is being able to knock out a 10,000 iso image and know it'll be usable. Delight is extracting gorgeous details from the cloak of shadows. Delight is firing off a number of shots without having to wait for the buffer to catch up. Delight is constraints, joyfully embraced.
Fast Software, the Best Software
An Essay by Craig ModI love fast software. That is, software speedy both in function and interface. Software with minimal to no lag between wanting to activate or manipulate something and the thing happening. Lightness.
Software that’s speedy usually means it’s focused. Like a good tool, it often means that it’s simple, but that’s not necessarily true. Speed in software is probably the most valuable, least valued asset. To me, speedy software is the difference between an application smoothly integrating into your life, and one called upon with great reluctance. Fastness in software is like great margins in a book — makes you smile without necessarily knowing why.
Looking Closely is Everything
An Essay by Craig ModKambara, detail by detail.
I’d say that that huh is the foundational block of curiosity. To get good at the huh is to get good at both paying attention and nurturing compassion; if you don’t notice, you can’t give a shit. But the huh is only half the equation. You gotta go huh, alright — the “alright,” the follow-up, the openness to what comes next is where the cascade lives. It’s the sometimes-sardonic, sometimes-optimistic engine driving the next huh and so on and so forth.
Ri — The Distance Walked in an Hour
An Article by Craig ModA ri is a unit of measure, it’s about how far a person can walk in an hour at a reasonable pace. It clocks out at roughly 3.93 kilometers.
Remnants of the ri system are scattered along the old roads of Japan. During the Edo period, ri were marked recurrently by hulking earthen mounds that flanked the road — ichi-ri zuka, “one-ri mounds.” There are only a handful of “originals” left. When you pass one with an old cypress or oak growing from its center it becomes a tiny moment of celebration.
A Need to Walk
An Essay by Craig ModWalking intrigues the deskbound. We romanticize it, but do we do it justice? Do we walk properly? Can one walk improperly and, if so, what happens when the walk is corrected?
Life as Protest
A Fragment by Craig ModI’ve written this before but I constantly need to remind myself of it, so, once again: A certain kind of work, lifestyle, mode of living — in and of itself — is protest. That is, work that is curious and rigorous is implicitly an antipode to didactic, shallow bombastity. It is inherently an archetype against bullshit. That to be committed to this work or life of rigor (be it rigor focused on “art” or, as they say in Japanese, sakuhin, or family or athleticism or whatever), and to share it with the world is to opt-out of being paralyzed by idiocy, and help others who may be paralyzed find a path back to whatever fecundity of life it is that they deserve.
Koya Bound
A Book by Craig ModKoya-san — home to esoteric Buddhism — is the name of a sacred basin eight hundred meters high and surrounded by eight mountains. It is roughly one hundred kilometers of trails north from the Kumano Hongu Taisha shrine in Wakayama, Japan. Though the name of the basin is often incorrectly translated as Mt. Koya in English, Mt. Koya is only one of the eight peaks, and is remote from the central cluster of temples.
We walked towards Koya-san, but we did not touch Mt. Koya.
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.