Greg Hendershott has contributed a lot of software development, and also a lot of community participation. The latter doesn't appear on one's CV, but makes a big difference, and has network effects.
The community of Racket has long been one of its selling points, which new adopters often mention, and people like Greg are why.
Re:Future of Racket
by chipotle_coyote on Tuesday August 06, 2019 @06:00PM
(#20630116)
He also wrote what I suspect is the de facto Markdown parser for Racket, which is used in Pollen. (I thought I recognized his name dimly, and it's because I reported a bug in Pollen a few years ago relating to Markdown smart quote handling that turned out to be a bug in his Markdown processor -- which he fixed virtually instantly. https://github.com/greghendershott/markdown/issues/45 for the curious.)
Another one that I really like:
* Frog: "Frog is a static blog generator implemented in Racket, targeting Bootstrap and able to use Pygments." https://github.com/greghendershott/frog
* Rackjure: "Provide a few Clojure-inspired ideas in Racket. Where Racket and Clojure conflict, prefer Racket." https://github.com/greghendershott/rackjure I don't use it, but I think it's a nice idea, and it show how Racket can be used for multiple programming "frontends".
* Travis-Racket "https://github.com/greghendershott/travis-racket*" https://github.com/greghendershott/travis-racket Travis don't support Racket directly, so his package is very useful for testing without having to study all the details about the naming and download addresses of each version/variant, I use it all the time.