4 ms·
It's more human oriented than writing math proofs! Why is the gap between those two fields double digit percentage points?
by tptacek 2y ago
It's more human oriented than writing math proofs! Why is the gap between those two fields double digit percentage points?
- Jensson 2y agoStatisticians works directly with managers, almost all math professionals are statisticians and not doing theoretical maths.
- cauch 2y agoStatisticians are working less with managers than developers. Developers are supposed to be constantly fed back from the product users, and in practice, it means they interact with a bigger surface than statisticians. They may find ways to avoid interactions, but it is not "because developer is not people-related", it's because they want themselves to not be people-related. So, no, computer science is not less people-oriented than statistics. You may personally interact less with people, but it is just because you are personally less people-oriented, not because your job is fundamentally less people-oriented.
- tptacek 2y agoIn addition to what the sibling comment said, I am referring to academic mathematics.
- _05hb 2y agoMath proofs only need to convince other people. Programs need to convince a compiler. If compilers were people and you talked to them for the first time, the only reasonable response would be to call them assholes and find new friends. The field of mathematics doesn’t have an equivalent of the “Norway Problem.” Here’s my theory. Learning how to write code causes damage to the mind, particularly in the area of how you relate to other people. When we’re learning to code, men and women both notice this happening, but men care less. Women, on the other hand, tend to think, “this is bad and I should stop.” It’s hard to become a programmer without becoming a weirdo in the process, and women have a lot more to lose by becoming weirdos. If we knew how to learn programming without the mind damage -- if we could figure out how to allow learners to skip the “coal face” of spending long hours into the night talking to a compiler -- then that would solve the gender imbalance. Just my theory. For a good long stretch I thought the explanation was that tech compensation wasn't actually all that great compared to what women could earn in other fields, and then the explosive comp growth of the mid-late 2010s happened and I've been wondering about what is the problem ever since.
- cauch 2y ago> Math proofs only need to convince other people Wait, what? A math proof does not need to convince anyone: the proof exists or does not exist. If I prove X, then I don't need to convince other people that X is proven, they just have to read the proof. So, in practice, math is even worst than computer science. In computer science, you have to convince the compiler. In math, you need to convince math. You need to build an algorithm that compiles under the tons of math logic rules. > if we could figure out how to allow learners to skip the “coal face” of spending long hours into the night talking to a compiler But learning math and trying to build math proofs is even more "coal face-y". There is no pre-build debugger and you need to check things yourself, by hand, and when it fails it may be because you mess up the algorithm part or the compiler part. > Learning how to write code causes damage to the mind, particularly in the area of how you relate to other people. When we’re learning to code, men and women both notice this happening, but men care less. All of that is cultural. The developer mentality cultivates this idea that being burnout and being socially rude is a sign of success and is a manly thing to do. There is no reason why writing code causes damage, because it does not happen to plenty of other activities that are as grinding. Again, developers are not special, what they do and what they live is similar to a lot of other things. It feels more like a rationalization: the reason men get worse at relating to other people and become weirdos is because these men are failing at social life because of their mentality.
- _05hb 2y agoThanks for responding. Here’s what I mean about proofs. I learned how to do them in college, and in the early classes we got a lot of leeway on grading, and then as we moved up they expected more and more rigor. But it was still a conversation, like if I got dinged a few points on an exam question, I could take it to my professor and make my argument that my proof was valid, and I might get a point or two back. The proof-as-mathematical-object either exists or does not, but deciding whether my answer pointed to that proof was a social exercise. Professional mathematicians also cut either other some slack. Most proofs published today have small errors — typographical, skipped steps, etc — and those bugs are never fixed. Despite the bugs, we’re confident in the results, and that confidence is a product of social consensus. On the other hand, also in college, I had my programming classes, where I would turn in my code and they ran it through a test harness, and my grade was the number of tests that passed. So, if there was a syntax error, I got a 0. This was brutally harsh to the good students who attended every class, took notes, and studied, but who did not conform their minds to writing code. But that’s how we learn programming, because the compiler doesn’t care about intentions and “almost” is worth nothing. Alan Perlis said “programming is an unnatural act.” It’s not harder than other jobs — in many ways it’s easier — but it’s much weirder, and it makes you weird. Professional programmers write bugs, constantly: why can’t they just write the code, without the bugs? Because our minds aren’t built that way.
- jimbokun 2y agoI was not aware of that and it looks like math is an interesting exception. Any theories on what’s responsible for that difference?