5 ms·
When people wonder why my typical comments run on to multiple screenfuls, it's because I'm armoring them against this sort of dismissive snark. I was in between
by jerf 8y ago
When people wonder why my typical comments run on to multiple screenfuls, it's because I'm armoring them against this sort of dismissive snark. I was in between tasks today and lacked time to make it longer.
- ajross 8y agoOK, long form: you whooshed on the point of the linked article entirely. Software exists to solve problems, not to achieve some sort of aesthetic ideal. Time spent in pursuit of abstractions (or skill in the expression of abstractions) is wasted, by definition. You seem to be conflating the two. To wit: spending hours giting gud at Haskell doesn't translate to hours saved solving real problems (like the one in the link -- a straightforward list operation anyone could code in an imperative language in a few minutes). And your inability to see the humor in that (or the expository value of a good quip) is... well... let's just say more evidence that you're head is pointed somewhere other than the correct solution space.
- jerf 8y ago"spending hours giting gud at Haskell doesn't translate to hours saved solving real problems" As long as we're playing "make baseless assertions at each other", my experience says otherwise. That's going to be hard for you to talk me out of. Programmers still seem to have this bizarre belief that programming, uniquely among all the skills in the world, is not possible to improve via deliberative practice, and an equally bizarre belief that improved skills can't possible translate into better programs or even worse, must inevitably translate into worse programs. I can't wrap my mind around it. I don't deny that there certainly is a trap where you learn these skills in a sort of greenhouse environment, then fail to translate them out of that environment properly. But that's the fault of the practitioner, not the skills, and I prove by demonstration that the skills can come out of the greenhouse and improve real code. I mostly write my professional code in Go, so you can be quite assured my production code is anything but a mess of functional paradigms inappropriately applied, since that's basically impossible in Go. I find what I learned in Haskell to be incredibly useful in Go.
- ajross 8y agoI genuinely don't think you read the linked article. The author clearly is quite good at Haskell and hasn't fallen into this "trap" you're positing. It's not a failure of the "practitioner" at all. It's a fairly insightful point about the psychology of programming and the diminishing returns of the kind of skills we're talking about here. > you can be quite assured my production code is anything but a mess of functional paradigms inappropriately applied The point of the article was precisely that functional paradigms appropriately (which is to say, "appropriately") applied are themselves a design smell.