The Aesthetics of Code
We can describe code that works. We struggle to describe code that's good. This is an attempt at the difference.
mport InlineCallout from '../../components/InlineCallout.astro'; import InlineCalloutCluster from '../../components/InlineCalloutCluster.astro';
Something Feels Off
It was a class name. Part of a component I'd built a few weeks back. It worked, it was in production, nobody had looked at it twice. But every time I opened that file for something else, I'd hover over it for a second longer than I needed to. .wrapper-inner-content. Not wrong. Just…not quite there. Like a word you use in conversation because you can't find the right one fast enough.
I renamed it on a Tuesday morning before I'd properly started the day. Took about four minutes including the find-and-replace. Closed the file, made a cup of tea.
I stopped thinking about it. Which means I'd been thinking about it the whole time.
Did you enjoy this article?
Recommend it — Standard Reader surfaces well-loved writing to more readers across the network.