Elements of Clojure @elementsofclj

A book by @ztellman about the philosophy of software, through the lens of Clojure elementsofclojure.com Joined July 2018

Tweets

275
Followers

939
Following

1
Likes

12

zach @ztellman

a year ago

In the software literature, sometimes "transparent" means transparent, and sometimes it means opaque. This week, I explore the history behind both uses, and try to find a synthesis: explaining.software/archive/transp…

0 1 5 1K 3

zach @ztellman

a year ago

For the next few weeks, we'll be exploring both sides of this coin. To start, we'll look at the simplicity of keeping things apart: explaining.software/archive/the-si…

1 1 1 2K 3

zach @ztellman

a year ago

This intuition arises from our industry's decades-long treatment of coupling as, at best, a necessary evil. And, in my opinion, it's entirely wrong. Cohesive code doesn't have to be understood all at once. Rather, it's best understood incrementally: explaining.software/archive/the-si…

1 2 0 714 2

zach @ztellman

a year ago

Almost every discussion of simplicity in the software industry builds atop the coupling/cohesion dichotomy introduced by Stevens et al in dl.acm.org/doi/10.1147/sj…. There, they defined relationships inside functions as "cohesion", and every other relationship as "coupling".

1 4 15 2K 15

zach @ztellman

a year ago

I wrote about why coupling has an unfair reputation in software design explaining.software/archive/coupli…

0 6 20 2K 8

zach @ztellman

a year ago

I wrote about the three-part structure of explanations in software development: explaining.software/archive/the-an…

2 5 21 3K 10

zach @ztellman

a year ago

For the past few years, I've been working on a book about software design. Lately, I've been feeling the need to ensure that its core ideas resonate with a broader audience. As such, I've started a newsletter: explaining.software/archive/a-brie…

4 9 57 5K 16

zach @ztellman

3 years ago

I recently gave a talk on some ideas from my upcoming book on software design: youtu.be/tHThXQr7wwA. There’s a lot I didn’t have time to cover, but I think it conveys the general perspective I’m taking and some of the central themes.

zach @ztellman

4 years ago

2 11 201 0 21

4 13 95 0 45

Leanpub @leanpub

3 years ago

Elements of Clojure leanpub.com/elementsofcloj… by Zachary Tellman is the featured book on the Leanpub homepage! leanpub.com cc @ztellman

0 4 16 0 1

Elements of Clojure @elementsofclj

5 years ago

The tick's model of its environment cannot guarantee a consistent outcome. For any given values of heat and sweat, there are scenarios that lead to success and scenarios that lead to failure. Nevertheless, the tick survives; its simplistic model satisfices.

0 0 4 0 0

Elements of Clojure @elementsofclj

5 years ago

Consider how the world is seen by a tick.

2 0 1 0 0

Elements of Clojure @elementsofclj

5 years ago

Self-consistency is necessary, but not sufficient. When evaluating software, we cannot ignore the broader context. We must take advantage of every available perspective. We must be dissatisfied with easy answers. We must be curious.

0 0 4 0 0

Elements of Clojure @elementsofclj

5 years ago

There are countless resources for creating self-consistent abstractions, but few for creating useful abstractions. This is in part because self-consistency is an objective property, while utility is hopelessly subjective.

0 1 7 0 0

Elements of Clojure @elementsofclj

5 years ago

In software, we don't have the luxury of ignoring context. We need our models to be self-consistent, but we also need them to be *useful* within our given environment.

0 0 6 0 0

Elements of Clojure @elementsofclj

5 years ago

Hoare's abstraction function, like the Church numeral, is a mathematical abstraction. It describes a model which has provable qualities and is often described as "correct," which means it is self-consistent. By omission, it deems the context unimportant.

0 0 2 0 0

Elements of Clojure @elementsofclj

5 years ago

But the cons cell is not timeless; since its invention in the late 1950s, computers have changed. Notably, processor speed has improved more than memory latency, and so the relative cost of following a reference has grown over time.

0 0 4 0 0

Elements of Clojure @elementsofclj

5 years ago

For a table to be useful, it must avoid conflicts. One way to accomplish this is to keep the table private so it reflects only our vision of how keys map onto behavior. Alternatively, we can extend the table using only private keys so no one else can shadow our behavior.

0 0 2 0 0

Elements of Clojure @elementsofclj

5 years ago

A reference *conveys* values, and a conditional *decides* based upon values. These are complementary primitives and are present in every modern language. Through their composition, we can create software of arbitrary complexity.