Clojure lets you focus on solving real problems (as opposed to the language's problems), and this yields unique long-term benefits. I've written about them in this article and have highlighted a dozen Clojure companies that are hiring and will train you:
https://t.co/dcbWr2M9ht
I wrote a thing!
From Tables to Graphs: How to Model Entities in a Graph Database
"graph dbs use a different paradigm for modeling data than you're used to with relational dbs. This guide will lead you from the relational world to the graph world..." https://t.co/hk85MXX05W
Today @FlureePBC is launching their public preview of Fluree, a JSON-LD database. I worked with them to create excellent docs explaining RDF/graph data and how they "future-proof" your data. Check out https://t.co/hk85MXX05W to learn a new way to think about data systems 😊
Just published a new blog post: An Interactive Intro to CRDTs! It's the tangible, code-based introduction I always wanted, plus a bunch of interactive visualizations to help build an intuition for how CRDTs work. https://t.co/x0o0DJxDX1
new experiment! this lets you define a “virtual service” in a library that a client can provide a handler for. immediate use case is to make it possible to have a library interact with a data store when you don’t know what data store the client is using https://t.co/SVxa9m5oaW
Another experiment: hooked, a library that introduces an extensibility mechanism for optional side effects. It aids in creating libraries that encapsulate both a workflow, and side effects to perform at specified points in the workflow.
https://t.co/IGiN1UuTw3
Writing a programming major mode is much easier now that you don't have to write an intricate web of regexp and code to power the font lock and indentation engine in #Emacs.
Here's how to write a #treesitter powered major mode
https://t.co/GxcVkZaExN
SISYPHUS: what’s up guys today we’re making another attempt at getting boulder to 100% of summit. My current record is 98% but I’ve come up with a new strategy that might get us–Wow, magnes just donated 50 free subs, can we get some laurels in the chat for magnes
The fantasy of an easily categorized world is seductive in the face of fear of the future, but do not be fooled by snake oil salesmen into missing that its complexity is the font of its beauty. The world will always surprise you.
Babashka Babooka: Write Command Line Clojure
https://t.co/wDOrIZ3BWt
Babashka is a Clojure scripting runtime created by @borkdude, and this guide will show you how to get productive with it!
Includes links to free PDF and epub downloads
Enjoy! 🎉
The most annoying people in the world love to say there is no objective difference between good code and bad code
So I made a list of 15
Good Code v/s Bad Code: The Masterlist of 15 Differences
“In Finland, the # of homeless people has fallen sharply. Those affected receive a small apartment & counselling with no preconditions. 4 out of 5 people affected make their way back into a stable life. And all this is CHEAPER than accepting homelessness.” https://t.co/EH3reri9lz
@amithgeorge@NPException Yeah that's where I started too, wanting to very explicitly only allow two options. I don't know, maybe I'll just move back to that; constraints can often be your friends
Alright I think graphputer is ready for prime time 😎 I've updated the syntax a little so you can validate the values you're puting, and I've released it to Clojars: https://t.co/Wje1zOV3Wu
@amithgeorge@NPException suggested nodes could handle multiple branches, and I think it's useful to support that. Plus I like having a goto keyword :P I think [::puter/goto :fail] is a little more explicit and I think that makes it clearer