I guess what you’re describing is like a tweet that hits the uncanny valley of good and bad in such a precise way, with such confidence, that it just pisses everybody off.
Because if you look at this tweet for just a second you’re like ok, that’s a fine bedroom, but then you look at it, and it starts to unravel in your mind, like trying to remember a dream after you just woke up. And you’re like “what is this?” It’s like a deepfake of a person’s face.
…Ok, I’ve got some fire for you: A bad tweet is like a deepfake of an idea.
The perfect bad tweet is like something you read and you’re like “ok yeah” but then you’re like, “wait…”, and it just starts to come apart in your mind and you’re like that makes no fucking sense, just like this photo of this incredibly bad room.
One thing I've been enjoying about working as a technical writer is that the minute-by-minute texture of the work feels right. Something about formatting text, faffing about with SVGs, trying to rewrite a sentence more clearly... it's just enjoyable in itself, and I feel at home with it.
...Working as a programmer was very much not like that. There's something in the rough vicinity of professional dev work that I do like, which I could probably label as 'iterative hobbyist tinkering with websites'. I like working on something with a strong visual component, and I like to be inside of a fast feedback loop, and I'm mostly interested in just somehow bodging through until it works. I'm not very interested in either the computer-sciencey side of programming — data structures, algorithms — or the software-engineerey side of making things run reliably at scale in a maintainable way. So maybe it's not surprising that the minute-by-minute texture of professional programming was just... kind of bad. Occasional fun bits when I got into something, but the background experience was not fun.