I couldn't make it. I gave up after 2 paragraphs. The random meandering from one thought to another without saying what the point of all this is got to me. I'm sure it's not a problem in the post. It's definitely a "me problem". Would someone be kind enough to post TL;DR of some sorts?
I had the same issue. I think that their point boils down to what we consider "technical" as a label on people. Basically that "technical" is more of an identity rather than someone having a specific skillset. Something the author feels excluded from, even though they do work that's relevant and impactful.
I think so anyway. As I said, I had the same issue as you having difficulty getting through it. The article takes a long time to actually get to a point, circling around things rather than concretely building towards something.
If I had to guess it is more of a flow of thoughts and not really a classical argument.
It also makes it hard to draw any conclusions about it. Because I think I sort of get where they are coming from, but at the same time I am not sure if I entirely agree. In my line of work technical just means "being skilled with IT related technical skills" without a judgement about other skill sets. It is just there to distinguish between people who can dive into systems hands-on and those who have other skills and bring value in other ways.
It seems to be about the way "technical" and "non-technical" are thrown around with implicit assumptions in conversations in places like this as hard categories. You're either technical, or what are you doing here? Are you lost? The door is over there.
A key paragraph:
>> "This is because Technical is a structural designation that operates outside of any actual problem-solving you and I are doing together. Being Technical is about being legitimate. Or to put it more simply: it’s because you are Technical that I can’t be. We have created the identities this way. A person with a PhD in human things and who deals in human problems and human solutions cannot ever be Technical no matter how dense her statistics are, how many conferences she speaks at, and how comprehensively she has given examples of generating outcomes that are often beyond engineering to generate (change over time; impacts on humans; making legible even an imperfect approximation of just one single emotion). These things can be useful, interesting, valuable, heartrending, inspiring and memorable to tech, but they cannot be legitimate."
I'm still reading but it does seem to be about gatekeeping while avoiding any language that would set off a Technical person.
The author just want a medal saying they're Technical. Whatever this means, it is important to them. Like a child and a sheriff medal. "Technical" is the current cool club to be in and they want in. I guess technical is "techbros and their salary", not your average electrician and even less a Toyota Hilux with a 50 cal. in the back.
I've noticed that a lot in discussions like this. Some people seem to have the impression that if you get the credentials or achieve a certain level of work, someone comes along and bestows a title of respect on you (here, "Technical") or welcomes you officially into that club. They seem to think that's how it works for everyone else (or some other group), and complain because that hasn't happened to them.
But I don't think that's really how it works for anyone. I've been doing "technical" work for three decades and no one's declared me Technical or anything else. Some may consider me that and others may not; it's never occurred to me to ask. How I feel about whether I deserve to claim that title is up to me, and shouldn't really depend on others.
> The author just want a medal saying they're Technical. Whatever this means, it is important to them.
I don't think that's quite it.
> I guess technical is "techbros and their salary"
That is it, from what I can tell. "Technical" is "you get US coastal techbro power and money". Which, most "technical" (lower-case) people working in computing also don't get, even in the US.
This author wants sciency work in fields with more women in them than computing has, to be valued in terms of pay and prestige as capital-T "Technical", and defines "Technical" such that people deciding who gets that pay are somehow within it (rather than very much not within it, as would be the case for most of the category I think the median HN user would call lower-case t "technical", which is part of why so much of the essay is hard to follow until you've figured that out)
This is why the piece is so hard to follow: this isn't made clear until way down near the bottom.
I actually read your comment while still around the halfway mark of the piece, and assumed it was reductive and way off the mark, but I think you've located the actual heart of it, now that I've finished reading it.
> Would someone be kind enough to post TL;DR of some sorts
I found o3 to have done a decent job of it:
- Technical as structural identity: Being "Technical" is a power‑laden designation that shapes reality and enforces belonging, not a neutral skill measure.
- Dehumanization paradox: The system prizes flat emotions yet sustains itself by choosing emotions over efficacy, repeatedly devaluing human needs.
- Excluded expertise: Human‑centered work — psychology, caregiving, storytelling — is repeatedly labeled illegitimate despite its practical and moral value.
- Boundary policing: The "Technical" boundary is preserved by rejecting both outsiders and insiders who push its limits.
- Caring as resistance: Genuine care, narrative, and solidarity with those left outside offer a path to rehumanize tech beyond mere "Technicality."
- Collective rebuild: A hopeful call to action—tech builders possess the capacity to dismantle and reassemble systems to include humanity at their core.
