bureaucracy
A segment of the enormous file
As office buildings grew taller, and flammability became a problem, steel file cabinets replaced wooden ones – the tall cabinets mimicking the shape of the skyscraper, such that the “file” seemed to be a metaphorical stand-in for the office itself. “Each office within the skyscraper,” C. Wright Mills would argue some years later, “is a segment of the enormous file, a part of the symbolic factory that produces the billion slips of paper that gear modern society into its daily shape.” Aldous Huxley, in his dystopian novel Brave New World, could imagine no more powerful symbol of a totally bureaucratized world than the idea of each person having his or her name on a file.
Each fascinating crisis
The problems themselves, though they once obsessed you, and kept you working late night after night, and made you talk in your sleep, turn out to have been hollow: two weeks after your last day they already have contracted into inert pellets one-fiftieth of their former size; you find yourself unable to recreate the sense of what was really at stake, for it seems to have been the Hungarian 5/2 rhythm of the lived workweek alone that kept each fascinating crisis inflated to its full interdepartmental complexity.
An enormous machine
The couple of years in question here saw one of the largest bureaucracies anywhere undergo a convulsion in which it tried to reconceive itself as a non- or even anti-bureaucracy, which at first might sound like nothing more than an amusing bit of bureaucratic folly. In fact, it was frightening; it was a little like watching an enormous machine come to consciousness and start trying to think and feel like a real human.
Unborable
The underlying bureaucratic key is the ability to deal with boredom. To function effectively in an environment that precludes everything vital and human. To breathe, so to speak, without air.
The key is the ability, whether innate or conditioned, to find the other side of the rote, the picayune, the meaningless, the repetitive, the pointlessly complex. To be, in a word, unborable. I met, in the years 1984 and '85, two such men.
It is the key to modern life. If you are immune to boredom, there is literally nothing you cannot accomplish.
Institutional structure
'That was all he said it seemed like I needed, just to talk to somebody with no bullshit, which was what the Zeller Center doctors didn't realize, or like they couldn't realize it because then the whole structure would come down, that here the doctors had spent four million years in medical school and residency and the insurance companies were paying all this money for diagnosis and OT and therapy protocols, it was all an institutional structure, and once things became institutionalized then it all became this artificial, like, organism and started trying to survive and serve its own needs just like a person, only it wasn't a person, it was the opposite of a person, because there was nothing inside it except the will to survive and grow as an institution.'
The Pale King
A Novel by David Foster WallaceCubed
A Book by Nikil SavalDeadlines are bullshit
An ArticleIn software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil.
- External vs. internal deadlines
- Why are internal deadlines evil?
- Engineers who love their work
Big company tale: six months for a list and a button
An ArticleWhenever you wonder what it's like at a big company... sometimes, it's like this! And, hey, sometimes it's even worse!
In defense of disorder: on career, creativity, and professionalism
An Essay by Chia AmisolaProfessionalism is a lie, build what you love, explore everything. In today’s age of creation, anyone who attempts to tell you otherwise is lying. You’ll end up seeking what you traded for the rest of your life.
Dolor
A Poem by Theodore RoethkeI have known the inexorable sadness of pencils.
The small web is beautiful
I believe that small websites are compelling aesthetically, but are also important to help us resist selling our souls to large tech companies. In this essay I present a vision for the “small web” as well as the small software and architectures that power it.
Why aim small?
Why aim small in this era of fast computers with plenty of RAM? A number of reasons, but the ones that are most important to me are:
- Fewer moving parts. It’s easier to create more robust systems and to fix things when they do go wrong.
- Small software is faster. Fewer bits to download and clog your computer’s memory.
- Reduced power consumption. This is important on a “save the planet” scale, but also on the very local scale of increasing the battery life of your phone and laptop.
- The light, frugal aesthetic. That’s personal, I know, but as you’ll see, I’m not alone.
Features and complexity
Niklaus Wirth of Pascal fame wrote a famous paper in 1995 called A Plea for Lean Software. His take is that “a primary cause for the complexity is that software vendors uncritically adopt almost any feature that users want”, and “when a system’s power is measured by the number of its features, quantity becomes more important than quality”.
Solving the problem of software bloat
But instead of just complaining, how do we actually solve this problem? Concretely, I think we need to start doing the following:
- Care about size: this sounds obvious, but things only change when people think they’re important.
- Measure: both your executable’s size, and your program’s memory usage. You may want to measure over time, and make it a blocking issue if the measurements grow more than x% in a release. Or you could hold a memory-reduction sprint every so often.
- Language: choose a language that has a chance.
- Remove: cut down your feature set. Aim for a small number of high-quality features. My car can’t fly or float, and that’s okay – it drives well.
- Say no to new features: unless they really fit your philosophy, or add more than they cost over the lifetime of your project.
- Dependencies: understand the size and complexity of each dependency you pull in. Use only built-in libraries if you can.
Raw size isn't enough
A few months ago there was a sequence of posts to Hacker News about various “clubs” you could post your small website on: the 1MB Club, 512KB Club, 250KB Club, and even the 10KB Club. I think those are a fun indicator of renewed interested in minimalism, but I will say that raw size isn’t enough – a 2KB site with no real content isn’t much good, and a page with 512KB of very slow JavaScript is worse than a snappy site with 4MB of well-chosen images.
...[Instead, it's about] an “ethos of small”. It’s caring about the users of your site: that your pages download fast, are easy to read, have interesting content, and don’t load scads of JavaScript for Google or Facebook’s trackers.