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 Fidelity Curve
How do we choose which level of fidelity is appropriate for a project?
I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing.
I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing.
Four levels of fidelity
Suppose we have four levels of fidelity…
- Rough sketch (on paper or an iPad)
- Static mock-up (eg. Photoshop or Sketch)
- Interactive mock-up (eg. Framer, InVision)
- Working code prototype (HTML/CSS, iOS views)
Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained
Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it.
Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.