Learning to walk through walls An Article by David R. MacIver drmaciver.substack.com I have a running joke that one of the most useful things I do when coaching or consulting is to say to people “Yes, that does sound like a problem. Have you tried solving it?” Part of why this is a joke is that actually most of the useful work happens prior to the point - the hard part is actually articulating what is going wrong well enough that it seems like a soluble problem - but there is genuinely something useful about this, because often it feels people are looking for permission. Without the external prompt, solving their problem is not something they noticed that they were allowed to do. A Burglar's Guide to the City problemsgames
Delight in the imperfect An Article by David R. MacIver drmaciver.substack.com I think part of the difficulty in allowing ourselves to properly delight in the imperfect, comes from conflating delighting in something with wanting it to happen. This isn’t the case. You can appreciate something as it exists while acknowledging its problems. You can see that a fire is beautiful without becoming a pyromaniac, and you can appreciate the absurdity of your political situation without thinking it’s good. Even if a delight in the imperfect causes you to want more imperfection in your life (and it should), there is no shortage of imperfection to seek out. The imperfect is not scarce, it’s abundant. If you find imperfection delightful, you will never be short of things that delight you, even if you fix any given problem. Solving problems and smoothing out imperfections doesn’t remove the source of delight, it merely opens up new vistas for it. You could give yourself over totally to delight in the imperfect and never run out of things to explore, even without creating your own. flawshumorproblems
We are surrounded by ghosts An Article by David R. MacIver notebook.drmaciver.com I'd like to call the more general phenomenon that this is a specific instance of "ghost knowledge": It is knowledge that is present somewhere in the epistemic community, and is perhaps readily accessible to some central member of that community, but it is not really written down anywhere and it's not clear how to access it. Roughly what makes something ghost knowledge is two things: It is readily discoverable if you have trusted access to expert members of the community. It is almost completely inaccessible if you are not. In this sense, most knowledge is ghost, particularly if you take an expansive view of what counts as an epistemic community. knowledge
Trust beyond reason An Article by David R. MacIver notebook.drmaciver.com In this sense, trust is a polarizing strategy, and it's one that is important to apply early on in the relationship before someone becomes important to you. If you trust someone excessively and it goes badly, but they don't matter to you, you can just kick them to the curb. In general, trusting someone at a level that seems slightly excessive for their level of importance to you will help you sort people in your life who you want to be more important to you than they are from those who you want to be less important than they are. And it does need to be excessive. It needs to be trust beyond reason. Not beyond all reason, but somewhat beyond what currently seems reasonable. If it is not, then unless they are prepared to take the first move, you will never find the signs you need to move to a higher level of mutual trust. Sometimes this will go badly, but you need to be able to try bad things. trustlovefriendship
The fastest way to learn something is to do something An Article by David R. MacIver notebook.drmaciver.com Suppose you have a problem to solve. What do you do? Well, you sit down and think real hard, and after extensive and careful planning you try the well thought out and rigorous solution that you have thought up. Right? No, wrong! Bad. The correct thing to do when you have a problem is: Think for a short amount of time. Make sure it is safe to try things. Try something you think will work. Observe the result. If you succeeded, yay you solved the problem! If it didn't work, think about what that means for the nature of the problem and try again. The Feynman Algorithm problemsprototypesfeedback
Coevolution and the bad take machine An Article by David R. MacIver notebook.drmaciver.com So when you have a bad take machine, you get the following processes: They make a bad take. People are outraged and talk about it. The bad take machine likes it and does more of that behaviour in future. If, on the other hand, they make a take and nobody cares, they do not get reward and the behaviour is selected against. The behaviours drove the spread of the outrage replicator, and the outrage replicator provides the selection mechanism for the behaviours. Thus, via the spread of our outrage on Twitter, we have operant conditioned the bad take machine into producing worse takes. Which is to say, it's bad on purpose to make you replicate it. How to write a high-engagement tweetA bad tweet is like a deepfake of an idea mediaanger
Notes on the Legibility War An Article by David R. MacIver notebook.drmaciver.com The basic idea of legibility is that the act of making something comprehensible enough to control is itself an act that shapes the thing to be controlled, often with far greater consequences than the control itself. This is because it removes complexity that is deemed as irrelevant that makes it harder to control, and that complexity may be in some way essential to the health of the system. controlsystemscomplexitylegibility
Things you didn't know you can be bad at An Article by David R. MacIver notebook.drmaciver.com I 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. Idiolect skilllearningpractice
Brilliant Hardware in the Valley of the Software Slump An Article by Craig Mod craigmod.com It begins with craftPenn StationEdgesThe business case for craft
It begins with craft Something strange is happening in the world of software: It’s slowly getting worse. Not all software, but a lot of it. It’s becoming more sluggish, less responsive, and subtly less reliable than it was a few years ago. In some ways this is hyperbole. Objectively, we’ve never been able to do so much, so easily with our smartphones and laptops and tablets. We’ve never pushed more data between more places more readily. But while the insidious “worseness” I mention falls only in part on the engineering side of things, it falls harder on the more subjective, craft side of things, making it all the more worrisome. Why should we care about this? Because the majority of our waking hours take place within the confines of applications. A truth recently amplified by the covid pandemic. And I believe software used by millions (if not billions) has a moral duty to elevate the emotional and intellectual qualities of its users. That elevation begins with craft. Apps Getting Worse performancecraftsoftware
Penn Station In the same way that physical architecture can affect a mind, so too can software. Slower, less reliable software is like Penn Station: Sure, you can catch a transfer from one train to another but the dreary lowness of the place, the lack of sunlight or sensible wayfinding will make you feel like a rat, truculent and worthless, and worse: You’ll acclimate to that feeling and accept it as a norm. softwaretransportation
Edges Hardware has literal and metaphorical edges — it must be fully complete and largely bug free to ship. Software? It’s far more amorphous, like mist. Patches can be endlessly pushed. It never ends. Faulty hardware can destroy a company. Faulty software can be patched. The butterfly keyboard debacle may never be lived down. Even as I type on this improved Magic Keyboard, I can’t help but wonder: Did they really test this thing? I had three butterfly keyboards die on me, twice in the field. Not fun. Hardware failures live long in the mind.
The business case for craft macOS software that adheres to craft — Things or Carbon Copy Cloner or BBEdit or Sublime Text (which, despite not being “native native” feels so solid and so responsive you’re willing to overlook its quirks) or Bear or Alfred or iA Writer or Keynote (arguably one of the best pieces of macOS software of all time) or anything by Panic, heck, even Terminal or Quicken (which, against all rational expectations is just a joy to use)5 — exists in troves, the existence of such proves to the Slacks or Twitters or Adobes of the world that it’s not impossible nor rare to produce craft-oriented software in service to user fluency, and still make a profit. In fact, there’s a business case to be made for being craft- and fluency-focused. We’ve seen entire companies with business models that could be summarized as “Bloat-Free X” emerge in recent years. Affinity is bloat-free Adobe. Install Adobe Creative Cloud on your laptop and marvel at the no fewer than a dozen processes whirling around in the background for unknown purposes. It’s no surprise Affinity Photo and Publisher and Designer have taken off. Sketch’s main feature for many years was simply: Not Adobe. And the web! When you care — when you really give a shit — the web is awe inspiring. I still can’t believe Figma is web-native (also born from the Not Adobe camp). That an application can feel so powerful, so fast, so well-crafted and be fully web-based should be a kind of lighthouse-archetype for all other sites lost in a sea of complexity and muck and unnecessary frameworks. More profitable and a better buy craftbusinesswww