clojure

Side effects as data

One thing Ive noticed about programming in clojure is that usually there is a separation of functions that return data and functions that use that data to perform what are usually called side effects. By that I mean operations that when performed may have a different output even when given the same exact input.

Read
clojurescript

Snap

Dealing with restful APIs from a react based web app can be very ad hoc and informal.

Read
clojure

Full stack clojure

Full stack clojure, started from the server now we're here.

Read
clojure

Essential clojure dev tools

It's 2016, not 1958, the tools for writing lisp (clojure) have evolved. No one balances or even sees parens anymore. Here are the essential tools you should be using to write clojure and clojurescript code.

Read
clojure

Clojure, SQL and You

Data access made simple

Read
clojure

Things Clojure Makes Simple

There's quite a few things that clojure makes simpler. Some high level ones are: - syntax (or lack thereof) - composition - async - immutability But there are tons more!

Read
clojure

Why clojure why now?

Clojure is slow to start, it's not the fastest once it gets going either. It runs on the JVM and has interop with java which is my least favorite language. The stack traces are terrible, bugs are easy to create and large refactoring is difficult without a lot of well written, well thought out tests.

Read
life

2015 Year in Review

2015 was kind of a crazy year for me, I mean I didn't jump out of a plane like I did in 2013, or get married in Hawaii like I did in 2014, it was crazy for different reasons.

Read