Clojure - Thriving in the dynamically type-checked hell scape of Clojure

The article "Thriving in the dynamically type-checked hell scape of Clojure" discusses the author's experience with Clojure, a dynamically typed programming language. The author addresses the common question of how to write code without types and explains that the nuance of strong and weak typing, as well as static vs dynamic type checking, is often lost on people.

The author attributes their cognitive model of writing code to their early experiences with programming in C and using tools like GCC and GEdit. They admit to having a "bad" habit of using GEdit and the command line, which followed them into their university studies and their first job as a Clojure developer. They mention the preference for using Emacs prelude + CIDER in the office, but also highlight the challenge of outdated documentation and the need to rely on reading code instead.

The author argues that having less code in the developer's head is better and that dynamic type checking in Clojure can be managed through the use of docstrings and idioms, which are more descriptive than type declarations on function arguments.

Overall, the article provides insight into the author's experience with Clojure and highlights the benefits and challenges of working with a dynamically typed language. Developers interested in Clojure and dynamic type checking may find this article informative and relatable.