Skip to content
Tech News
← Back to articles

Anecdotally, Programmers Dislike "Reduce"

read original more articles
Why This Matters

This is a lightweight, anecdotal observation about programmer preferences among functional array methods, noting that 'reduce' tends to draw more code review pushback than 'map' or 'filter'. While not a hard data-driven finding, it touches on real concerns in software engineering around code readability, maintainability, and team conventions that affect day-to-day developer productivity.

Key Takeaways

Anecdotally, programmers dislike "reduce"

In short: from my experience, people like map and filter , but not reduce .

I use functions like map and filter all the time. When I put that code up for review, my peers rarely complain. I get plenty of feedback about other decisions, but not about my use of map and filter .

I cannot say the same for reduce . Often, when I’ve submitted a patch with reduce inside, I get a comment like, “this part is hard to read.” And I see reduce way less than map , filter , some , and so on.

Anecdotally, I have come to believe that programmers don’t like reduce as much.

I don’t know why, but I have a few theories:

reduce is harder to read.

is harder to read. reduce is less familiar.

is less familiar. reduce can have worse performance compared to other options.

can have worse performance compared to other options. reduce is less elegant in languages I use, like JavaScript, Python, and Swift. In my blissful stint as a Clojure developer, I did not get this feedback.

... continue reading