Coding requires almost no physical effort. Everything you do is hidden behind avatars, so furry and anime faces hide the wrinkles and dead eyes. EVERYONE is into coding, or at least wants to be because of the ebin Learn To Code memez pushed by Big Tech and world gubberments, and trannies are part of "everyone". People are promised huge wages and lots of freedom for very little effort, so it's easy to cry sexism/racism/transphobia when your weekend coding camp doesn't result in 300k starting. Everything has tl;dr Codes of Conduct and Terms of Service so there's ample opportunity to police others. A lot of troons are already computer-enslaved anime nerds who are predisposed to computer-centric jobs and hobbies anyway. There's lots of high profile tech people that don't actually do anything tech-related, but still make it look like tech is the important bit and not just where/how they invested. All that makes it pretty attractive to any modern soy-laced lad, but also to troons especially since they're usually goony netizens.
Autists lack theory of mind which means they are bad at abstract thought. I don't know if you're familiar with the pencil case test: it all about tracking who has what information when. Autists really struggle with doing things out of order or understanding how different inputs can produce the same output. There is probably a psychological term for it. For example it can be really dumb stuff like 1+1+1+1 can't equal 1+1+2 because it's not 1+1+1+1. (I can't think of better way to illiterate this) All the inflexibility and repetitiousness comes for this quality. It's not crazy to see that this is the product of having a malformed frontal lobe. Frontal lobe does logic, puzzles, and abstraction. (or reducing abstraction), so if that part of the brain is not working right it really fits why Autists have such particular qualities.
This is another reason they like coding but never seem to be particularly good at it. There's very little nuance to programming basic utilities, and you can get away with building basic utilities out of easily digestible bits of logic. In theory, when you're coding, if you write something, it works the same way every single time. That's more soothing and easier to get started with than any other trade where you have to deal with the wonkiness and imperfections of real materials or have to operate in team environments where people can be particularly flaky or work faster than others. Doesn't help that everything is networked, computerized, and has some proprietary app to go with it. Even to normal people, coding just looks easier and seemingly has a better RoI and RoR than anything else. To insecure autists that love routine and can't handle nuance or variation, not just how easy but
how consistent it looks is a massive boon.
You can also do it completely on your own, since everyone has a computer and you can just rip shit off of StackExchange or GitHub, build it, and feel like a Rock Star Full Stack Developer because you compiled something from source but changed a few lines.
Why they become bad coders though is that they can't move past that stage and think of complex systems in terms of anything other than those basic bits, and are too sensitive to take good advice on how to get to the next level. Like the classic yanderedev style if-then chain, they know that Ifs Just Work, there's no failure to compile or crash at any point, so what's the problem? There's no concept that there must be a better way. As far as they're concerned, they're just playing with LEGO and are building a castle instead of a house so it takes a few extra bricks. But because they're already oversensitive dingbats, anyone saying "hey maybe use a switch" or "oh god what the fuck why are you storing all this character's dialogue in a logic chain as part of the loop that handles renering, why not put it in a file storing a hash map???" is just a transphobic terfy hater
Also, coding is
fucking hard so no wonder they're bad at it.
Everyone is bad at it. I could write at length at how inherently difficult working with modern IT crap is compared to any "traditional" trade but tl;dr. But it does introduce a new issue that keeps them as bad coders -- it's not particularly likely that someone offering them advice is actually offering good advice. The troon making a 6000 line If-Else chain getting told to write it as a Switch instead isn't right to freak out about it, but if there's something in the back of their head going "There's no fucking difference" then they ain't wrong. What was wrong was not refactoring into some other method of checking and reacting. May as well keep it a 6000 line if-else, since it'll all compile to the same thing anyway. Even my example hash mapping solution is probably garbage someone is going to call out, themselves proposing something else that's not much faster or more maintainable, and still won't make you as much money as
VVVVVV did.
Actually, writing that last bit, that might also be a piece that makes it alluring -- no matter what code you write, it's probably better than something that's actually a real and well-liked final product somewhere, so it's easy to be very self-righteous and defensive about your shit code.
On top of all that, it's also A Thing in Open Source communities to just be really haughty about being able to navigate or manipulate things that others can't or won't. It's an easy way to build a sense of self-worth, just like offered by any other field, like I said it's a hell of a lot easier to "build" something by writing "make" in a Kali shell than to field dress a deer or design PCBs.
PS,
For example it can be really dumb stuff like 1+1+1+1 can't equal 1+1+2 because it's not 1+1+1+1.
I have to pick this out because this is a different issue inherent to American education. I'm not trying to start an anti-yanqui derail or anything but math in the anglosphere is taught mostly by rote memorization of tables (usually only up to 12x12, oddly) and the US goes whole hog on it thanks to Common Core and its legacy. So you end up with weirdness like people having it really well ingrained that 6x4 is not the same as 8x3, but not really having a concept of why it matters (or that it doesn't most of the time). This understanding of numbers as discrete objects made up of other discrete objects is also what gets you nonsense like "binary clocks" that are made up of columns of LEDs representing base-10 numbers