online posts and comments on aesthetics of code

beautiful code according to blogger

link 1 - link 2

he talks about a beautiful patch for a faster clocktime on illumos, a version of BSD. reached out to the author for explanation.

beautiful code exists (acm queue)


he is working on a hadware counter monitor for FreeBSD and explains why this is beautiful code.

C #define PMC_VERSION_MAJOR 0x03 #define PMC_VERSION_MINOR 0x00 #define PMC_VERSION_PATCH 0x00

names are significant, even more so in C/hw-level in which sometimes you have to deal with hex codes. (aesthetic is going against set practices, individual display of skill, for others -> the reader).

a bit later, he separates the variables that are machine-dependent, and variables that are machine-independent. this is the most important and effective categorization/labelling. (this constitutes a part of conceptual distancing)

and a final commentary on using C because drivers are written in C, but still remembering lessons and practices from other languages (i.e. data encapsulation in C++)

stackexchange answer on “what is beautiful code”


these are recommendations on reading Beautiful Code, Literate Programming.

hamon: beautiful code and japanese swordmaking


the author states that ugliness is self-explanatory, but that beauty is elusive (they still don’t define ugliness).

his main arugment is that of hamon, the wavy pattern on the edge of a japanese blade which indicates its quality. they see the same thing with code, there’s a pattern that’s an indicator of its quality.

this introduces the possibility of different scales at which we read code. a glance, a deep-dive, a spelunking. and also different timings (glancing first, then reading)

literate programming resources (after knuth, lots of snippets from different authors)


a series of excerpts from the knuth fan club. one interesting point is that Lit Programming is a paradigm, a sort of meta-text that goes on top. it’s a target. but is it still source code? does it qualify as a craft, or does it just move the craft to another layer, that of writing TeX docs? (which is def a fucking craft). however, while LP highlights the human reader more than the machine reader, i’d argue that the way that humans read source code is different from the way humans read books, and that there are techniques in source code which help understand the code better (conceptual distances, metaphors, separating concerns), and that those are poorly represented in LP. in fact, LP is efficient, but not elegant on the aesthetic level; because it abstracts the details, some of the beauty is lost.

stackexchange answer on explaining beautiful code ot non-programmers


(answers are listed by decreasing upvotes)

David Thornley: the one that uses the simpler and fewer ideas whilst doing the job correctly.

user21007: makes an analogy with architecture, but without going beyond “[…] And it is aesthetically pleasing”

Steven Evers: “All of the code is present, is required, and none of it requires explanation” (ideal goal? any code requires explanation, though.)

Mason Wheeler: “When it requires a lot of explanation like that, it’s not “beautiful code” it’s a “clever hack”.

asoundmove: adds “it must also subjectively feel perfect & light”

user21007 (as above): adds that if it’s self-explanatory, it must also be non-trivial. and it must take into account that it is maintainable, and in the right language. given that, hello, world!, couldn’t be called beautiful.

Macneil: “coding problems are about conceptualization, so beautiful code represents a remarkable conceptualization of the problem”, and a beautiful execution. (programming really is just the craft of ideas). “for instance, when a problem can be reduced to an existing problem, it gives us an insight into the nature of the problem itself.” (and elegance uses simple trucks to achieve difficult tasks). he concludes with quicksort.

dsmicha: beautiful code can’t be attained because it implies conflicting interests. is it then about balance and compromise?

Chris Cudmore: compares beautiful code to beautiful math proofs.

tp1: talks about behaviour than actual writing

guidhouse: states they’re a craftsman

paul d. waite: it’s beautiful when it’s readable.

fortran: you should be able to read it like a book. page after page, without skipping ahead or skipping back to understand the current page.

Erik Reppen: compares it to efficient vs. sloppy bureaucracy

quora question on “what makes beautiful code” (cf. WR archive for more)


Pierre Chapuis: states that it is simplicity, and quotes David Gelernter—”Beauty is more important in computing than anywhere else in technology because software is so complicated. Beauty is the ultimate defence against complexity.”—as the CS who thought most about the beauty of code.

David Seidman: makes a difference between simple (organization) and simply written (naming, structures, etc.), then lists the usual suspects, and then adds does something interesting (aka a login page couldn’t be nice). i’m not sure about login pages not being nice, but it says something about ingenuity, craftsmanship.

Brian Schmitz: the python one-liner that makes use of decorators.

python @lru_cache(3) def fib(n): return n if n < 2 else fib(n - 1) + fib(n - 2)

after a lengthy, technical explainer, he concludes in saying that “the beauty here is the power of a single line of code” (emphasis my own)

Christian Baune: gives thorough code examples, demonstrating that naive approaches can be the most optimal. in the end, beautiful code is:

Bill C. Reimers: makes the point that what is considered beautiful depends on the data context (adding 10 positive ints, vs. adding all ints between -10^38 to 10^38). his point is that “When you come up with code that is both simple and accurately computes the results, then you have something beautiful.”, followed by the conclusion that, depending on the usage, it’s about divide and conquer

Lucas Wiman: difference between two attemps of solving sudoku (norvig vs. ron jeffries). the first one displays a keen understanding of both the problem and the tools. referenced here

Alexey Spizhevoy: the balance between easiness (to read, maintain) and smart ideas, originality. he refers to Zen and The Art of Motorcycle Maintenance (craft)

John Rainey: quoting his college prof, “elegant code provides the simplest soolution to a problem”

Mario Hines: gives an example, but doesn’t say why.

Anders Borg: code symmetry, using the same constructs for the same tasks. make for easier to understand code, and it looks better too (sic)

Hitesh Sajnani: thinks code isn’t beautiful, the architecture is. if you have a shit architecture, you can’t have beautiful code.

Mark Roberts: it’s not about the what that the comments describe, but the why that they describe (business requirements, problem domain). indeed, for the first case, correct names can take care of the what comments.

Cornel Masson: “fluid interfaces that make it read like natural languages”

Nabarun Mondal: gives an example of beautiful code, but prefaces it with “Oh, and if you understand predicate logic, this is cake walk.”, which touches directly upon issues of understanding and requirements.

James Liu (here): code that everyone can appreciate (i.e. read), disregarding their level of expertise

Peat Bakke: beautiful code enlightens the person reading it. “when you read a bit of code that makes you go “ah hah!” … That is beautiful code.”

data scientist on general description of beautiful source code


“beauty is conferred by simplicity and architectural coherence, which go hand in hand with functional precision and creativity applied to the problem”. simplicity, because there is a (at-least) linear relationship between number of lines of code and amount to be understood. but even that isn’t certain (cf. one liners). rather, it is the amount of tokens that need to be reduced (semantic elements).

no two people will write exactly the same code: voice of the programmers.

quote of knuth to explore further: “computer programming is an art, because it applies accumulated knowledge to the world”

“The visual appearance of well-formatted code is strongly associated with its quality and many programmers who take pride in their work, derive great satisfaction from polishing it, as they realise that a programmer is remembered for their style and discipline and very rarely for the code itself.”

he calls small enough functions “pure” functions

IT manager on general description of beautiful source code


follows bob marting (Clean Code) a lot. following this idea of software craftsmanship, describes two components necessary to it: knowledge (heuristics, patterns, principles) and work (the emobided component). it’s all about practice.

the name of a variable/function should answer: why it exists, what it does, and how it is used. this requires descriptive/syntactical skills but also a shared cultural background.

“master programmers think of functions as stories to be told rather than code to be written”

cleanly formatted code is a matter of presentation, of communication, of reputation

15 ways to make code more beautiful from devops perspective


addresses code clarity as the goal.

```C void SomeMethod(){ if(x != y){ //– stuff } }

void SomeClearerMethod(){ if(x == y) return;

//-- do stuff } ```

what makes code readable


there are standard answers (usual suspects), but he puts the emphasis on “background experience levels”. the experienced programmer bypasses syntax for semantics, while the beginner programmer focuses on syntax. (here: goodman). the essential example is the ternary operator.

also states that the languages constrain your means of expression (they have an upper-limit, but is that upper-limit)

“What we really need to focus on now is programming languages with small vocabularies that can be easily understood and learned, even though they might not be as expressive as more complicated languages.” -> processing language


informatimago: prog languages are different in that you are constantly redefining the language.

tz1: variable name length should also hint at the importance (hierarchy) of the variable

Spudley: actually, breaking down into smaller functions doesn’t make it more readable, but it makes it more re-usable. there’s a difference between reading to understand, and understanding to act.

rph: Also I don’t agree that large grammars are worth their expressiveness. Firstly, I think languages, like C, with small grammars can still be sufficiently expressive. Sometimes, a large grammar doesn’t really give you the ability to express more types of things. It gives you the ability to express the same thing in multiple ways. I like to contrast Perl and Python in this respect. I can’t stand reading other’s Perl code because it usually uses a style I’m not accustomed to. Python is just as expressive but there’s usually an obvious way to express an algorithm, making it universal, Languages like, C++, with large grammars, are extremely hard to read and it has contributed to developer’s all adopting their own styles, much like natural languages have different dialects and lingoes. How do programming teams solve this problem? They adopt coding guidelines that restrict the developers to a subset of the language’s grammar.

Tamas Rev (related to above): lower level languages express more in terms of computers, and higer level languages express more in terms of humans.

review of Beautiful Code


(justly) complaining about lack of beauty and familiarity in most of the authors examples, and compares it to explaining poetry in a foreign language. he then goes on to say that what matters is the architecture, the design of the code (in sennett’s terms, still separating the hand from the head)

“focusing on the code is like focusing on the brushstrokes, pigments of the mona lisa”. but i think the discourses around the mona lisa are already established, and already reveal things about our humanity. it is the discourses around the making of the mona lisa that need to catch up.

justinC: highlight that (3…6).each { |num| puts num } is elegant

Jheriko: *dst = *src; while(++*dst = ++*src); is ugly

style is substance, by ken arnold (selected by joel spolsky for his book)


about the strict, compiler-level enforcment of coding styles (number of spaces, etc.). he seems excited by the prospect of no more style wars, but to what extent is the “style war” an essential part of the practice?

implied: whitespaces do matter (cause that’s what a lot of styles are about amyways, and whitespaces make things clearer or more confusing, especially in FORTRAN, cause it has columns-as-whitespace)


a manifesto of sorts, tying even further the idea of craftmanship

account of a software rewrite


with anecdote about MS source code: the expletives in the MS source code, that attest to the very reality of making something in groups.

does beautiful code matter? medium post wit sc examples


definition of beauty: that which pleases the senses, but which pleases the beholder’s senses. then he immediately acknowledges that comprehension is first and foremost (both a priori and a posteriori).

in any case, beautiful code will be readable.

like playing an instrument, there is personality and soul in coding.

so, professionally, where does commercial responsibility end, and artistic license begin?

medium post as lit review of code complete


how do you define good code? maintainability, efficiency, elegance (simple, proper use of language constructs)

the holy grail of self-documenting code!

quotes this post from microsoft on what good code is.

“Elegance combines simplicity, efficiency, and brilliance, and produces a feeling of pride. Elegance is when you replace a procedure with a table, or realize that you can use recursion—which is almost always elegant”

and then he gives the example of fibonacci, so i’d need to investigate if fibonacci is elegant on its own, or if it’s a playground for elegance.

Clarity of code. Clarity of design. Clarity of purpose. (related to the differrent scales of appreciation)

and, sure, you can do clever hacks, but they need to be clever to be justified.

but really, good code is balance.

python code style


because python is praised for readability, it has (needs?) idioms, and they’re all illustrated with code:

overview of clean code (the book)


the rails doctrine, with best practices and paradigms and beautiful code


programmer happiness above all else… “doing programming because I fell in love with it as a mode of intellectual exercise and expression”

convention over configuration

ruby/rails looks like domain-specific language (like it’s speaking the language of the problem)

subtlety, flow and focus in: if people.include? person vs. if people

expressing ideas, what we want to say is as close to the truth as possible.

EXPLICITNESS is valuable

same thing but for python (PEP8) style guide


use blank lines sparingly inside function definitions to show clear steps (like the “decisive moment”)

learning and finding out the beauty of cobol


the beauty of doom’s source code


more detailed version


princeton’s guide to writing clear code


freecodecamp opinion on writing comments in code


review of “beautiful code”


testimony on why someone loves to code (re: psychology of programming)


clean code in angular


best comments in source code from stackoverflow


interview with one of the authors included in beautiful code


personal account of coding


javascript specific clean code


summary of clean code


personal take on the aesthetics of code


stackoverflow: do you care about the aesthetics of your code?


art of readable code (book), chap. 4


sql aesthetics


interesting personal post on aesthetics, understanding and familiarity in code


medium post on clean code


refactoring and aesthetics


discussion on improving the aesthetics of perl code


perl user-generated style-guide


personal account of beautiful code


“why is it hard to write clean code?”**