Clojurians Log v2

For anyone still using org.clojure/java.jdbc, I just released 0.7.12 to Maven Central. The only difference from 0.7.11 is that most of the protocols are now extensible via metadata making it easier to work with a wider variety of data types (just like in next.jdbc). Follow-up in #sql

enjoyed checking out both, particularly type-infer :) wrt power-dot, merely as a musing: I don't find the reify examples so bad - they're concise enough and transparently reflection-free. The main problem is probably discovery, e.g. it's hard/tedious to know in advance that .. (IntStream/range ...) can be auto-completed to filter, and that similarly, filter can be auto-completed to IntPredicate. It seems plausible to me to conceive this as a problem that could be solved in https://github.com/alexander-yakushev/compliment (the lib that powers the auto-completion of CIDER et al). Basically teaching it to understand functional interfaces + to emit completions that are more substantial than a single symbol (e.g. emit a whole (reify ...) as a completion)

Thanks. Basically because SNOMED is an ontology we can use the relationships (triples basically) to infer that, for example, you have a type of neurological disease if I know you have Parkinson’s disease. But it isn’t limited to diagnostics but lots of different domains including occupations, countries, procedures, drugs etc. See https://www.snomed.org/snomed-ct/five-step-briefing I use in an EPR.

My dear Clojure friends, Developing in Clojure over the last 9 year taught me so many powerful general insights about programming. I am writing a book called “Data-Oriented programming” in which I am attempting to share part of those insights with the global developer community. The https://www.manning.com/books/data-oriented-programming?utm_source=viebel&utm_medium=affiliate&utm_campaign=book_sharvit2_data_1_29_21&a_aid=viebel&a_bid=d5b546b7 is available in early stage at http://manning.com. Here is a 50% off discount code: mlsharvit2.

I recognize plantuml diagrams ! Good choice

Hehe! Being able to have “source code” for diagrams motivates me to create lots of diagrams. I don’t have to bother my mind with the look and feel of the diagram. I focus on the “logic” of the diagram. Also, I have the ability to refactor diagrams across the whole project (e.g. fixing a typo or changing the case of a term…)

I love that you posted this, because earlier today I had posted a link to the book on our company’s internal Clojure Slack channel saying “This looks like a book about how to program as if you were using Clojure”! 😀

A use case I love also, being able to generate diagrams.