Live data from Hacker News

Calling a bureaucrat by its name

scottlocklin.wordpress.com

11–20 of 31 posts

Re: Calling a bureaucrat by its name

#11
In 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.

Re: Calling a bureaucrat by its name

#12
post #8

There'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…

On 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. T…

NPC's come from gaming/internet meme culture.

Non-playable character

Re: Calling a bureaucrat by its name

#13

There'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…

Also, there's an important ability: to be able to come up with new or modified procedures.

Re: Calling a bureaucrat by its name

#14
post #13

There'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…

Also, there's an important ability: to be able to come up with new or modified procedures.

Certainly! My goal wasn't to claim an equally ridiculous opposite position, only to observe that a lot of very good engineering is completely indistinguishable from what the author sneeringly calls bureaucracy.

Re: Calling a bureaucrat by its name

#15
post #7
post #2

First 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 the…

Also, 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…

Concur. 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.

Re: Calling a bureaucrat by its name

#16
I 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" :)

Re: Calling a bureaucrat by its name

#17
post #7
post #2

First 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 the…

Also, 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…

The 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.

Re: Calling a bureaucrat by its name

#18
post #5

Such 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 conferre…

Isn’t engineering just another way to say applied science?

Re: Calling a bureaucrat by its name

#19
OPs 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.

Re: Calling a bureaucrat by its name

#20
It'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

Post reply on HN