<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alex Feinman on Medium]]></title>
        <description><![CDATA[Stories by Alex Feinman on Medium]]></description>
        <link>https://medium.com/@afeinman?source=rss-8528f44ad3b0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*oXITIKA2tmI7T9kO.jpeg</url>
            <title>Stories by Alex Feinman on Medium</title>
            <link>https://medium.com/@afeinman?source=rss-8528f44ad3b0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:12:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@afeinman/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[On Losing]]></title>
            <link>https://afeinman.medium.com/on-losing-fa7667f1cae2?source=rss-8528f44ad3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa7667f1cae2</guid>
            <dc:creator><![CDATA[Alex Feinman]]></dc:creator>
            <pubDate>Wed, 15 Oct 2025 12:54:53 GMT</pubDate>
            <atom:updated>2025-10-15T12:57:51.992Z</atom:updated>
            <content:encoded><![CDATA[<p>Tactics for the modern age, Part 2</p><p><em>(originally published December, 2016)</em></p><p>You may also be interested in <a href="https://afeinman.medium.com/tactics-for-nerds-dc735ff6e68a">part one</a> of this loose three-part series.</p><h4>Drowning</h4><p>You know that <a href="http://www.slate.com/articles/health_and_science/family/2013/06/rescuing_drowning_children_how_to_know_when_someone_is_in_trouble_in_the.html">article on drowning</a> that went around a while back? It makes a crucial point: drowning doesn’t look like what we’re taught. In a movie, people splash around and shout and go under, and there are lots of bubbles. In real life, people panic and freeze up and slowly bob up and down, unable to get a full breath, and drown slowly and silently. It’s horrific, and once you’ve been taught to spot it, you will.</p><p>Losing is sometimes like that. Losing is silence. And silence is death.</p><p>We’re in an age of unparalled censorship. We rely on distribution means that can programmatically remove your ability to speak, to be seen at all. A minor flip of a bit in an algorithm, and your ability to post, to, say, FB can be removed. The bit-flipping level hasn’t quite been reached for “internet as a whole”, but we’re not far off. Nations out there censor every bit of internet in and out of their countries, and hire armies of monitors to catch what the algorithms miss. What’s the result?</p><p>Silence.</p><p>What about abductions? Uncommon, but often portrayed in movies. What does it look like in movies? Angry men grab the child, the mother yells after them, maybe gets hit if she tried to interfere, the men jump into a van, vanish. In the real world? You turn around. The kid is gone. No one saw anything. You never see the person again. No one ever sees them again. This happened for <a href="https://en.wikipedia.org/wiki/Forced_disappearance#Chile">two decades in Chile</a>, just for example. People evaporating.</p><p>Silence.</p><h4><strong>Feedback</strong></h4><p>There’s this anti-pattern that exists in computer science: only speak up in an error occurs. It reached most of us through Unix, and from the TTY, the teletypes that printed each character slowly and laboriously. Output was precious — don’t waste it on success messages! Instead, only speak up when there’s an error.</p><p>I fight with folks at work about this constantly.</p><p>“Silence on success” is an outdated concept. Let users know the thing worked. If you’ve played any video game, basically ever, the interface has some feedback to let you know that the thing worked. A ding, a bell, a status change in your health indicator, a corpse that cries out and falls down, a glowing green aura around your newly-energized self, whatever.</p><p>We’re primed for it nowadays!</p><p>Except in social interaction. In social media, silence still means “nothing doing”: nothing new to report, nothing you feel like contributing. Which is great; folks shouldn’t feel *compelled* to produce content, to check in constantly.</p><p>Except.</p><p>We’re in a situation, now, where people may start going silent. Willingly, or unwillingly. And it’s not going to happen in a big splash with a lot of bubbles, at least, sometimes, not. It’s going to happen like real drowning; some bobbing up, some vanishing, with the person who is drowning unable to be the one to speak up — because they’re going to be caught in machinery that wants to silence them.</p><p>I don’t have a solution for this. I think step one is for us to be more connected, not less. Check in more. I shy away from this, because social networks are easy to use against you, but I think it’s worth it. The roadmap of our social connections is already laid out bare for anyone to exploit. A decade ago I was watching presentations about how social network analysis was being used to bring down bin Laden. Slowly, as it turned out. But the presenters, and it was one of the three-letter agencies, had it all mapped out, just from human intel. Nowadays, it can be done automatically. I worry for well-connected nodes, because that was the strategy then, and it’s the strategy now: attack the hubs.</p><p>So we need more hubs, and more communication. This is hard on the introverts. Not sure how to ameliorate that.</p><p>But dammit. Keep talking.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa7667f1cae2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Invisible Competence]]></title>
            <link>https://afeinman.medium.com/invisible-competence-06e49c34f1fd?source=rss-8528f44ad3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/06e49c34f1fd</guid>
            <dc:creator><![CDATA[Alex Feinman]]></dc:creator>
            <pubDate>Thu, 03 Jul 2025 15:29:03 GMT</pubDate>
            <atom:updated>2025-07-03T15:29:38.764Z</atom:updated>
            <content:encoded><![CDATA[<p>Invisible Competence — or, why success looks like failure until the end,<br> and why most people can’t plaster a wall (but think they can).</p><p><em>I originally posted this essay in another context in May 2010. It engendered a great conversation about competence, so I edited it for reposting in 2011. The explosion of conversation about LLMs / “AI” has made it relevant again in 2025.</em></p><p>I was watching “This Old House” some years ago–some plasterers were coming in to finish up a new room. They slid some mud on their trowels, pressed it up against the wall, and skimmed the plaster on there. Easy peasey, like painting with a roller. In my usual arrogant way, I thought, “Gosh, I can do that. Perhaps I’ll plaster up the big gap in the basement, and bill the landlord.”</p><p>But then I remembered back to a bad experience I had trying to plaster a ceiling with my dad, perhaps 20 years ago, and did another assessment of how hard it is to plaster. It’s hard. The danger is that it <em>looks</em> easy.</p><p>There are two effects at work here which you may be familiar with. The first one is obvious; the second, less so.</p><p>First is the <a href="http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect">Dunning-Kruger</a> effect; it states that people who aren’t skilled at something have a hard time estimating their own skill at something. People who are bad at something paradoxically claim to be very good at it, whereas people who have more knowledge can see their own short-comings. There was an IgNobel awarded here, so I’ll assume you’re passing familiar.</p><p>A related effect is that <a href="http://headrush.typepad.com/creating_passionate_users/2005/12/the_hires_user_.html">Learning Increases Resolution.</a> Knowledge about a thing enriches experiences of that thing. Though the inexperienced can definitely have strong and complex emotional reactions to a design or a craft, they may not be able to articulate why, nor even recognize the elements that made them react. In fact there’s a drive in the other direction–to leave the engagement inexplicable, to resist understanding that it’s the symmetry in faces that makes them beautiful, or that using a very specific ratio of height to width (known by every snail) makes buildings have a particular aesthetic.</p><p>When it comes to skilled behavior, these things collide. Generally, skilled work produces something which is easier to appreciate than it is to create. Because a superficial or moderate appreciation of the endeavor is accessible to even unskilled observers, it is a common mistake to think that the creation is also accessible.</p><p>To put it bluntly, most of the time when you look at something pleasing and it seems simple, your gut reaction of “oh, I can do that” is wrong. You can probably learn to do that; but unless you’re understanding the details of making it, you aren’t able to right now.</p><p>You don’t know how hard it is until you try.</p><p>And why is that?</p><p><strong>Seeing in High Rez </strong>[1]</p><p>One of the side-effects of skillful work is <strong>making the tricky parts look easy.</strong> Sure, we often say, “he made that look easy” for things we know are hard; but we forget it’s also true for things that really <em>do</em> look easy.</p><p>Plastering a wall is a good example. On its surface (ha), a plastered wall looks like the simplest thing: a flat, featureless plane. When I watched the This Old House plasterer, it seemed like all he did was put some goop on the trowel and run it along the wall, and–tada! Flat wall. The trowel’s flat, the wall’s flat, should be easy enough to apply a flat layer of plaster between two flat things, right?</p><p>And then you try it, and the plaster falls off the hawk onto your carpet, the trowel stutters and sticks where you press it, you end up with one crumbly edge and one goopy edge. And even when you manage to get the plaster to stick to the wall, it comes out wavy, with trowel marks all over, and looks awful. Then, the next day, it’s got sag marks and cracks all through it, and you have to start over. What happened?</p><p>Well, what happened was the hard part. And you missed it, because you were looking without comprehension. You were seeing it in low res.</p><p><strong>Let’s Go To The Instant Replay</strong></p><p>So you watch again. And armed with your own experience, you see that the plasterer actually spends a fair amount of time, a few seconds, loading up his hawk with plaster in a particular way. He spent a lot of time making sure it was the right consistency, and testing it beforehand. He holds his trowel just so, and lets his wrist float as the trowel hits the imperfect wall and imperfections in the mix.</p><p>He flattens the trowel against the wall in a gradual, steady fashion as the plaster leaves the trowel. He pushes it in against the wall in a particular scraping fashion. He moves his elbow and shoulder and body to smooth out the body’s natural tendency toward arcs instead of lines, and he works in a particular direction along the wall and around obstacles. He has a plan for undercoats and overcoats, and he knows exactly how thick to make each layer so it doesn’t crack as it dries.</p><p>All this richness, hiding in “put some goop on a flat metal thing, and run it along the wall”.</p><p>But the second time you watched — second if you’re lucky, as sometimes it takes many repeats — you knew where you had trouble. You paid more attention there, and you compared what you saw and felt with what was happening as you tried it. A good teacher will highlight these, helping the student learn, but you can also do it yourself. Eventually you learn to see in high-res.</p><p>But only if you’re willing to take an earnest look at your own work.</p><p><strong>But I’m Already Perfect!</strong></p><p>One thing that can prevent learning is overweening pride in one’s accomplishments. We all have a story in our heads, the story of who we are. If we’ve taken the time to try to plaster a wall, chances are our story includes elements like “I am handy” and “I get things done” and “I can be good (enough) at anything”. (There are people whose story includes things like “I suck at everything”, but that’s a topic for another essay. See also “<a href="http://en.wikipedia.org/wiki/I%27m_OK,_You%27re_OK">I’m OK, You’re OK</a>“.)</p><p>So, when you try, and you achieve some sort of partial success, there’s a strong temptation to call it full success. You may try to redefine what you did as a complete success, in a few ways. You can move the goal posts; that’s a common one. (“Those grapes were sour anyway.” “Well, with a wall as uneven as that, I’m just glad I got plaster on it.”)</p><p>You can claim it’s amazing, and fight anyone who doesn’t agree. You can explain how it’s a work-in-progress, with no real plan to ever redo it. And you can call a spade a spade, and be satisfied with owning what you created, even if you are not satisfied with how it came out.</p><p>Learning from your work–that’s the hardest part. It is a crucial lesson to learn for aspiring artists: the workpieces along the way, the imperfect mutant wobblies that didn’t come out the way you wanted, are part of the art. When you try and create something flawed, in addition to giving you opportunity to practice your craft, you learn about the places that are hard.</p><p><strong>Honest Appraisal</strong></p><p>The trick is to look at it honestly, celebrate its charm, understand its faults, and own it. Learn so that the next time around, you can pay more attention to how others do those parts and to how you did those parts, to what works there and what doesn’t. Learn from your failures–but even moreso, learn from your successes. What went right? Why? How can you do that again?</p><p>Then, some day, your art will look flawless, and while you’re sweating away, straining every nerve to keep it perfect, some sot will come along and say, “Gosh, you make that look so easy.”</p><p>And you’ll say, “look deeper.”</p><p>[1] Or, these days, “In full 4K!” Or, for the previous generation, “high fidelity stereo”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=06e49c34f1fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Housecat Theory of the 10x Engineer]]></title>
            <link>https://afeinman.medium.com/the-housecat-theory-of-the-10x-engineer-fe716789fc23?source=rss-8528f44ad3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe716789fc23</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Alex Feinman]]></dc:creator>
            <pubDate>Sun, 01 Jun 2025 21:22:21 GMT</pubDate>
            <atom:updated>2025-06-01T21:38:39.148Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KrPH4fRX7jSLvDhgvnMQlQ.png" /></figure><p>I recently re-encountered the myth of the “10x engineer”. Having <em>been </em>a 10x engineer, able to output more useful product than the other 10 people on a team, I have been convinced that such people exist, but — and this is the crucial part — only because most teams have someone who is currently contributing negative work, possibly several somebodies.</p><p>This might be a temporary thing — they’re learning the new thing, they messed up, they’re stressed from their pet frog croaking — or a permanent sign that they’re in the wrong career. Both happen, and both are signs that we’re human. Or worse — a reminder that we exist in an imperfect world, and that problems will always arise, and always need addressing.</p><p><strong>“Why do people who suck at it keep thinking they should get paid to make software products, and why do they also think AI can help?”</strong></p><p>There are a lot of careers where aptitude is easy to see. At least <em>formic</em> aptitude, where you can get the form right, rather than creative aptitude. Cooking; painting; building a fire. Incompetence, for whatever reason, is apparent rather quickly (or rather quickly afterwards, in some failure cases for cooking).</p><p>But most of human endeavor isn’t like that; it’s difficult to ascertain skill, and even more difficulty to quantify it.</p><p>We’re lied to by the lying lies of things like “IQ Tests” and “the SATs” (both designed to exclude black and brown people from the Ivy Leagues); and, more recently, by “Likes” and “5-star reviews” and all the other Sisyphean metrics gathered on our collective actions these days. And there is some value to social proof of quality; but only some, and it is a very noisy signal indeed.</p><p>(And, crucially, it’s almost impossible to tell a 3-star from a 5-star without significant exposure and training. This is why most review places these days have two ratings (“five stars, or we fail”).)</p><p>And then Dunning-Kruger rears its ugly head, and the people who are most sure of themselves for being able to judge a thing are the ones who most ought not to be doing that. And we end up here.</p><h4><strong>Building things wrong</strong></h4><p>In certain fields, like construction, architecture, programming, food preparation, and a host of others, everything has to go more or less right from start to finish. Otherwise you end up with the Leaning Tower of Pisa, or a cholera outbreak, or a wide swath of modern software.</p><p>In every career under capitalism, there is insufficient time for things to be done right, and so some things go wrong. I mean, things always go wrong, but there isn’t budget to fix some of the wrong things, and so sometimes we call them “assumed risks” (in the sense of “assuming a role”, not in the sense of “assuming an outcome”). Or “tech debt” or “acceptable losses” or “actuarial science”.</p><p>So every practitioner has to learn to deal with, well, negative output. However, and this is the annoying part, I keep encountering people who…can’t. If they were working in a busy kitchen, someone would elbow them out of the way, toss the now-flaming pasta in the metal bin, and start a new pot of water boiling. But there aren’t any flames, there’s just a pile of stench that looks like it wanted to be code or a design or a presentation or an email, and them standing there.</p><p>If I’m lucky, this poor chef is at the useful point where they can <em>see</em> better than they can <em>do</em>, and so they know something is wrong. I do wish they’d sing out that they never saw flammable pasta before and should it be doing that? but this rarely happens; instead, they stand there, horrified, as the bonfire gets larger.</p><blockquote>For more advice, including “Dying Loud”, which is what the above is about, see my series on <a href="https://medium.com/@afeinman/everything-i-know-about-business-i-learned-in-the-sca-part-3-5fb2ca2c8d6c">Lessons from the SCA</a></blockquote><p>But at least these folks know they shouldn’t <em>serve</em> the pasta flambée.</p><p>Because then there’s the other category, further into D-K, who gleefully submit…crap. Presentations no one can read, let alone comprehend. Architectures — if they think about architectures at all — built like an elephant on a teacup, lots of bloat at the top and lots of fragility at the bottom.</p><p>Code that…doesn’t. It might even look okay, though it usually smells a little off; there’s a reason the industry settled on “code smells” as a thing.</p><p>But when you try to build on it, you find that it’s burnt pasta underneath; or, sometimes, they just put the entire box of pasta, cardboard and all, into the pot and turn on the heat, and then serve it like that. You know, like people who <em>leave the AI prompts</em> <em>in their self-published novel.</em></p><p><strong>if (aboutToFail) then { don’t; } // It’s just that easy, right??</strong></p><p>These people. Their box of flaming pasta, and the six people who now need to stop working and fix their thing instead? That’s what makes me a 10x engineer, because I’m now being more productive than the entire rest of the team.</p><p>BECAUSE. And this is the crucial part, yes, I see that hand in the back, but it’s my essay.</p><p>Because the times when I’ve been 10x-ing, I’ve had the luxury of someone else doing the labor of recovering from all the Dumb going on around me.</p><p>And remember, we’re all Dumb, sometimes.</p><p>So really what the 10x nonsense is is that golden dream we all have, of the day when all the bytes lined up, when every test failed successfully on the first try, when the architecture you chose turned out to be the right one, of getting the syntax for an xargs command right on the very first try. (Some say it’s tar that confuses them, which confuses me, because who hasn’t memorized tar -xvfz foo.tgz?)</p><p>It is precisely the same fantasy that fuels Libertarianism; that they will be out doing the Real Work, the Important Stuff, like Science or something, while the little folk (usually women, and often — if <em>those </em>people are allowed in their fantasy — non-white) take care of all the unimportant stuff like nourishment, safety, cleaning up, bathing, etc.</p><p>The housecat theory, as someone aptly put it: convinced of their own superiority while wholly dependent on a system around them that they barely register as work. That&#39;s your 10x engineer.</p><p>Now, there is a LOT to be said about not hiring people who have a high percentage of Dumb days. But we all have some percentage. There&#39;s an ambient level of Dumb, and sometimes it comes to roost in your brain, whatever you imagine or wish. So that&#39;s really a false hope, the same one that thinks, &quot;if we just lock up all the lesbians, there will be no more gay people&quot; or some bullshit like that.</p><h4><strong>Everything&#39;s better with Libertarians, err, AI*!</strong></h4><p><em>(* with apologies to James Nicoll, but hey, dark alleys and language and all that)</em></p><p>So how do we get to AI?</p><p>Let&#39;s not always see the same hands.</p><p>Right, because AI is portrayed as that perfect slave, the employee who <em>never</em> messes up and always gives 110% even without a pizza party. And the people from Act 1, the ones who aren&#39;t trained to see quality, can&#39;t see it.</p><p>I&#39;ve said that current generative AI tech is like the mirror-test for humans. You know, where they put animals in front of a mirror and see if they recognize it’s themselves, or not. In genai, we see something that looks like &quot;us&quot;. And some people realize, oh, it&#39;s a twisted funhouse mirror of a million Redditors crying out at once. But other people think there&#39;s a mind there, and worse, try to convince us of that.</p><p>This is worse for peoople whose sense of other people is, shall we say, suspect. If you don&#39;t have a strong social theory of mind, then you&#39;re going to fail to detect when you&#39;re staring in a funhouse mirror, especially if it sounds a lot like how you think you sound (certain, competent, loquacious and &#39;well-spoken&#39;. God, I hate how smarmy most genai sounds these days.).</p><p>And then you add in a career where actual quality isn&#39;t easily perceptible.</p><p>AI output has, these days, good <em>formic</em> quality: the sentences are valid English, the facts look truthy, the citations sound very authoritative, the code has all its parentheses matching (if you&#39;re lucky). It&#39;s a miracle! Finally, the 10x engineer!</p><p>It&#39;s only when someone expends the 10x energy (thank you, Brandolini) to refute the bullshit that it becomes apparent that, as recently happened, the &quot;solution&quot; facilely proposed to a messy work directory was <em>not </em>to delete every file on the file system. (&quot;Hey [some AI], how do I tidy up my work<br>folders? I want them sorted by author and date.&quot; &quot;Run this command exactly as typed: &#39;rm -fr ~/*.&#39;&quot; How I wish I was making this up.)</p><p>And, of course, all the work to refute that bullshit is seen as without value. Who pays attention to the cleaning staff? I just keep pooping in this magic litter box and it keeps being clean!</p><h4>I like to end on an &quot;enh&quot; moment.</h4><p>So there you have it. The myth of the 10x engineer is the myth of the unencumbered hero, diving in at the last minute to tap a photon torpedo into an exhaust shaft and get a big award. Pay no attention to the thousands, if not hundreds of thousands, of people whose work went into that. And that heroic myth is embodied in the person that AI-hawkers are trying to pretend it is. And boy am I tired of it.</p><p>Go be awesome sometimes, and non-awesome some times, and human through all of it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe716789fc23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Being A Better Man]]></title>
            <link>https://afeinman.medium.com/on-being-a-better-man-d3a5044d67fe?source=rss-8528f44ad3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3a5044d67fe</guid>
            <dc:creator><![CDATA[Alex Feinman]]></dc:creator>
            <pubDate>Fri, 28 Mar 2025 14:25:50 GMT</pubDate>
            <atom:updated>2025-03-28T14:27:15.798Z</atom:updated>
            <content:encoded><![CDATA[<p>How is being a “good man” different than being a “good person”? The answer lies not in the destination, but in the starting point. Men — <em>boys </em>— are taught a specific way of being, and in doing so, are put at a great disadvantage when they try to become good people.</p><p>I realized this as part of aproject I’ve been working on for at least 15 years : being <em>personally</em> a better man, which is to say, adult male, despite being raised in and living in a society that rewards men for being abusive, temperamental boys.</p><p>It got a lot more awful in the past decade, for an awful lot of folks. The message are coming clear and hard from the top of the political food chain. It sucks, especially for people who are in my boat — survivors of abusive behavior that came from people that sound an awful lot like our current leaders.</p><p>So how do we adjust?</p><h4><strong>Listening</strong></h4><p>Listening is the primary skill that boys are taught not to do. Listening is weak. Listening is letting the other person exist. All of that crap is punished. Interject as early as possible. Ram your opinion over the others — shout it louder and longer, and it’ll go your way.</p><p>So of course I’ve been doing a lot of listening.</p><p>The thing about listening is, people can’t see you do it. I mean — the person you’re listening *to* can see it (especially if you practice active listening, where you act to prove your understanding of what they’ve said). But third parties don’t see it if they’re not looking for it, or if they’re not trained to notice it.</p><p>(This is one of the reasons I originally liked Twitter, specifically, the “retweet” functionality that emerged organically and eventually got turned into a feature. Retweets let you take something someone else said, and put it in front of your readers, <strong>attributed to the other person</strong>. That last bit is key — you are saying “This thought is important enough that you should hear it, too.” It’s the active form of listening, in a way that doesn’t fuck it up like stealing a quote or mangling someone’s meaning.</p><p>Naturally, RTs became a weapon for attack, people conflated RTs as support or not support rather than signal amplification, everything on Twitter is horrible, etc. But the idea was a good one.)</p><h4><strong>Patriarchy</strong></h4><p>Some time back, I read <a href="https://womboflight.com/article-169257">an article</a> by Bethany Webster, on the “Mother Wound” both causing and being caused by the patriarchy. It is a way of raising boys that <strong>reinforces</strong> the grown-baby-man as the desired outcome.</p><blockquote>“On a personal level, the Mother Wound is an internalized set of limiting beliefs and patterns originating from the relationship with one’s mother. The Mother Wound exists on a spectrum, with healthy, supportive mother/child relationships on one end and abusive traumatic mother/child relationships on the other end.</blockquote><blockquote>“Many complex factors go into how one’s Mother Wound manifests and where one falls on that spectrum. For men, it comes down to the specific dynamics that played out between a boy and his mother, as well as how the father supported or thwarted that primary connection. Because patriarchy — the principle of domination — can be embodied by either a man or a woman, the mother or father may have played the role of patriarchal parent in a boy’s life.” — Bethany Webster</blockquote><p>I’d go so far as to say both parents, as well as outside forces, serve as patriarchal parent. If the actual parents refuse, the government parent (in the form of school) fills the role. If a child is lucky enough to have neither parents nor school fulfill this role, they’ll learn it the hard way from age-peers and work environments.</p><blockquote>“…men are caught between a natural desire for their full humanity (the ability to be emotional, vulnerable and empathic) and their desire to remain privileged and in dominator mode.” — ibid</blockquote><p>Specifically, because they are taught that all other modes are bad; and because privilege is pretty damn good to have.</p><p>The author also quotes bell hooks, who as always is devastatingly accurate and insightful in a way that makes me wish it was taught in middle school:</p><blockquote>“Patriarchy demands of men that they become and remain emotional cripples. Since it is a system that denies men full access to their freedom of will, it is difficult for any man of any class to rebel against patriarchy, to be disloyal to the patriarchal parent, be that parent female or male.” — bell hooks</blockquote><p>(Man, I need to read more bell hooks basically every day.)</p><h4><strong>Bash ‘em!</strong></h4><p>The Patriarchy is power-based; we know this. What is less obvious, to both men and women I’ve talked with about this, is that men are beaten into submission, beaten into a place in this hierarchy: taught to both be victim and perpetrator. *Required* to be both.</p><p>Someone on LJ, I forget who, made a crack about the military being “a place for secret dom/sub fetishists to be ordered what to do and order other people what to do”, and there was a certain truth to it, but it’s also a way that almost all men I’ve met are taught.</p><p>Don’t want to be bullied? The solution isn’t to resolve the conflict; the solution is to punch the bully in the nose. Now you’re the bully! You won! (This was literally the only advice on bullies I received growing up. It came from many sources, both inside and outside the family.)</p><p>Don’t like what someone’s doing? Get them in trouble!</p><p>Don’t like what a country is doing? Bomb the snot out of them!</p><p>In no cases, listen. In no cases, accommodate, seek to find root causes, change the environment, build community, find double wins, or any of those other things that are available.</p><p>The article linked to above avers that men are in this way traumatized — habituated to a particular way of being, and taught not only that acting any other way is Bad, but Impossible.</p><h4><strong>Change and the transition to manhood</strong></h4><p>Some years ago I asked for recommendations on how to be, at that time, a 35-year-old man. I got some good suggestions; one that stuck with me was King, Warrior, Magician, Lover (hereafter KWML), a somewhat woo-woo book with a really good dose of important stuff at its core.</p><p>KWML asserts that there are four general archetypical pieces of a man’s personality, and that most men enter adulthood with one or more of these pieces in an immature state. It goes through the immature states for each (which generally fall into the “too little” or “too much” categories, with those two situations paradoxically right next to each other). And then talks about what a mature version of that looks like.</p><p>This was….really helpful for me. Descriptions of other ways of being. Reasons to question the way I was taught to be. But mostly, the hope that there <strong>is</strong> another way to exist, that other men have gotten there, and that I might, too.</p><p>KWML also asserts that men are robbed of an important piece of growing up: the ritual, well-supported of transition to manhood. In the book, they explain the importance of those mentors and peers who help move the boy to be a man.</p><p>The <em>mentors</em>, crucially, are the ones who have come out the other side. And the second crucial part is the <em>peers</em>: other people who are struggling, too, to undo the damage, and agree that the striving is worth it.</p><p>I’m also reading <em>Adult Children of Immature Parents</em>, on a recommendation from a close friend, and it raises the same point: men who are seeking to undo the damage inflicted on them by immature parents and a patriarchical society need the company of both camps.</p><h4><strong>Sword from the Stone</strong></h4><p>In today’s society, the mentors are twisted, sick perversions of boyhood grown to adult size; and the peers are taught to make fun of each other for trying to grow out of the bad behavior.</p><p>This leaves the well-meaning individual quite alone; and usually we’re not even lucky enough to have a magician take us under his wing before he’s killed off in the first act of the movie.</p><p>This thought fascinated me so much I wrote a book about it (<em>Mr. Maybe and Dr. Don’t</em>, still unpublished). Most book-heroes, and certainly all the sword-based heroes (Arthur, Luke Skywalker, Richard Cypher, etc.) are also missing a mentored transition to man-hood. They often get a kick in the ass from the Elder (Obi-wan, Merlin, etc.), but then they get their father’s penis/sword handed to them, summarily, and they somehow become an adult.</p><p>This resonates with a lot of men because, well, that’s what happened to us. We got thrust into a place we weren’t prepared for, and everyone around us acted as if we were a hero (because patriarchy), and after a while we started to believe it, too.</p><p>(Yes, I use the word thrust there, because that’s what the narrative is.)</p><p>And for many of us, it never felt right; something was missing.</p><h4><strong>Last of the Jedi, Iron Man 3, Dr. Strange</strong></h4><p>People HATED Star Wars’ take on this, i.e., Luke’s journey in The Last Jedi. I think this is why TLJ was impactful for so many men, positively or negatively whether or not it reached the level of cognition. It shows what happens to that incomplete man-child after the big award ceremony, after the medals, when they’re <em>still</em> a 20 year old farmboy from a backworld desert, but now they have a magic sword and responsibility and the fate of the entire world on their shoulders, with emotionally stunted allies all around and a sister who comes from such a different world they may as well be strangers.</p><p>Luke crumbles, has a big-ass screw-up, and rage-quits the world.</p><p>This is a really common pattern for men. The things we used to get rewarded for don’t work any more, and no one’s taught us what actually works — rather, they’ve been rewarded for doing things that take a hundred people to get them to that point, and another hundred to patch up the mess they leave behind afterward. (viz: Rogue One, where we learn about the literally hundreds of people who gave their lives so Luke could shove a missile in a hole. See also the story _The Light Of Others_, hosted elsewhere.)</p><p>But in TLJ, Luke *has* grown — eventually. It takes a doggedly determined woman and patient Wookie to break him out of his funk, but in the end, he finds a way to act that is consonant with both the ideals he ascribes to and the demands of the situation. The effort, however, kills him: such a person cannot persist as a man, even in the fictional world of Star Wars. Such people can only be ghosts, like Yoda and Obi-wan; our culture simply doesn’t permit a living male hero who is not an abuser of others.</p><p>That might be a bit dark. But it also might be a bit true.</p><p><strong>Iron Man</strong> is a different, interesting arc. In the movies Tony starts the typical American hero — brash, self-assured, possessed of secret knowledge and power that makes him, quantifiably, in every way, better than you. And it kicks all that out from under him, because unlike our leaders, Tony has a conscience, and a heart. He literally works on his heart for the whole movie, replacing it with a heart of his own invention; he drags the woman in his life through hell to help him replace it.</p><p>(In retrospect, the symbolism is heavy-handed, but I bet 99% of the audience missed it.)</p><p>But Tony can’t sustain it. Cracks show in IM2 and Avengers, and by Iron Man 3 he breaks completely: he shatters, into a mental invalid. It’s not a rage-quit: he’s running for his life, beset by panic attacks and crippling self-doubt.</p><p>(Superhero movies are useful because the symbolism is so obvious: Tony literally crashes and burns in his dead-weight suit, the armor of self that he puts on to pretend to be a grown-up.)</p><p>This, too, is another typical pattern for adult American men. (And may be for other cultures; I only write what I know.) “Taking time off for family” and all its related excuses; disappearing into a drunken haze; suicide. These are all versions of this. We’re seeing a LOT of this pattern right now, because men are taught it’s an acceptable way to escape from the challenge of growing up.</p><p>The third example is <strong>Dr. Stephen Strange</strong> (“Oh, we’re using our made-up names?”). In the comics, I always saw Strange as the epitome of mature adult — it often seemed to me that other heroes, necessarily immature due to the type of archetype they were, came to him and got really decent advice about how to act grown up. In his solo movie, it felt like they wanted to get there, and failed: they started with the same brash asshole as Tony Stark, and then he takes his licks.</p><p>But instead of him being properly humbled, and learning a different way to be, Strange finds a way to not only stay the same asshole on the inside but also get his hands back. (Hands are not swords, but a sword is wielded with your hands; it’s a similar symbol of virility.)</p><p>I felt like this was a failure of story-telling, but perhaps it’s just that the writers wanted to end up with a different Strange than the one in my head. (It’s possible their version is closer to the comics; I haven’t read them in decades.) But it was just a — a missed opportunity. The Marvel cinematic universe only has one mature leading man — Steve Rogers — and he’s a caricature of a particular kind of maturity, and stunted in other ways. (For one, he’s really bad about including anyone else in his martyrdom. He’s willing to lead, but not to *be* with people.) Okay, that’s a bit unfair to King T’Challa, who may also be on the path to maturity. Also: there are a bunch of secondary men who are vastly more mature in this regard. Wong springs to mind.</p><p>In the last of the Avengers movies (i.e., Infinity Gauntlet part 2), I felt like Strange was moving more in the direction of wisdom, but still not there; he ends up self-sacrificing, choosing to trust in his own private judgement of what is best rather than forging an alliance that all agrees. He gets caught up in the petty squabbles, and a little of the “old” Stephen pops out.</p><h4><strong>Quando omnis flunkus moritati</strong></h4><p>Ironically, some of the best advice on being a man came to me from the Red Green Show, a show about men misbehaving in particularly man-ish ways, but in a supportive environment that recognizes what they’re doing, and gently pokes fun at it, in a way that makes it clear it’s not the only way to be.</p><p>The above pseudo-Latin motto of their fictional Possum Lodge (“When all else fails, play dead”) is effectively the Stark solution in IM3 — run away, hide, pretend it’s not your fault. But the conjoining phrase for the Lodge, the convocation to assembly, is the Man’s Prayer:</p><blockquote>“I’m a man<br>But I can change<br>If I have to<br>I guess.”</blockquote><p>This is such a pithy encapsulation of the journey that it’s almost hard to laugh at these days. Because that’s just it: there are an awful lot of men who understand they need to change — want to change — if they have to — they guess — but are blocked on next steps, on finding others who wish to strive in the same way they do, and who reject the dark side, the easy “victories” of abuse or retreat or self-blame.</p><p>The other resonant tag-lines are their sendoffs. Episodes end with an admonition to “Keep your stick on the ice,” a male-coded version of “stay prepared”, but one that envisions a passively-engaged participant — quite the opposite of the always-shoving-forward ‘man’ of the patriarchy.</p><p>And the other one is in Red’s “Midlife Musings” recurring segment. It ends with the large, friendly letters on the cover slogan of: “Remember — I’m pulling for you. We’re all in this together.” Because in those segments, he *is* acting as that adult mentor, even if his advice is often of the Fractured Fairytale variety.</p><h4><strong>Finding peers, finding mentors</strong></h4><p>So I think my next step is finding patient peers and mentors, and connecting them with those in need. This has to come from a restricted set: people who were raised as male in a society similar to my own. There’s too much to explain to almost anyone else; while writers like bell hooks, above, have a very clear idea of the situation, it feels like being talked <em>a</em>t, whereas folks need to talk <em>with</em> people who are on the same journey.</p><p>Some of y’all are folks who I respect in this way, so that might be one place to start. Some work folks might be, too; I’ve pinged a few people about this.</p><p>Because this stuff takes time, it’s hard, and it threatens the self. And you don’t want to end up like Luke, or Tony, or even Stephen, with the lessons glancing off or causing self-destructive (or other-destructive) behavior.</p><p>So, that’s my life’s work sorted for the foreseeable future. Hope you enjoyed reading this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3a5044d67fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tropes I Won’t Write]]></title>
            <link>https://afeinman.medium.com/tropes-i-wont-write-476d418aeac8?source=rss-8528f44ad3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/476d418aeac8</guid>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Alex Feinman]]></dc:creator>
            <pubDate>Fri, 19 May 2023 23:07:23 GMT</pubDate>
            <atom:updated>2023-05-19T23:07:23.093Z</atom:updated>
            <content:encoded><![CDATA[<p>(All tropes available for review on TVTropes.org; warning for existential-level time sink threat.)</p><ol><li>Crowning Moment of Awesome. Screw that noise. I’m like 90% sure this is rooted in a deep insecurity on the part of authors, being afraid of achieving something.</li><li>Fridged women. Ditto. Find real motivations for your heroes.</li><li>Rape as “spice”. GRrrrr. (I cannot 100% rule out rape happening in my books, because like murder it’s still something that needs to be written about and thought about, but never in a trivial fashion.)</li><li>The joke is, they’re gay!</li><li>The joke is, they’re nerds!</li><li>The joke is, they’re ____!</li><li>Ye moldy Noble Savage, and its modern relatives Magical Negro and Magical Native American. Hopefully these are self-explanatory.</li><li>Causality loops, except when they are the plot. (Non-causal-breaking time travel, however, will definitely happen.) I also detest Stable Time Loops, because of the creeping inevitability problem. (“Well, I guess we’ll just *choose* to do precisely the thing that makes this puzzle interlock!”)</li><li>Single-biome planets, and its relatives Injun Country, Eskimo Land, Planet of Hats, etc., etc. (Except as intentionally-created or curated places, like Rabbit Island in the sea of Japan…)</li><li>The dual of racist environments, veiled racism as: Fantastic Racism, Space Jews, etc.</li></ol><p>Call me on it if you see me doing a one of these. Sometimes the cultural programming we’re all subject to infects what I end up writing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=476d418aeac8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I am still a human]]></title>
            <link>https://afeinman.medium.com/i-am-still-a-human-71c145544009?source=rss-8528f44ad3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/71c145544009</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[generative-art]]></category>
            <dc:creator><![CDATA[Alex Feinman]]></dc:creator>
            <pubDate>Sat, 18 Mar 2023 11:43:23 GMT</pubDate>
            <atom:updated>2023-03-18T11:43:23.184Z</atom:updated>
            <content:encoded><![CDATA[<p>For many years I have used a tagline similar to the current one, which includes the stipulation: “All posts made with 100% recycled electrons, sustainably crafted by artisanal artisans.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GYZNq-VF67LjDnvdBsWdLQ@2x.jpeg" /></figure><p>It was meant to be a gentle jab at frou-frou food shops, of the type I often frequent when writing these posts.</p><p>But in these days of generative AI, which threatens to overwhelm our attention with content that *seems* interesting but is ultimately as contentful as the grinding noise from an aging microwave, it’s necessary to be specific.</p><p>The tools I use to write involve relatively “dumb” things like spell checkers and (when writing on a phone) predictive keyboards. I understand the allure of using generative text-slingers, and fully expect them to become normalized over the next decade.</p><p>But when you blindly use the regurgitated, reconstituted blur of whatever GPT and its brethren were trained on, the point of art is lost.</p><p>Art is communication and connection. This is because we are humans, and long for connection and communication, and we have refined our techniques for such over thousands of years.</p><p>So if generative techniques help folks connect and communicate — excellent. I will continue not to use them much, because I am stubborn, but also because I am most interested in the things that noone has thought before, the phrase someone just invented but turns out to be the thing we all knew needed a word, the insight that helps me connect with you all.</p><p>And we’re not there yet. Right now it’s all Madlibs pablum and regurgitated recombination of the cheapest data set the trainers could find. There’s no *there* there, to quote Gertrude Stein.</p><p>So yes. This is 100% hand-crafted. How about you? Are you human?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71c145544009" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fixing the coding part of interviews]]></title>
            <link>https://afeinman.medium.com/fixing-the-coding-part-of-interviews-4182e6f06aa?source=rss-8528f44ad3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/4182e6f06aa</guid>
            <category><![CDATA[interviewing]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Alex Feinman]]></dc:creator>
            <pubDate>Thu, 27 Jan 2022 11:47:52 GMT</pubDate>
            <atom:updated>2022-01-27T11:47:52.516Z</atom:updated>
            <content:encoded><![CDATA[<p>Coding interviews suck. They’re painful for everyone. But we need to assess technical ability, so we keep doing that.</p><p>What if there were a better way?</p><h3>How we got here</h3><p>If you’re a programmer, there’s a 99% chance you’ve been in this part of an interview:</p><blockquote>“Okay, so, you’ve got to program a remote control for a TV. Write out the code and talk me through the solution.”</blockquote><p>Then they open a blank tab in a text editor[1]. And…go!</p><p>This sucks. People panic. It’s hard to remember syntax or recall function names. It’s hard to map out a solution. The interviewer squirms because they KNOW the answer it’s so EASY why are you not getting it!? The interviewee feels like an idiot, or worse, wastes months memorizing the code for inverting a B-tree[2].</p><p>The worst part? It doesn’t actually assess how productive that person will be. It tells you nothing except how that person behaves in unreasonable situations.</p><h3>How we actually code</h3><p>That’s not how humans write code these days. Code is too complicated to write on a whiteboard. We have special-purpose software that enables us to write code faster, smarter, and more productively every day. I have four linters keeping me honest with every keystroke, and two machine-learning systems supplying me with code constructs, so I can focus on the part that needs actual human intervention.</p><p>It’s also not how teams produce code. If you go off and sit in a blank room and write a block of code and then pretend you’re done, you’re going to have a lot of trouble when you need to be a part of a team of more than one person. Software development includes division of labor, testing, usability input, data generation, version control, code and solution reviews, and a dozen other practices that ensure we ship quality products.</p><p>As someone who runs a lot of interviews, I wanted something different.</p><p>I wanted something that would tell me that this person would be a valuable addition to a programming team I was on. The qualities I look for in teammates include:</p><ul><li>knowledge and learning potential</li><li>adaptability to new situations, even if it takes a minute</li><li>working well with others, including critiquing and improving each others’ work</li><li>finding and explaining the root cause of problems</li><li>coming up with solutions for problems</li><li>explaining why something is or is not a good solution in context</li></ul><p>Of these, whiteboard coding covered <em>maybe</em> one and a half. No wonder it felt so wrong and artificial!</p><h3>The Solution: Other People’s Code</h3><p>My variant on <a href="https://lawsofux.com/jakobs-law/">Jakob’s Law</a> states “Programmers spend most of their time looking at code other than their own.”[3]</p><p>So let’s do that in the code interview.</p><p>My code interview consists of three parts:</p><ol><li>You are given a short block of code in your preferred language, and a series of tests for it.</li><li>Some of the tests are failing. There is also a note from the code’s author, who is on vacation this week, sorry.</li><li>I ask you to talk through the code and explain what you see, including why the tests are failing.</li><li>I ask you to talk through solutions for making the code behave correctly and the tests pass. This might be improvements to the code, fixing the tests, dusting off and nuking from orbit, whatever.</li></ol><p>This tells me a lot of things about the candidate:</p><ul><li>Can they understand the code? Can they explain it to me? Do they understand what parts are important and what parts are boilerplate? Do they make use of all available info (e.g.: code, comments, API documentation, etc., etc.)</li><li>Can they see the flaws? How quickly do they find them, and what methods do they use to find them?</li><li>Can they explain the behavior in human terms, and hypothesize what’s causing any problems?</li><li>Can they come up with plausible solutions, and explain to me why those solutions are appropriate?</li><li>Can they critique code in a way that will make the original coder comfortable enough to accept the input and improve the work?</li></ul><p>Usually by the end of this segment I have a <em>much</em> clearer idea of what kind of a team member the candidate will be.</p><p>It’s worked so far, and a nice bonus is that interviewees report less stress and more engagement afterwards.</p><h3>Summary</h3><p><strong>tl;dr: Interview using code reviews, not blank-board coding.</strong> It is more true to life, and tells you much more about how the candidate will perform in day-to-day work.</p><p>It also is much less likely to piss off senior devs who have had quite enough of coding game “guess what I’m thinking” interviews. For folks with more experience, I will choose one of the more complicated code samples to review, but even with a trivial example, you’ll learn a LOT.</p><p>So try it! And tell me how it goes!</p><p><em>NOTE: Opinions expressed here are my personal opinions, and not intended to represent the views of any current or past employer.</em></p><h4>Footnotes</h4><p>[1] Or, if you’re interviewing in the stone age, they hand you a whiteboard marker. Because that’s how I write all my code![4]</p><p>[2] I have been paid for programming for 30 years. I have never been asked to write such an algorithm, because it is already written in every language I use, and the right approach is to import the appropriate function from the b-tree package, not to reinvent it.</p><p>Also, yes, I know inverting a B-tree isn’t a thing. I put that in there just for you! Please don’t ask “gotcha” questions in your interviews, either.</p><p>[3] This is absolutely true in industry. The main places it isn’t true are (a) in college, where you’re asked to write a lot of code from scratch, and (b) for self-taught folks[5] who learned to code before the internet was much of a thing.</p><p>[4] I’m not knocking white boards. But I don’t write code on them. I write diagrams that explain code, and the people I’m doing it with also have the context I had.</p><p>[5] But even I had <a href="https://www.goodreads.com/book/show/1131564.Making_tracks_into_programming">some sample code</a> to learn from, and that was a long time ago.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4182e6f06aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Five Hearts]]></title>
            <link>https://afeinman.medium.com/the-five-hearts-c4754e8bdece?source=rss-8528f44ad3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4754e8bdece</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <dc:creator><![CDATA[Alex Feinman]]></dc:creator>
            <pubDate>Mon, 14 Jun 2021 15:51:04 GMT</pubDate>
            <atom:updated>2021-06-14T16:43:17.126Z</atom:updated>
            <content:encoded><![CDATA[<p>“No, Twitter, I didn’t want to shove that in all my friends’ faces, I just wanted to let the author know I liked it!”</p><p>“Wait, if I heart this, who sees that?”</p><p>“Hey, +Person? Hello? @Person? Can you see this?”</p><p>“Save for later. No, that’s public! Crap. Wait, I mean, send to bookmarks. No, wait, heart. No, um…”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*FeHeZSzggmbCG-un.gif" /><figcaption>You, possibly, when faced with the array of options below every damn post on social media.</figcaption></figure><h3>A superfluity of options</h3><p>As a designer, I know there are a number of things I want someone to do when they see a post. As a customer, there’s a different set, but they overlap.</p><p>The first set of things are atomic: you do them, and that’s it, there’s no other step:</p><ol><li><strong>Feedback:</strong> Nice job! (Send feedback to the author)</li><li><strong>Share:</strong> My friends should see this!</li><li><strong>Guide:</strong> I want to see more things like this.</li><li><strong>Bookmark:</strong> I want to read this / remember for later</li><li><strong>Weigh in:</strong> I agree with this; or see below.</li></ol><p>The problem is that five is a lot of controls. We’ve settled on three, usually; but we have a hard time remembering what <em>these three</em> do on <em>this</em> medium as opposed to another.</p><h4>We need to go…deeper</h4><p>Each of these atoms has some variation and detail, too, and sometimes the detail makes you use the tool a little differently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*mRARXke64yZQs6Ko3-qcTw.gif" /></figure><p>“Weigh in” is actually a number of things in combination:</p><ol><li>The spectrum [endorse … agree … disagree … consider harmful]: I have an opinion, which might include “this is awesome”, “this is problematic”, “this is hate speech”, “this is spam”, and everything between. Facebook canonized this a while ago with the reaction-faces, because “Like”ing someone’s funeral notice seemed a bit crude.</li><li><em>Directed</em> vs. <em>Broadcast</em> vs. <em>For the Admins</em>: I want the author to know my thoughts; or my friends; or everyone; or possibly I want to talk to the moderators. It’s rarer to give users control over this directly, though Twitter recently has started letting you pretend to talk to to the algorithm. (I have my suspicion it’s the Door Close button of the internet, however.)</li></ol><p>Each combination of these two is useful. Most systems let you select “broadcast endorsement” as an atomic option, or “flag for admins as spam/problematic”, but others are useful too. For example, I’d like a “flag as propaganda to my friends only” button on Facebook articles; it wouldn’t prevent them from seeing it, but it would add context for my less-skeptical friends.</p><h4>Support</h4><p>There’s a second set, which involve further communication:</p><ol><li><strong>Respond</strong>: I want to respond to the author directly.</li><li><strong>Quote</strong>: I want to comment on this where my friends can see.</li><li><strong>Follow</strong>: I want to further engage with the author, or with this stream of content.</li><li><strong>$$$</strong>: I want to support the author (financially, or other means)</li></ol><p>These are not mutually exclusive, though many platforms split them up. Twitter used to hide direct @-replies, leading to the “conference call” pattern of at-ing people. Quote-tweeting lets you add commentary to a tweet, as does resharing on Facebook. Most social networks let you follow a creator, but it’s often by identity (“follow <a href="https://medium.com/u/8528f44ad3b0">Alex Feinman</a>”) rather than by category (“follow social media”. Medium is unusual in that it does allow this in combination (“follow <a href="https://medium.com/u/8528f44ad3b0">Alex Feinman</a> when he posts things about social media”).</p><p>Patreon /etc. let you follow-and-$$$ people you like, including “give $$$ when Person posts a new thing”; this seems useful, and worth porting to new media. Medium lets you $$$ a particular post, if you’re a member, but ties it together with “guide” and “endorse”.</p><p>And this is just the tip of the iceberg. There are hundreds of useful combinations here.</p><h4>You’re confused because it’s confusing</h4><p>And so we’re left with the combination of a nicely complicated social world. Human society is complex, and rightly so, and so these attempts to simplify it to a handful of controls necessarily flatten out interesting wrinkles.</p><p>But perhaps this lexicon will help you think about what you’re really provided with, in the future, when you see that set of like/heart/clap/plus/follow controls.</p><p><em>This is the obligatory part where I remind you that this post is self-referential, and encourage you to use the Clap button many many times if you found this content useful. Because Claps are all of these: “nice job!” and “share with others” and “$$$” (for members, though I see no money from it personally), sent in a broadcast manner.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4754e8bdece" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Not to Ruin your Design Review]]></title>
            <link>https://afeinman.medium.com/how-not-to-ruin-your-design-review-bede0694a1ef?source=rss-8528f44ad3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/bede0694a1ef</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[presentations]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alex Feinman]]></dc:creator>
            <pubDate>Mon, 23 Nov 2020 11:21:59 GMT</pubDate>
            <atom:updated>2021-02-03T18:44:57.523Z</atom:updated>
            <content:encoded><![CDATA[<h4>You might be sabotaging the process from the get-go</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uY2ycDZbsOI2hO-ncr5B_A.png" /><figcaption>Take care of your valuables!</figcaption></figure><p>We’ve all been there. The Dev team has worked really hard to nail down a search results page they think will really help users. You pull up your slide deck and start walking the stakeholders through it.</p><p>“Okay, here’s what the user sees after they log in,” you say to the assembled throng. It’s good to start with the familiar, you’ve heard.</p><p>“Wait, that’s not the right time zone,” the VP of marketing points out.</p><p>“This is just fake data,” you say, hoping to get back on track quickly.</p><p>“Nobody has that many books on their shelf. Why are you showing so many books?”</p><p>“Lots of our users have really large shelves,” you stammer. “But we’re not reviewing the book shelf design right now.”</p><p>“I don’t like that font. Why is it so blocky?”</p><p>And on, and on.</p><p>What happened?</p><p><em>(A side note: I have committed EVERY ONE of these mistakes. And I hope you can learn from my errors!)</em></p><h3>Remember to Begin Before You Start</h3><p>Prep is everything in a meeting like this. If you don’t have time to prep, you don’t have time to have the meeting — you’re just wasting N peoples’ time.</p><p>Some specific prep things to think about:</p><h4>Don’t Just Throw Wireframes up there</h4><p>Set the scene. Even if “everybody” knows the situation, quickly summarize <strong>who</strong> the user is and what their <strong>goal</strong> is. This can be a single sentence! If you’ve got established personas, use those: “Ricky, our romance reader, is trying to find a new book to read by one of his favorite authors. Recall that Ricky uses the site weekly, and has hundreds of titles in their to-read pile.”</p><p>We’re all so busy. It’s impossible to prep people in meetings, you say. I had 6 design reviews today alone!</p><p>Well, that sucks. And it might <a href="https://afeinman.medium.com/worshippers-in-the-cult-of-busy-ef341d1e8e06">say something about your workplace</a>. But 3 super-productive design reviews, with a few minutes for audience prep ahead of time, and a solid half-hour afterwards, are better than 6 abbreviated ones. There’ll be less rework and deeper insights.</p><p>So budget your time appropriately, and help people understand context before they jump into your design review.</p><p>If you don’t build up context and give some user background, reviewers often simply overlay their own experience on whatever you’re presenting. You’ll get their knee-jerk reaction, or end up <a href="https://en.wiktionary.org/wiki/bikeshedding">bike-shedding</a>, instead of getting valuable design input.</p><h4>Trim What You Don’t Want To Talk About</h4><p>You cut and paste that thing from the old mockup, but it’s okay, people will just ignore it, right? Also, you show the drop-down menu both closed and open so the developers can see what it looks like; pile ’em all together in a heap!</p><p>Except — no. We’re all human, and design reviewers are already at a disadvantage, because they haven’t lived with the design while you’ve been working on it.</p><p>At best, they’re coming in largely blank — at worst, they have the old version, or a dozen old versions, floating around in their head fighting for dominance. So help those squishy human brains to focus on the relevant piece. Take the extra time to trim out things you don’t want to talk about.</p><p>If you’re exploring search that day, aggressively blur out the rest of the page. Or put a big gray X, labeled “USER’S SHELF”, over that section. A big gray box, with the right voice-over, is totally fine if you want your audience to focus elsewhere.</p><p>A big grey X, you say? That’ll ruin the aesthetic! Well, yes. And make it abundantly clear you are not talking about aesthetics right now. Make it <em>unmistakably</em> ugly, and as clearly labeled as the devices in the Bat Cave circa 1967. Bat-Login-Page. Bat-Bookshelf. Bat-not-what-we’re-reviewing-today.</p><h3>2. Craft Your Presentation</h3><p>Hey, look, it’s more work! This time, the work is crafting the content of the presentation to shine a light on the part you are discussing, and help people avoid being tripped up by inconsistencies, irrelevancies, or trivialities.</p><h4>Show Your Design How Users Will Use it</h4><p>It’s tempting to show every possible state. Developers often ask for it. And it saves time — just throw that extra state onto the same slide! But it’s harmful to getting feedback on the design. Instead, do a little extra work so you can get the best feedback from your reviewers.</p><p>Most of us are familiar with <strong>style sheets</strong>, and it’s tempting to do something like that with mockups. These have a different audience and purpose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OHap5So3UqF_JaGj" /><figcaption>An example of a style sheet for Google’s Material controls. This is not the sort of thing to include in your workflow review. (<a href="https://lh3.googleusercontent.com/xQK41sPgGmQNzcqCAgAiycOZQNh75Ono9cvtrFomKPBAi0CDuaqhn2jTn7Grbr3tMQMTmhMIzN8x0tqmSN4BT5j6Wwf9-e0W4qIbS2k=w1064-v0">source</a>)</figcaption></figure><p>Designers are often tempted to reuse the same format for both <em>design documents</em> (which are used to coordinate with developers) and <em>design presentations </em>(which are used to get high-level feedback from user proxies). While these can look similar, their constraints and goals are very different, and often in conflict.</p><p>For a design review, you’re attempting to elicit responses similar to what a user will have while using the design.</p><p>Note: there ARE many exceptions to this! For example, if you’re showing off search results that change depending on the type of result, it’s helpful to have a “style sheet” like the above during your presentation showing all 12 variants at once. There are just too many instances to make up a design case for each one. But first set the scene, and if possible, keep available the context for the style-sheet focus. In an ideal world, you could even switch between the items <em>in</em> context — think about a color picker that shows you the color used in a variety of situations, letting you see the contextualized result as you vary the color — but that’s a bit of a pain to set up.</p><h4>Use Realistic Content</h4><p>Content? We don’t need no steeenking content! Just stick <em>lorem ipsum </em>everywhere! Even in fields that generally have one small number.</p><p>Sure, yeah, just put “test test test” (or just “lorem”) in the text area which is going to show a page-long blog post. It can’t possibly affect the layout…</p><blockquote>There’s a famous study from the dawn of UX regarding cockpit design. The designers worked hard to establish a new layout of gauges based on best principles of human factors and the needs of pilots, then presented it to pilots to get their input.</blockquote><blockquote>The response from pilots? “That’s impossible! That could never happen!”</blockquote><blockquote>It turned out the gauges were eminently readable — but the data they were showing was conflicting nonsense. Since the entire goal of the interface was to understand those gauges, designers should have paid attention to sourcing high-quality data for them.</blockquote><p>This requires you to identify the <strong>key info</strong> in your interface. Can you gather real data, potentially anonymized? If you absolutely cannot, can you create data that is the same shape (word length, number of words, size of pictures, length of numbers)? It makes everything work so much better. There are a variety of code <a href="https://github.com/benkeen/generatedata">libraries</a> and <a href="https://www.seventhsanctum.com/index-name.php">websites</a> for generating “random but real-seeming” data — use ‘em!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9WEBhIQ3TYPJBg42RfEkFw.png" /><figcaption>Think how much better that presentation would be if all the people had Goblin names.</figcaption></figure><p>And yes, sometimes throw in the “hard” content. The person with the display name that is more than 32 characters long (I’m married to one). The exceedingly long load-time number. (“Your call is important to us. Your call will be answered in approximately 4294967295 seconds.” — well, okay, maybe that one calls for a rethink of the interface.) Translate the interface to German, if that’s a target market, because text labels tend to be longer in German. Whatever makes sense for <em>your</em> scenario.</p><h4>Avoid presenting in a format wildly different than your target</h4><p>Okay, I get it, you can’t hand out cell phones to everybody in the room and ask them to use the app. (I mean, you <em>can</em>, and sometimes that’s a great method, but this post is about design presentations.)</p><p>But you can set yourself up for success by approximating the target platform(s). Are you targeting desktop users with 24&quot; monitors? Then make your mockups in 48pt type, because that’s what slides require. Designing for mobile? Ditto!</p><p>But, you say, but! Designs that <em>work well </em>might not <em>present well</em>. It’s impossible for people viewing a slide deck over a crummy network connection to read all the details of an interface. And that’s a good point.</p><p>So it’s up to you, the presenter, to ameliorate this. One way is to give an overview and then zoom in on specific areas of interest, either with an inset image or by having successive slides focus on different areas. Another is to provide context some other way, for example, via printouts or a static document (PDF) shared, and then say “we’re looking at this section”. For smaller designs, as for a phone interface, avoid the temptation to blow the phone up to full-screen, and instead make it a size such that design elements have proper importance.</p><h3>3. Transition To Action</h3><p>The end of your presentation is likewise key. You can have done everything right, and have it fall apart here.</p><h4>Be clear about desired feedback</h4><p>There’s some sort of taboo against asking for what you want. But it’s crucial to help focus: the same way you craft your presentation to give the most screen time to the parts you want to review, you should craft your review process to get the kind of feedback that will improve your product.</p><p>I sort of understand the taboo. Heaven forefend people know what kinds of feedback they should give. You’re “leading the audience” when you say “we’re focusing on the overall workflow, not on details like color or precise wording”!</p><p>Nope.</p><p>People are busy. Especially in high-tech, we have a hundred little details fighting for brain-space, and we context-swap all day. It’s well-known that a bit of constraint helps with creativity, and the same seems to be true of critique. Are you reviewing icon types today? Say that. Are you reviewing the user’s flow as they search their bookshelves? Say that, and possibly mark some things as off-topic.</p><p>This is something that should ideally be done at the start AND at the end of the presentation. Again, it doesn’t take long. “We’re looking at the search work flow today, so how each step flows into the next, and whether the user can figure out what to do at each point in the process. We’re not focusing on visual design — color, fonts, and so on — and we’re presuming the user has already been through on-boarding.”</p><p>At the end of the presentation, that exact paragraph, but starting with the words “As a reminder, …”</p><p>If (when!) reviewers invariably give out-of-band feedback, that’s fine; that’s what parking lots are for. The act of visibly noting something down, in the “useful but off-topic” category, helps everyone stay focused.</p><h4>Be Visible In Your Action-Taking</h4><p>Your job in the design presentation is two-fold: presenter, and receiver of feedback. Sometimes these jobs are sufficiently arduous that they get split into multiple people, e.g., a presenter and a note-taker, or two presenters who swap roles halfway through.</p><p>That’s fine, but whatever solution you settle on, make sure that:</p><ol><li>You actually take notes on the feedback received.</li><li>You take them in a visible way — everyone should know you are paying attention to what they say.</li><li>The notes are intelligible two weeks later when you can’t remember the meeting.</li><li>The notes are shared with the right people. Some companies like the reviewers to get a copy, so they can clarify. Some teams want the notes to “belong” only to the UXer (I dislike this pattern); some like the notes to be part of the Dev team.</li></ol><p>Whatever you do, the notes are now a gold mine, and if you sit on it, you’re a <a href="https://tvtropes.org/pmwiki/pmwiki.php/Main/DragonHoard">greedy dragon hoarding wealth</a>. The feedback is very valuable, but inherently useless unless shared. <em>(What do dragons DO with all that gold? It’s not an especially comfy bed, and it’s not like most ravaging dragons participate in a functioning economy…)</em></p><p>I’ve found in the past that it is best to call a meeting for the whole Dev team to talk through the notes; possibly multiple meetings, if there are a lot of notes. This ensures that everyone blocks out time to pay attention, and distributes the gold to many minds, where it can be exchanged for future improvements.</p><h4>Be Flexible</h4><p>Finally, sometimes you get it wrong. You thought you were coming into the meeting to review search workflow, but you didn’t know they’d just bought a new Search Engine 9000 and really what they want to talk about is how to integrate its UI into yours.</p><p>These things happen. Ideally more <a href="https://en.wiktionary.org/wiki/%E3%81%AD%E3%81%BE%E3%82%8F%E3%81%97#Japanese">nemawashi</a> would have headed this off, but they happen.</p><p>In this case, you have two choices to be productive: pivot the meeting, or adjourn. The latter is a rarely-taken option — it’s hard to schedule people! — but if things are this far off, it’s probably the better option. You’ve got the wrong set of people, the wrong set of materials, and the wrong set of research and ideas in the room. So call it, and schedule another review for later, when you can address the change of environment.</p><p>If you do choose to pivot the meeting, it’s necessary to redraw the ground rules. We <em>were</em> talking about search flow, but now we’re talking about the visual design of two systems and how they work together to feel unified. Fonts, colors, spacing, and so on are back on the table, and we’re going to focus on two screenshots, side-by-side, showing their UI and our UI. You have to do the entire above list in 3 minutes or less, before you lose their attention — that’s why adjourning is usually a better choice.</p><p><em>Hi folks, Alex here. I write on Medium because I like writing and sharing knowledge.</em></p><p><em>If you enjoy what you read, it’s nice to know that all you have to do is literally move your mouse a few inches and push a button to let me know that. I don’t earn any money for this, and I don’t get anything out of it other than the knowledge that, perhaps, this bit of hard-won knowledge helped someone else.</em></p><p><em>Medium doesn’t have a “thumbs-down” or “unclap” button, but if you’ve got thoughts on that line, a comment usually works. And thanks for reading.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bede0694a1ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning How To Practice]]></title>
            <link>https://afeinman.medium.com/learning-how-to-practice-2ca2a79ec64f?source=rss-8528f44ad3b0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ca2a79ec64f</guid>
            <category><![CDATA[skills]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[music]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Alex Feinman]]></dc:creator>
            <pubDate>Sat, 08 Aug 2020 18:42:00 GMT</pubDate>
            <atom:updated>2021-02-15T19:42:09.134Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0XH5mjVKj0OSOHRDbPjuPg@2x.jpeg" /><figcaption>No, I don’t know why someone labeled the keys like this, I just found it that way. (photo courtesy of the author)</figcaption></figure><p>Practicing is a skill. Learning to learn can really pay off. But it’s hard work, and rarely rewarded.</p><p>Background: I trained as a musician for the first thirty years of my life. Music is a fascinating field where there are many orders of magnitude of skill, and you can easily be <em>tremendously</em> better at it than someone else, and yet have many people who are <em>tremendously</em> better than you. (I’m in that middle area, a “talented amateur.”) I only know of a few other areas like this — chess, for example; many sports, due to their competitive nature; some arts; and some mental endeavors like programming may or may not be one, I haven’t decided.</p><p>To get better at music, you need the trinity of aptitude, experience, and focus. It’s pretty indisputable that there is some sort of inherent aptitude — some of which may be formed early in infancy, when we’re learning sound and language. Focus is a topic for another day. Experience is training your body and mind to do what you think you can imagine; and the intersection of focus and experience is practice.</p><p>Today’s subject is <strong>practice</strong> how to teach your body and mind to do the thing. I’m going to contrast this with <strong>performance</strong>, which is when you seek to achieve the main goal of what you’re practicing.</p><p>Performance is when you’re graded; it’s where you score real points, earn promotions, face real opposition. Practicing gets you to performance. It’s important to understand that practicing is NOT “performance, but a lot”.</p><h3>Step one: What Needs Achieving?</h3><p>It’s tempting to practice “everything”. “I’m going to practice piano”, you say to yourself. But in practice (sorry), it’s important to know what you’re trying to achieve. “I’d like to get Beethoven’s Moonlight Sonata to the point where I can perform it” is slightly better; “I’d like to get measures 72–144 (i.e. the fast part) up to a tempo of 96 bpm with no missed notes” is a much more concrete, measurable goal.</p><p>(Side note: this itself is a step along the goal of getting to “performable”: I don’t mean to imply that getting all the notes right is sufficient for a ‘good’ performance, but it’s generally necessary.)</p><p>Athletes practice this way. Boxers don’t train for “boxing”, they might train for “punching for a two minute round, solid, with no missed shots”. But most things in our life don’t break down into nice metrics like measures and tempos and perfect placement of fingers. So it’s up to you to find structure in your task, because that’s how you’ll figure out how to practice it.</p><h3>Step Two: Figure Out How to Make Steps on the Way to Achievement</h3><p>Got your goal? Good. Now you have to figure out how to trick your body and mind into learning. Generally, we learn best when we stay in the <a href="https://en.wikipedia.org/wiki/Zone_of_proximal_development">Zone Of Proximal Development</a> (aka ZPD), that region where things are hard but achievable. If it’s too easy, we’re not progressing; if it’s too hard, we’re not learning.</p><p>This is an exhausting state to be in. So it’s a state we enter and come out of — pushing ourselves a little, then pulling back a little to “lock in” the learning.</p><p>Back to our example. Since the goal is to get the fingers and mind working in concert, we might start with things that are predictable and help forge that connection. Scales are often used for this, though I find that scales aren’t super helpful for me. I prefer something like Hanon’s Exercises, which are repetitive patterns up and down every key signature, and at this point are pretty much rote for me. They get that connection forged, and get your fingers used to the feel of the keys again, the sense of working together, etc. (They also force you to work the two hands in unison, which is another necessary bit.)</p><p>There are many stops along the way; I’m going to break them out into their own maxims.</p><h4>Maxim One: If you Practice it Wrong, you’re Learning it Wrong</h4><p>A next goal might be to learn the actual notes. Trying to simply play through at tempo is going to learn it wrong: you’re not sufficiently skilled to play it yet, or you would do the thing. With music, once again, there’s a simple dodge: reduce the speed. Playing a piece of music at half or one-third tempo is boring, but it does let you see what’s coming next. (I don’t mean the slow “picking it out” stage, which may precede this depending on your skill level with the instrument; I mean actually _playing_ it at a tempo which is vastly slower than the target tempo.)</p><p>Another trick is to play it in slanted tempo: play it with dotted rhythm, slow-fast doubles, like swing. Then play it with reverse-dotted rhythm, fast-slow. Congrats! You’ve just played every pair of notes “fast”. Do it enough, and you can play it all fast.</p><p>Another trick is to play a subset: just the right hand, just the left hand. Just the melody line, but using the fingers you’ll use when you put it together. Just the first two voices.</p><p>The goal here is to simplify enough that you <strong>get it all right</strong>. If you get it wrong, you’ve just played it wrong, and you’re teaching yourself the wrong version.</p><p>Note! This is very challenging! It’s easy to get fatigued and give up, and say, dang it, I just wanna play. That’s okay. But it’s not practice, and will set you back if you want to improve at the thing.</p><p>In sports, this sort of mock practice can be seen in things like slowly practicing a golf swing, or pre-visualizing what you’re going to do. (Some of this is practice for body; some for mind; some for both together. Those are each separate steps.) A while ago I thought up this idea for an exoskeleton that you wear, which limits your motions to the “right” ones for a golf swing or a baseball pitch, literally forcing you to do The Right Thing; it sounds like this idea is finally, 15 years later, becoming reality.</p><p>Without such a thing, you have to be the exoskeleton for yourself. Do it right, every time. If you’re not doing it right, slow it down. Start again. Clear your mind of the wrong.</p><h4>Maxim Two: Pareto-optimality is Insufficient: Focus on the Hard Parts</h4><p>Pareto-optimality is sometimes misquoted as “good enough, everywhere” or “a 90% solution is better than no solution”. (It really means “the state where you can’t make one thing better without making something worse”.) But we’re not in that sort of zero-sum game here. We want “better, everywhere it matters, and no worse in the rest of the places.”</p><p>So the next thing to think about is where you need practice. “We don’t practice the easy parts,” a teacher once said to me, when I complained that practice was hard. This has to be filtered through the ZPD and exhaustion, of course, but in music, people will forget the 999 notes you got right and remember the chord you blew. Another music teacher: “In baseball, if you bat .500, you’d be the best ball player of all time! In music, if you miss half the notes, you wouldn’t make it into the audition in the first place, and even if you get 99% of them, you’re still not going to get through it.” Music requires a certain kind of perfection as a <em>starting</em> point.</p><p>(Side note: there are some types of music where this is adamantly not true; some types of jazz, notably, recast certain mistakes as ‘creative exploration’. Nevertheless, there are many categories of mistake which are equally disruptive as a wrong harmony in a Beethoven sonata, and being good at improvisational jazz is about making the right sort of mistakes, and ameliorating the impact of the wrong sorts.)</p><p>Programming is a bit like this; any disharmonic mistake is a bug. We ship software with bugs in it all the time, of course, and every one of them has a chance to cause serious problems.</p><h4>Maxim Three: Make Things Locally Hard, but Easy to Judge</h4><p>This falls out of the above. To get better, you have to break out of a local maximum of skill by forging into the wilderness and challenging yourself. But it’s hard to see if you’re making progress if all you can see is trees.</p><p>In music, a traditional way to judge yourself is with a metronome. It keeps a constant time, which is better than nothing — on your own, the tendency is to slow down for the hard parts and speed up for the easy parts. (Unless you have perfect timing; I have a drummer friend who has such. “Hey, Russell, 72bpm? Thanks.” It took him many years to cultivate, including a stint Trained By A Master at some French school where they literally just drummed all day.)</p><p>The metronome gives you constant feedback, once per beat, about where you are with respect to your goal. You can adjust it easily, up or down. As you practice, you adjust the tempo to adjust the difficulty and keep yourself in the ZPD. You can use it as a unit test against your progress.</p><p>Well, the combination of the metronome and your ear; you still have to recognize your performance as sub- or up-to-par.</p><p>In professional sports, this job falls to the trainers. They watch your swing; they time your lap; they give feedback on whether you’ve lost form after 1m 52s of solid punching. In chess, one way to approach this is to put yourself in situations from past masters, then force yourself to continue the game from there — and then compare your solutions to theirs, giving you feedback on what others have thought about that situation.</p><h4>Maxim Four: Quantity Has a Kind of Quality</h4><p>Our bodies and minds are made up out of neurons that require repitition to adjust. (There are exceptions, where a very strong signal causes us to learn something immediately — think food poisoning — but those generally aren’t things you practice.)</p><p>So do it a lot. A lot. This is where the myth of “10,000 hours of practice” comes from. Highly-skilled people are finding ways to practice all the time. Professional musicians may devote 4–8 hours EACH DAY to keeping at the top of their game. Writers talk about writing thousands of words a day to keep in practice. We, the mere mortals, might not have to go to such extents, but we do need to practice more than might be obvious.</p><p>This is super challenging in a white-collar setting. Most “professional” jobs contain exactly zero opportunities for practice: you’re expected to perform, all day every day. So it is up to us to carve out practice time, from work time when work earns a benefit from it. More clever organizations are realizing that this is necessary, but most are still in this weird Capitalist loop of “hire practiced people, force them to perform 100% of the time, then fire them when ‘somehow’ their skills atrophy/don’t progress”. It’s kinda bullshit.</p><p>This “repeat the hell out of it” is what I’ve been taught to call <a href="https://en.wikipedia.org/wiki/Woodshedding">woodshedding</a>, the idea being that you take your instrument and go out behind the woodshed where no one else will be bothered by you playing the same four measures over and over again at slow tempo for two hours. (Not to be confused with <a href="https://en.wikipedia.org/wiki/Law_of_triviality">bike-shedding</a>, where the uninformed have opinions that derail the central conversation.)</p><p>Shedding is also where you start to learn your instrument, by which I mean yourself. It can be a kind of meditative practice in which the actual thing you’re practicing goes away, and you learn what is between you and it. It lets you see what <em>you</em> bring to the situation, and seek to improve on it.</p><p>Shedding is <strong>HARD.</strong> That leads us to the next step.</p><h3>Step Three: Figure Out When to Stop, Rest, and Reflect</h3><p>Practice is hard work. If it’s not, you’re not practicing; you might be reinforcing, but you’re not improving.</p><p>As a result, it’s easy to exhaust yourself practicing, and then you start taking shortcuts. You start doing it wrong. You’ve stopped learning, and in fact, you’re unlearning — you’re undoing the hard work you just put in! It’s time to stop and catch your breath.</p><p>This point is different for different endeavours. When trying to practice for cardio, say, for a marathon, it’s <em>crucial</em> to push yourself past what your body tells you is “enough”. The learning process — the practice — includes improving your ability to judge the point between “I can’t do this any more (it’s so hard™)” and “I *CAN* *NOT* do this any more (or I will hurt myself)”.</p><p>This stopping-point-decision can be a very tricky for non-physical endeavours; we’re not trained to recognize it, and in fact receive lessons all the time that we’re super human and should be able to do it for infinitely long.</p><blockquote>[Far Side]Teacher, can I be excused? My brain is full.[/Far Side]</blockquote><p>So go ahead. Rest. Weightlifters know that their bodies need to heal — traditionally, you have “leg days” and “arm days”, and alternate; as you get older, your muscles need more time to heal the microtears, and so this might become a three- or four-day cycle.</p><p>But! The downtime is not just for rest. It’s for rumination. After you’re not quite so blasted by the practice, as soon as you can, you need to assess what happened during practice. Did you make progress on something? Hurrah! Put it in the “lock it down” pile for later (see step four). Was something unexpectedly hard? Put it in the “woodshed” pile. Is something confusing? Break it down into smaller pieces. Something has come together? Lock it down.</p><h3>Step Four: Lock It Down</h3><p>Once you’ve got things in a good place, it’s time to lock it down: get it inside you so it can’t escape. We’ve all had the experience where we cram for a test, pass the test, then can’t remember whatever we spent four hours learning. That’s because we didn’t lock it down, and it got away.</p><p>Locking it down is a different sort of practice. Instead of challenging yourself to learn, you’re challenging yourself to integrate that learning into the larger body of work that constitutes “you”.</p><p>Some of this is achieved through Mere Repetition (more woodshedding); some is achieved by integrating the work into what surrounds it. You might play the pieces from a few measures before the hard section, and from the hard section into the next section, to practice on the transitions. You might luxuriate in playing the whole thing, if it’s “good enough” and start thinking about the next layer you’re going to learn (for music, traditionally, this is where ‘interpretation’ comes in).</p><p>In sports, this sort of integrative work is seen in more complex routines (e.g. kata or long weapons forms in martial arts), in sparring or scrimmages, etc. These are highly stylized spaces where practice can be performed without the actual rigors and stress of performance — you’re still in “practice” mode — but they provide a way to integrate the words and sentences you’ve been teaching your body into a full-fledged statement.</p><p>This is the actual goal of business practices that usually get relegated to the BS pile, like “retrospectives” and “hansei” and “performance reviews”. The ideal goal is not to judge performance, it’s to lock in the learning and achievement (as well as do some of the “ruminate” part of step 3). Sadly, in corporate America, these steps are usually used to punish, shame, or otherwise derail any attempt at learning.</p><h3>Finishing Line: lather, rinse, repeat</h3><p>The great thing about learning is that it never ends. Every time you learn something, conquer a bit of possiblity space, you realize that you’ve just increased the surface area of things you <em>could</em> learn, could improve. (With rare exception. Sometimes you’re filling in holes. But those are usually times when you can abstract away an entire nugget into a whole that you can use for other things. “Okay, I understand how to construct a major and minor scale in any key! Now I can ‘play scales’. What can I do with that knowledge?”)</p><p>You’ve learned all the hard parts, by identifying them, isolating them, woodshedding them, and assessing your progress. What you’ve got, you’re going to keep, thanks to locking it down. You’re rested and think there isn’t anything left in your original goal. Woo! Celebrate! Perform! Dance in the streets!</p><p>Then get back to practice, because there’s always more to do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RZAcnEjUYbn2xtIfKfCQWw@2x.jpeg" /><figcaption>She would <strong>like</strong> to let me practice, it’s just so <strong>comfy</strong> here… (photo courtesy of the author)</figcaption></figure><h3>Conclusion</h3><p>And that’s it. Four steps, with many ways to achieve them. Four <em>hard</em> steps which require challenging the ways we are taught to learn, and contradict the way that most of us are rewarded.</p><p>No one said it was going to be easy. But it’s better than spinning your wheels, lying to yourself about measure 76 and that tricky run in the left hand that you mumble your way through, knowing that you could get it if you just spent a few hours teaching it to your body and mind.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ca2a79ec64f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>