Never heard of this before as I mainly use MS stack.<p>However, my first impression is very positive.<p>1. Database First<p>Great way to distinguish your product from traditional ORMs. I am personally not a fan of code first approach especially as a LOB applications developer. I have been writing code for 15 years and the database&#x2F;schema has outlived each and every application that I wrote. (I am in full agreement with lukaseder&#x27;s comment: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=10880942" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=10880942</a>) As an experienced developer, they immediately made their value proposition clear to me and I wanted to learn more.<p>2. Examples<p>Side by side example comparing jOOQ to SQL. A great way for me to quickly see if I like their DSL design.<p>3. Convince your manager page.<p>I absolutely loved this: <a href="http:&#x2F;&#x2F;www.jooq.org&#x2F;why-jOOQ.pdf" rel="nofollow">http:&#x2F;&#x2F;www.jooq.org&#x2F;why-jOOQ.pdf</a><p>We all have worked with &#x27;a technical manager&#x27; who isn&#x27;t really technical. When you need to purchase a tool, you need to convince your manager and this page is as good as I have seen. All commercial software development tool product websites should feature a &#x27;Convince your manager&#x27; page.