# Looking for a technical reviewer

**URL:** <https://discuss.elastic.co/t/looking-for-a-technical-reviewer/88579>\
**Category:** Elasticsearch\
**Created:** [June 7, 2017, 12:22pm UTC](https://discuss.elastic.co/t/looking-for-a-technical-reviewer/88579 "2017-06-07T12:22:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jimbojw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jimbojw/32/18880_2.png) [@jimbojw](https://discuss.elastic.co/u/jimbojw)\
**Post date:** [June 7, 2017, 12:22pm UTC](https://discuss.elastic.co/t/looking-for-a-technical-reviewer/88579/1 "2017-06-07T12:22:19Z")

</div>

Hi Elasticsearchers,

_Sorry if this is not the right venue for this request!_

My soon-to-be-released book, _Node.js 8 the Right Way_[1] features Elasticsearch prominently. Readers learn to create indices and insert documents, then later how to implement Express-based APIs that perform Elasticsearch queries.

I'm looking for a technical reviewer who can vet the content of the book from the Elasticsearch side of things. I want to live up to the title "the Right Way". I wrote the bulk of the book targeting Elasticsearch version 5.2, so it would be especially helpful if you know the ins and outs of 5.4 and beyond.

Thanks in advance!

[1] [https://pragprog.com/book/jwnode2/node-js-8-the-right-way](https://pragprog.com/book/jwnode2/node-js-8-the-right-way)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 12:23pm UTC](https://discuss.elastic.co/t/looking-for-a-technical-reviewer/88579/2 "2017-07-05T12:23:17Z")

</div>

Closed on July 5, 2017, 12:23pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.