I don’t think I really need to explain much, their admins are transphobic. 
https://hexbear.net/post/1587342
Snowe, an admin, complained about a transgender person being offended over being misgendered. Ategon made an apology post but keeps snowe on, no public apologies from snowe to the transgender people affected.
Textbook 
note: conversation about Ategon’s use of the word triggered edited out, might be misunderstanding, need clarified
pretty good chance if you come across a programming.dev user commenting on hexbear it’ll be some reactionary shit, too
given the comments are far worse than what the admins have said, yep
Death to programming
except the cool kind
programming should be a profession in the way writing is. The only reason it’s not a universal skill is because the field is full of manchildren who either fetishize shitty technology from the 70s for aesthetic reasons or don’t actually know how to code so they build 15 layers of abstractions on top of eachother and 90% of the effort is spent dealing with the garbage these people spew out.
This whole programming thing is boring and looks like it takes too much effort to learn for too little benefit for the average person. Just replace them with the cool trans programmers tbh.
I like it as a puzzle solving exercise - fitting shaped blocks together in my head and letting the compiler tell me how my answer doesn’t make sense. but yeah, it attracts the worst people. I’ve met… 5?.. cool people in a dozen years working professionally.
IMO there wouldn’t be a distinction between programming and just using a computer if these ppl weren’t so convinced they were super special bois and everyone else should only use computers through software made for toddlers.
Most of my students don’t even know what a directory is.
I mean that kinda proves my point. They don’t know what a directory is because they spent most of their time on computers(phones and tablets) that hid the file system from them. It’s not like it’s a particularly hard concept to grasp.
I’m struggling with this notion of something being hard to grasp. I don’t think that’s an intrinsic property of the concept itself so much as environmentally determined; they don’t need to know what a directory is, so they don’t ever learn it, and when it comes up in a classroom, it’s so removed from their daily experiences that some of them never seem to grasp it.
I dunno, it’s a dialectic a guess.
I disagree. If employers could simply not pay people such high salaries, they would. There is still an inability of the education system of most places to produce enough programmers to create a significant reserve army of labor of programmers. I don’t like techbros either, but the idea that what they do is not highly specialized and doesn’t take a significant amount of training to do is nonsense.
Being able to read and write was considered a rare skill that commanded a high position in society too. Scarcity doesn’t mean that the field is inherently hard.
In theory, getting a CS degree is about mastering computer science. In practice, CS grads spend their time memorizing the syntax for 30 different types of regex and write CRUD apps their entire career. The particularly talented ones will devote their time to creating a 31st variant of regex 30 layers of abstraction away from the actual hardware that uses more resources than an actual supercomputer from 2008. Ask these people basic questions about something as simple and commonplace as unicode and they’ll get it wrong more likely than not. This is why if you go on the orange site they constantly complain about having to solve the most basic problems during interviews.
So where we are right now is the medieval scribes stage of development. Most of these people’s only skill is that they can write code at all, not that they’re particularly good at it. Just like a medieval scribe’s main skill is simply the ability to read and write at all, and not like, literary analysis or philology.
I think it depends on the school you go to. some programs are basically math degrees and others are glorified job training of the type your describing. of course, to get a job after school, recruiters expect you to have both the CS theory and direct experience writing code. they stop checking for the CS background after the first job because it’s not something anyone stays proficient in, except in a rough heuristic sort of way. most training happens after you graduate in your first job or two.
the main differences between coding and writing are that 1. the former is predominantly a team activity and 2. the interface with the machine forces a maintenance burden on everyone that interacts with the code. in tandem, this means that if you write bad code, it’s not just your problem - it’s not merely that another person reading your code will struggle to understand what you mean but also that someone else after you will have to figure out how to change it to meet new needs.
capitalists try constantly to eliminate these factors and turn software into something that can be mass produced for no/little cost but they keep failing (for now) because they try to ignore the social factors (same reason AI code won’t work for a while yet). that doesn’t justify programmer egos, it’s just an explanation of how software development differs from normal writing.
I still think it takes a significantly larger amount of time to teach someone to read and write than it is to teach someone how to program. My point is that if it were that simple, corporations would have jumped on that ASAP and made it a commonplace skill, because then they wouldn’t have to deal with worker shortages and they no longer would have to pay these people a living wage. I also think It’s more akin to teaching someone stonemasonry or woodworking or something than it is basic literacy, and personally I refuse to spend any extra hours of my time having to deal with programming. I already have a job and I barely have time for my hobbies, I’m not going to spend my time learning how to do someone else’s.
That place is absolutely the personification of