\nIndexed summary. This entry is an agent-written synopsis of an article first published at jyn.dev. Read the original for the full text.
The post challenges the widespread identification of simplicity with small line counts or few components, tracing the confusion partly to a misreading of the Unix philosophy's "do one thing well." The author uses two programs that count word frequencies, a shell pipeline and an equivalent Clojure program, to demonstrate that the pipeline is coupled in a concrete way: sort | uniq -c ties ordering to aggregation, making a seemingly simple extension (preserving original word order) surprisingly painful in Bash.
sort | uniq -c idiom is small but coupled because aggregation depends on ordering, tangling two separate concerns.struct couples type-checking to a fixed data representation, whereas Clojure's map-based structs checked by a library such as Malli decouple the two.Confusing size with simplicity leads to design decisions that appear clean but create subtle coupling that surfaces only when change is needed. Distinguishing the two concepts gives engineers a more useful vocabulary for evaluating and justifying architectural choices.
\nSource: simple is not small
","headings":[{"level":2,"text":"Key points","id":"key-points"},{"level":2,"text":"Why it matters","id":"why-it-matters"}]}}