6 ms·
I wrote a blog post a few years ago[1] making a similar claim about computer science. I said there’s 3 main camps of programmers: - People who enjoy programmin
by josephg 6y ago
I wrote a blog post a few years ago[1] making a similar claim about computer science. I said there’s 3 main camps of programmers:
- People who enjoy programming because it’s mathematically beautiful (eg Haskell programmers)
- People who enjoy programming because they like reasoning about machines, and like mechanical sympathy (eg C programmers)
- And people who like programming because it can solve real problems for their users.
I got pushback here and elsewhere that lots of people fit into multiple camps - which makes sense. Maybe they’re better described as an ecology of values. But I also think there’s something real here. I worked in a consulting shop a few years ago and my boss came back from some front end development conference gushing about a talk he’d seen that I had to watch. The talk was a layman’s description of FP’s immutability approach applied to react. My boss had never heard of immutability before because it had never come up in front end web development circles. There’s lots of opportunities for our software to improve by cross contaminating all our best ideas.
[1] https://josephg.com/blog/3-tribes/ https://josephg.com/blog/3-tribes/
- Karrot_Kream 6y agoFantastic! Thanks for this. The FP vs non-FP split has always just felt like a less rigorous version of the "analysis vs algebra" or "problem-solving vs theoretical" discussion and I'm glad I'm not alone in thinking this. This is also what rubs me the wrong way about the simplistic level with which FP languages (like Haskell or Scala+monads) are either cargo culted or hated. The truth is, the two perspectives really go hand-in-hand, and we're all the worse for not realizing this.
- Kalium 6y agoIn my opinion, the FP/IP split is fueled in no small part by a wildly divergent set of vocabularies. A dozen different <greek letter> transforms are inscrutable to anyone who has not spent much time studying Lambda calculus, and the concept of a monad is famously difficult to explain. You wind up with two camps that cannot communicate. It's often made worse by the functional programmers - who are mostly also imperative programmers - doing a poor job of enabling translation.
- ukj 6y agoAll notations (programming or Mathematical) are just different ways of expressing computations. All notations have trade-offs at the level of semantics making certain operations more difficult to express (what programmers refer to as 'the expression problem') That's the entire shpiel of reification/first-class citizenships/semantics of programming languages. Instead of getting into fanboi-ism of 'my language is better than your language' perhaps approach the problem from first principles (design): what is "IT" that you want to talk about, reason, express and manipulate in your program? That dictates the sort of language you need to solve the problem that you are trying to solve. https://en.wikipedia.org/wiki/First-class_citizen https://en.wikipedia.org/wiki/First-class_citizen https://en.wikipedia.org/wiki/Reification_(computer_science) https://en.wikipedia.org/wiki/Reification_(computer_science)
- 29athrowaway 6y agoAnd people that do not care about any of those things and just want a paycheck, or to be promoted so that they do not have to code anymore (95% of developers worldwide). Unfortunately the people that get excited building things is outnumbered by the people that is just in this for the money.
- josephg 6y agoI'd love to see actual numbers on this. Its not 95% - but all of our intuitions will be a bit wrong because people cluster in workplaces based on personal values. So no matter what you're like, you'll end up working with people similar to yourself. I wouldn't be surprised if people who just program for a paycheck are the majority of employees in many offices. I know they're a tiny minority in a lot of the places I've worked at. That's not a boast or a coincidence - humans cluster in tribes based on shared values. I don't consider myself part of the same community as people who show up to work to close jira tickets and collect a paycheck.
- 6gvONxR4sf7o 6y ago> I'm not sure it makes sense to describe people who love programming and people who just do it for a paycheck as truly being in the same field. This is why I keep my mouth shut IRL about just wanting the paycheck. I'd imagine a lot more than a tiny minority of people are just there for the job where you've worked. We just keep our mouths shut because the passionate folks judge us paycheckers.
- eru 6y agoIt's fine to optimize for the paycheck first and foremost. But while you are at your job anyway, might as well make it slightly less of a drudgery while you are at it. (Eg I quite like functional programming. Both because I like the style of thinking, but also because I don't trust myself nor anyone else with code; and eg a heavy emphasis on immutability means that I'm less likely to get woken up in the middle of the night with some production problem.)
- throwaway17_17 6y agoI remember reading one of threads on your post here. The level of depth that the commenters went into regarding every possible permutation and exception to the broad classification were astounding.
- tarsinge 6y agoInteresting. I am definitely of the third kind since I'm a kid. But with the years I've come to appreciate mathematics (maybe FP was a gateway), and machines through wanting more real world connection, learning electronics and building physical things. Totally agree with your conclusion, no matter the path, all these aspects are important.
- quickthrower2 6y agoI’m a multi camper as I studied maths but originally got into programming as a creative pursuit. Guess us multis are going to pipe up!
- deleted 6y ago[deleted]
- kebman 6y agoI like C-like programming languages, and I like to solve real world problems for my users. So two camps, I guess. Moreover I was always that annoying kid in class who would ask the teacher, “but what use is that?” Often the teacher couldn't even answer this very simple question, and every time that happened it left me really unmotivated to learn. The epiphany came in Upper Secondary school when a math teacher shushed the other pupils and actually took his time to tell me what {insert abstract math topic here} was actually good for. This changed a lot for me, but as far as grades go, it was already too late. Though at least it left me interested enough to research some things on my spare time, so when I finally came to the university, I almost couldn't believe my own eyes when I started to get good grades on (for me) pretty advanced math topics. I obviously still have a pretty big disadvantage in mathematics, but researching things that require stuff like abstract algebra and calculus is now much less of a hurdle for me.
- deleted 6y ago[deleted]
- bluetomcat 6y agoThose 3 categories fall into the broader category of "enthusiastic programmers" which aren't the majority from my experience. Most people want to leave the office knowing that they have made some progress with their assigned work, knowing that they haven't screwed anything generally and being able to sleep at night. The thing about being "enthusiastic" is that certain cultures and organizations wouldn't at all recognise it and an otherwise enthusiastic programmer can easily become a drudge when the business requirements are just some company-specific internal rules changing all the time.
- eru 6y ago> [...] an otherwise enthusiastic programmer can easily become a drudge when the business requirements are just some company-specific internal rules changing all the time. It's not even that: you can take company internal rule changes and make it 'fun'. Or at least as fun as anything else. It's perhaps more the attitude of the organization. Both the wider organization and their software making department(s).
- globular-toast 6y agoFor me, these are three different hats that I keep on my hatstand. I like them all. The dream is to wear all three at once and get paid for it. But, in practice, I'm always wearing hat 3 when I'm getting paid and, if I'm lucky, I can put on one of the other two for a while too. However, I have worked with many people who appear to never switch hats.
- stared 6y agoThe camp 3 is called "professional programmers". I mean: - sometimes a practical problem benefits greatly from a well-designed high-level abstraction, - sometimes a practical problem strictly requires low-level optimization. And yes, it is totally fine to have one's inclination in general, pursue them to any level in their free time, or in some (but not all) academic research. Yet, if a professional software engineer consistently favours one of these motivations over adding value to the product, usually there are frictions in the workplace. I guess you all know "let's rewrite it to Haskell" people, or ones using their favourite paradigm for everything, and against everyone. Or ones that squeeze 20% performance in a place of code that does not matter at all for the end user experience.
- msla 6y agoAnyone getting paid to program is professional. We need to disabuse ourselves of the notion that "professional" implies any kind of quality, or that the people who program without being paid money are doing a bad job of it, for that matter.
- enriquto 6y ago> wrote a blog post a few years ago[1] I thoroughly enjoyed your post at the time! One thing that I disliked, though, was the inaccurate caricaturing of people on camp 2. For example: > Low level languages are often better than high level languages because you can be more explicit about what the computer will do when it executes your code. (Thus you have more room to optimize). My concern is the last parenthesis. I am squarely on camp 2, but I'm almost never concerned for optimization. I want my code to be very explicit because I want to understand clearly what it does (thus I hate C++ and other untoward abstractions). Thus clarity is the main motivation, not efficiency as you put it.
- nicoburns 6y agoPerhaps you are a detail-oriented person? I've met quite a lot of people who - like you it seems (although perhaps you disagree) - find things that are low-level and procedural to be clearest. Such people often like languages like C and Go where this style is encouraged. On the other hand, I tend to think in terms of abstractions. And thus find things much clearer when they are based on high level abstractions (things like map and filter, RAII, pattern matching, etc). And I like languages like Rust and TypeScript where I can express those. If I read a for-loop, I have to translate it into a more abstract higher-level function in my head to understand what it's doing anyway.
- enriquto 6y agoi think it may be that. When I see some code like this in C++: y = f(x); I'm extremely terrified to what is going on. It is like looking into an abyss. Is this code calling a function named "f" with argument "x"? If so, there may be several different functions "f" depending on the type of "x". Maybe none of them has the same type as "x", but there are some conversions that may happen and lead to that. Or maybe "f" is not even a function, but it is an object that has overloaded the parenthesis operator? And then, what happens to the result, whatever type it has. Is it calling a copy constructor (over some inheritance chain)? Is the assignment operator overloaded? If running this line results in an execution error, I'm totally lost as to where to find the problem. On the contrary, in C, the same line says explicitly what code is executed, without need for further context. If the code compiles, there is a single visible definition of a function named "f" and this is the code that is called. I read much more code than I write. But code with lots of abstractions, like C++ with objects or templates, however elegant was to write, is a disgusting chore to analyze, understand and eventually fix (because the abstractions always fail). On the other hand, analyzing C code is pretty straightforward, even if it was a bit more verbose to write.
- pjmlp 6y agoI belong to the camp that enjoys programing in a beautiful way and has experiemented languages that are capable of achieving mechanical sympathy without having to deal with C.
- colour 6y agoYou bluntly imply that j.blow wouldn't perish from using unity, but offloading to monopolies is really just a race to the bottom.
- ukj 6y agoThe trivial way to unify all camps is to view it from the lens of expressionism/self-expression. Mathematicians want to express equational reasoning/identities. Computer scientists want to express computations. Translation/bridging the gap will be a whole lot easier when both camps answered the trivial 'Why?' question which contextualises the reason for doing whatever it is that you are doing. People without shared goals have the tendency to speak right past each other.
- jerf 6y ago"I got pushback here and elsewhere that lots of people fit into multiple camps - which makes sense." People do fit into multiple camps... however, the camps definitely exist. One of the several reasons I didn't go into academia, and one of the bigger ones overall, is that I could tell I wanted to split the difference between the "practicals" and the "mathematicians". And while this may not have been impossible, it was certainly at the very least a "high risk" move, because you end up with the support of neither camp, and there aren't enough people in the middle to make up for it.