6 ms·
Calling a bureaucrat by its name
- lkrubner 3y agoFirst they suggest that most computer programmers are bureaucrats: > Most “software engineers” dealing in protocols, technical debt, the JVM, operations …. are also bureaucrats. Then they complain that Google is probably hiring bureaucrats, instead of real technical people: > Do you think the extra 100,000 people Google hired over the last 5 years are actual engineers, or any kind of innovator? I’m willing to bet they’re all bureaucrats, and any of them would say “I work at a tech company doing tech things” and be indignant at being described as what they are: bureaucrats. Well, if you re-define every job as "bureaucrat" then you automatically get the result that everyone you hire is a bureaucrat. The result is the consequence of how you've defined everything.
- lkrubner 3y agoAlso, this is astonishingly ahistorical: "Bureaucrats are also almost universally reviled for their lack of accountability and the lack of pride in their work. While there certainly have been great men; leaders who were great bureaucrats (Napoleon), they’re mostly seen as mostly a caste of sniveling eunuchs who flee from taking responsibility or attempting to make things better or taking any risks, even when that is in their job description." This is very, very inaccurate. Criticism of bureaucrats starts with the 1960s. While you can find an occasional novel or story that critiqued some aspects of bureaucracy (arguably some of Kafka's work, also maybe Bartleby, the Scrivener, though that is mostly seen as a critique of alienation, rather than bureaucracy per se) the rise of the "bureaucracy sucks" as a genre can be dated to the 1960s. Others often make this point, but you can really judge the cultural transition by the careers of leading business commentators, such as Peter Drucker. In 1946 he published his study of General Motors, the book Concept of the Corporation. In it, he examined the large bureaucracy at General Motors and celebrated it as the pinnacle of human civilization, the absolute peak of what the last 6,000 years of civilization had all been building up to. Drucker was not alone. In 1958 John Kenneth Galbraith published "The Affluent Society." A part of the book emphasizes the idea that "If we want to accomplish big things then we need big organizations." Once again, the book implies that large bureaucracies represent our success as a civilization, and those bureaucracies are what enabled that success. Starting in the 1960s, there is a tremendous cultural backlash against bureaucracy. We are still living with that backlash today. It is noteworthy that the cultural backlash has not had a real world result nearly as significant as the cultural result: that is, bureaucracies have continued to grow, even as they have faced relentless criticism for 60 years now. In my own consulting work, I've seen multiple promising startups fail because the founders were afraid of "becoming bureaucratic." I've seen other companies survive but never live up to their full potential because the CEO never set out to build a beautiful bureaucracy. My own sense is that the backlash against bureaucracy must come to an end at some point soon, because too much potential is being wasted by the lack of bureaucracy. At some point, business leaders must again commit themselves to building big, ambitious, beautiful bureaucracies, so they can capture the full potential of the organizations they are running.
- pbronez 3y agoConcur. Once an org knows what it’s good at, you need to start optimizing to scale. That means doing things that would have been counterproductive during the early exploratory work.
- briantakita 3y agoThe phenomenon you describe is not constrained to the 60s. It happens during a collapse of the imperial order...usually when "the common folk" no longer experience the benefits of maintaining an imperial buercracy. When the military rebels against the court Eunichs in late Han China...with the French Revolution & the disparity written by Victor Hugo in Les Miserables almost a century later. When Charles Dickens describes the conditions of the poor. When many Hebrews rebelled against Roman authority. Your work is about making companies more successful in this system & I'm sure you are quite effective at your job. However, many are left out with their wealth & agency transferred to these organizations. The innovator creates a tide that rises all boats. That improves the quality of life for society at large. The bureaucrat administers the existing order. Order is a service that saves many lives but can become very expensive to maintain...eventually costing more than it's benefits, or the cost/benefits of an alternate system. Some systems are more effective than others in maintaining an empire or civilization. The feedback of growing antagonistim toward counterproductive beucracies should be an indicator or the health of an empire or society. Sometimes it's better to cut the Gordian knot of complexity & let the innovators reform the system, through buecratic innovations, tech innovations, & social innovations.
- lkrubner 3y ago"It happens during a collapse of the imperial order.....with the French Revolution" That is also ahistorical. In 1789 the court of King Louis XVI of France was struggling to find the money to pay for a bureaucracy of 500 people, but just 5 years later, in 1794, a revolutionary France had a bureaucracy of 5,000 people. The bureaucracy grew by a factor of 10 in just 5 years, thanks to the Revolution, which seized the property of the Church and sold it or taxed it, thus generating revenue that the King could never have dreamed of. The dramatic expansion of the bureaucracy almost allowed the French to catch up with the fast growing bureaucracy of Britain. Likewise, the Communist Revolution in Russia, after 1917, brought in a complex system of committees vastly more convoluted than anything the Tsar could have ever dreamed of. See here for some speculations on this theme: https://demodexio.substack.com/p/is-communism-inevitable https://demodexio.substack.com/p/is-communism-inevitable
- deleted 3y ago[deleted]
- woodruffw 3y agoThere's a weird standard established in this post: you're either a bureaucrat or an "innovator," with the implication being that only innovators do "real" engineering. I don't know of any engineering profession in the real world that adheres to this standard: the gold standard for actual engineering is consistency within operational margins: building the cheapest and strongest bridge that doesn't collapse given the traffic allowed to go over it, airplanes that don't fall out of the sky, software systems that can reproduce their results, &c.
- nxobject 3y agoOn top of that, the implicit assumptions about how to identify a bureaucrat, and the historical claims about what they've accomplish, get a wee bit expansive at the end: > There are widespread popular revolts against the evil bureaucratic pyramids: Milei, yellow vests, the recent Dutch elections, the Trucker revolt in Canada, the Bukele revolution in El Salvador; even Elon buying X and firing 75% of the head count. This will continue to spread as long as the bureaucrat remains unaccountable. Bureaucratic reform is the defining problem of our time. Bureaucrats and their NPC enablers have ruined much of what made Western Civilization worthwhile. They’ve corrupted the scientific process, technological development, subverted governments, ruined health, created conditions of anarcho-tyranny in the cities and have generally wrecked most of what they’ve touched. Their proliferation is slowly strangling everything, just as a proliferation of intestinal parasites will weaken and ultimately kill if unchecked. Parasites have no natural predators. You need some kind of medicine to get rid of them. We can study the work of successful bureaucratic reformers; Lee Kuan Yew, St. Peter Damian, Napoleon, Park Chung Hee, Deng Xiaoping, Putin, Marius, St. Ignatius of Loyola: also the unsuccessful would-be reformers such as Nixon. The most important first step, though, is recognizing the bureaucrat. That being said, it's probably because I don't know what an NPC means in this context. Maybe it's because I'm one myself.
- woodruffw 3y agoI hadn't made it that far. That veers firmly from "stupid chest-puffing about real engineering" to "reactionary dogwhistling." When I search for the author, one of the only other sources I can find for him is bylines in a neo-Nazi-affiliated magazine[1][2]. [1]: https://www.takimag.com/contributor/ScottLocklin/161/ https://www.takimag.com/contributor/ScottLocklin/161/ [2]: https://en.wikipedia.org/wiki/Taki%27s_Magazine https://en.wikipedia.org/wiki/Taki%27s_Magazine
- defrost 3y agoSuch a bizarre world view: Most “software engineers” dealing in protocols, technical debt, the JVM, operations …. are also bureaucrats. Such people are not engineers in any normal definition of the word; they’re dealing with plumbing and protocol and social problems which come about from large groups of people. As an actual Big-E Engineer (of the Civil|Mech|Electrical|Electronic Professional Member type with conferred degree in Engineering) I can state that Engineers are likely greater "bureaucrats" than software engineers. Professional Engineering is almost entirely procedure and paperwork, documenting, ordering, checking specifications, identifying responsibility via chain of evidence, etc. Big Engineering projects (eg: the multi year UK rail transport expansion, the London sewer mega build (both the original and the recent upscaling), etc.) require truly vast amounts of attention to detail to eventually complete. Small engineering projects like building or safely removing bridges are very much the same; the work of an Engineer isn't to weild a spanner or press a plunger after cutting away steel to weaken a structure, it's to make a plan, order the ducks and line all the ducks up, to have a diagram of what steel to cut in what order (for both construction and demolition). And, (and this is quite the thing), to be responsible in the case of resource over runs and|or lives lost. Scott here has quite the romantic view of engineering, for Scott it seems that real engineering is all about single person | small team total control just have at it hacking about. Don't get me wrong here, I love doing that - but that kind of activity is (to steal a quote from the author) not engineering in the normal several decades old definition of the word.
- woodruffw 3y agoLooks like there are two confounding factors for this author: (1) his background is scientific, not engineering in nature, and (2) he appears to run his own consulting firm. In other words: it's unclear to me that he's qualified to make blanket statements about what "real" engineering is; his closest professional qualification is being a consultant with limited long-term responsibilities. I say this as someone who is also a consultant.
- lokar 3y agoIsn’t engineering just another way to say applied science?
- jacobsenscott 3y agoBlowhard is the term that comes to mind.
- theendisney2 3y agoIn my experience we wouldnt need them if we were capable of doing their few simpel tasks. For some absurd reason people would rather argue needlesly. My gut says half can be automated away and the other half needs a strictly defined job description free from any opportunity for freestyling. You could probably hire 2 or 3 extra for a while to hammer out the spec.
- jancsika 3y agoI love how the graphic undermines his argument. All those tentacles have their own intelligence. Any of them could therefore strangle him, even if they are all axed from the head. Maybe we should change the term "red herring" to "de-tentacled octopus head" Edit: changed "dismembered" to "de-tentacled" :)
- BIackSwan 3y agoOPs projects/expertise while they claim to not be a (weird af definition) bureaucrat - “General things I can do for your business: Mathematical and statistical modeling Data architecture Predictive analytics, statistical modeling and machine learning Physics/technology assessment and development Data science team building/recruiting Data reporting engines Technical writing Writing for technical and general audiences Time series databases” No more explanation needed. Do not hire this person.
- briantakita 3y agoIt's interesting to see the negative reactions to this post, which makes me think there is some uncomfortable truth being expressed that hits close to home. I won't be surprised if some buecratically inclined take this to heart & foster buercratic innovation. That being said, I resonate with the post. I have no interest in being a manager nor do i wish to be managed...but am interested in mastery of craft. I noticed there is much complexity lock-in in the tech ecosystem offerings & strive to strip away these complexities to uncover at the heart of the functionality. Tech solopreneurs & small teams still have a profound impact on the ecosystem & are empowered to bring innovation as a tide that rises all boats...to distill the essential functionality & focus on the essential complexity (within my control) to improve our conditions. There's all sort of different people & we have the ability to practice what we love & bring value to others. Edit I'm sure Lachlan will find it amusing that this post was flagged on HN. It does help to have a thick skin in light of critique...especially in the game of innovation. It is difficult to respect someone in a leadership position who cannot handle a critique...just sayin
- Brian_K_White 3y agoIf there are any valid points in the article, the critiques shown here are also valid, and seem all in all to outweigh. Every bad or ultimately invalid ideology or philosophy that appeals to anyone, necessarily has some sort of bits of rationality here & there to hang all their other arguments on to do that appealing. When a conservative or libertarian wants to sell the idea of deregulation, there are legitimate examples of disfunctional regulation to point to. When a neoliberal statist wants to sell the idea of abolishing guns or home schooling or cryptography or anonymous cash, there are legitimate examples of individuals misusing their individual agency to harm others. Those examples are real, and any sane person should agree those specific stories are bad outcomes, but that does not mean they actually support the argument or that the larger argument or philosophy is valid. It's wrong that Bill Maher can't build a shed. That does not mean that therefor the entire concept of building codes, zoning, epa regulations, etc are wrong and life would be on the whole better and saner without them. I think the bits of truth in this article are like that.
- 3y ago
- ks2048 3y agoWhen you never outgrow your Ayn Rand phase, you will see someone working with "protocols" or "the JVM" (weird examples btw) as a bureaucrat or "scoundrel, a useless cog in the machine, a coward, a gold brick, a sower of chaos and a parasite". At least he is studying "successful bureaucratic reformers", like Putin. Okay.
- satisfice 3y agoImpressive opinion density! Have you ever seen so many opinions in an article not having anything to do with the Marvel universe?
- NicholasGruen 3y agoInteresting that the thread cites Austrian economics. I quote Hayek in this piece of mine, and his welcome focus on unsystematic knowledge from the lifeworld. Yet he never took that argument anywhere other than saying "therefore markets are good". Yes in their place, they are, but there is much more in heaven and earth and we've been pretty bad at adapting organisations to respond well to those things. https://clubtroppo.com.au/2011/12/21/designing-better-lives-an-economist%e2%80%99s-appreciation-of-design/ https://clubtroppo.com.au/2011/12/21/designing-better-lives-...