Logo of shite

shite

shite's job is to help me make my website (https://evalapply.org). Thus, shite's scope, (mis)feature set, polish will always be production-grade, where production is 'works on my machine(s)' :)

github.com/adityaathalye/shitewww.evalapply.org/posts/shite-the-static-sites-from-shell-part-1/
Logo of Clojure 'Multiproject'

Clojure 'Multiproject'

See the 'Concept' section in the README. Basically, 'multiproject' addresses my own specific requirements; viz. indie and hobby SaaS apps of my own; RAD for outcomes-driven customers (like me) who want long-lived, stable software; and to benefit from the Clojure ecosystem's creativity, reach, stewardship, and software stability. Polylith (https://polylith.gitbook.io/) is the (far) more sophisticated alternative to my approach.

github.com/adityaathalye/clojure-multiproject-example/www.evalapply.org/tags/web_development/
Logo of Clojure By Example

Clojure By Example

This workshop aims to get your brain and fingers accustomed to just enough of the Clojure programming language to start doing useful things with it. In other words, 'What could one do with just a little bit of Clojure?'.

github.com/adityaathalye/clojure-by-examplewww.evalapply.org/tags/clojure
Logo of usermanager-first-principles

usermanager-first-principles

Sean's original 'User Manager' example project and its variants (including this one), aim to demystify 'How to construct a Clojure web application using only libraries?'. 'Composition over inheritance', 'Libraries over frameworks', and 'Data orientation' feature prominently in the Clojure world's canonical mental model of programming, including programming the web. Absent some of these key intuitions, even experienced developers who are new to Clojure tend to struggle to build apps using libraries. The 'User Manager' collective of demos aim to address this specific challenge.

github.com/adityaathalye/usermanager-first-principleswww.evalapply.org/posts/clojure-web-app-from-scratch/