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.
A Plea for Lean Software
Software's girth has surpassed its functionality, largely because hardware advances make this possible. The way to streamline software lies in disciplined methodologies and a return to the essentials.
Measured by the number of its features
A primary cause of complexity is that software vendors uncritically adopt almost any feature that users want. Any incompatibility with the original system concept is either ignored or passes unrecognized, which renders the design more complicated and its use more cumbersome. When a system's power is measured by the number of its features, quantity becomes more important than quality. Every new release must offer additional features, even if some don't add functionality.
Essential vs. nice to have
Customers have trouble distinguishing between essential features and those that are just "nice to have." Examples of the latter class: those arbitrarily overlapping windows suggested by the uncritically but widely adopted desktop metaphor; and fancy icons decorating the screen display, such as antique mailboxes and garbage cans that are further enhanced by the visible movement of selected items toward their ultimate destination. These details are cute but not essential, and they have a hidden cost.
/
Increased complexity results in large part from our recent penchant for friendly user interaction. I've already mentioned windows and icons; color, gray-scales, shadows, pop-ups, pictures, and all kinds of gadgets can easily be added.
Dependence is more profitable than education
A customer who pays—in advance—for service contracts is a more stable income source than a customer who has fully mastered a product's use.
Customer dependence is more profitable than customer education.
What I find truly baffling are manuals—hundreds of pages long—that accompany software applications, programming languages, and operating systems. Unmistakably, they signal both a contorted design that lacks clear concepts and an intent to hook customers.
The most rewarding iterations
Initial designs for sophisticated software applications are invariably complicated, even when developed by competent engineers. Truly good solutions emerge after iterative improvements or after redesigns that exploit new insights, and the most rewarding iterations are those that result in program simplifications.
Evolutions of this kind, however, are extremely rare in current software practice—they require time-consuming thought processes that are rarely rewarded. Instead, software inadequacies are typically corrected by quickly conceived additions that invariably result in the well-known bulk.
Never enough time
Time pressure is probably the foremost reason behind the emergence of bulky software. The time pressure that designers endure discourages careful planning. It also discourages improving acceptable solutions; instead, it encourages quickly conceived software additions and corrections. Time pressure gradually corrupts an engineer's standard of quality and perfection. It has a detrimental effect on people as well as products.