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