[dkarapetyan]

What about type theory weenies? The title is also a little link-baity. The person commenting on his pull request was not being a snob. He was making sure there was architectural coherence across the board. When codebases grow large having an idea of the overall architecture becomes an invaluable resource and the more consistent the codebase the easier it is to make sense of the architecture.

[jeremiep]

Type theory can help you build the proper abstractions to help the codebase grow and scale in a clean and manageable manner. It doesn't matter if you're working in Haskell or JavaScript either; types are still present and affect how well the different parts of the system can be composed together.

[gknoy]

  The person commenting on his pull request was not being a snob. 
  He was making sure there was architectural coherence across the board. 

This is actually the essence of the article. When people criticize things in our code that we see as "trivial", it's EASY to mistakenly ascribe that to snobbery or being a jerk. The entire point of this article is that we should look for the value that our peer is trying to add by pointing out inconsistencies or better ways of doing things.

Some of the best pull request comments for me have been the ones that made me say, "Dammit! .... you're right." Many of those PR comments have been replaced by impersonal linting tests that do the same, but the net result is still that I feel proud of what I write.

[codygman]

> What about type theory weenies?

Are we first graders?