Live data from Hacker News

Efficiency Is the Enemy

fs.blog

301–310 of 335 posts

Re: Efficiency Is the Enemy

#301

And this is why you schedule flights in the morning: there's so damn little slack in the system that if things go wrong at 10:00 AM at O'Hare, flights for the whole rest of the day are screwed up owing to the cascading delays. At least in the morning the airlines have had the overnight to unsnarl the previous day's mess because of the reduced revenue traffic overnight and the corresponding slack that accrues as a hap…

> This is also why things like the healthcare system, transportation network, and postal system shouldn't be run for maximum utilization/efficiency under normal load: if there isn't any slack in the system it gets real ugly when things get squirrelly. A couple years before the pandemic, the counties neighboring mine (where I lived at the time) cut out most public medical services (mind you, these aren't free , just p…

> Lean means cutting the fat, not the meat. They didn't just cut the fat and meat, they cut to the bone.

I will upvote you just for coming up with this illustration. This should be useful for future reference.

Re: Efficiency Is the Enemy

#302

One of the uncomfortable conversations we're going to have to have soon is about how 'Flow State' is efficient but ineffective. One of the characteristics of Flow State is a diminished sense of considering the consequences of an action. Exactly the "so busy figuring out if they could do it that they didn't stop to think if they should do it". In particular I've noticed that people get extremely defensive about code t…

I agree with this. Flow is a useful adaptation for something like learning muscle memory - practicing athletics or performing music. But when we're talking about intellectual pursuits like programming, if what you've done by entering flow is convert thinking into muscle memory - a cycle of mashing edit and debug keys - you may have just "laborized" your work. And this has some implications for what kinds of software…

> and you'll only wake up to it later

I generally consider myself fairly good at gathering evidence of self inflicted problems, but I’ve worked at places where the worst offenders never really admitted hey have a problem. Once you involve the ego, people can feel an existential threat when you tell them the thing they are good at, the thing they enjoy doing, is hurting everybody.

We tend to develop coping mechanisms to deal with our own flaws, but everyone else can find themselves adapting to the new circumstances fairly suddenly.

Re: Efficiency Is the Enemy

#303
post #133

Earlier quoted context omitted.

The thing that kills me about the ticketing systems is that they are often put into place in a way that is locally efficient but does not make sense globally. For example, an application owner might have to submit a ticket to request an upgrade once a year (or when a new OS is supported). What often happens is that the application owner now has to know about, find, and correctly understand a form that they see once (…

A lot of medium-to-large organizations used to have dedicated administrative staff, not just for senior management, but for everyone. It was good because the people in the admin pools were experts at navigating the organizational structures. They did it every day, all the time, for everyone, so they knew the tricks. In the interest of cutting labor costs, those jobs were cut, and self-service systems like the ones yo…

The culture of "self-service" in companies is more like the culture of "self-waste". What just used to take a single e-mail earlier now takes navigating a plethora of half-broken apps, sites, wikis and issue-trackers - all done in the name of cost, process and 'metrics'.

Re: Efficiency Is the Enemy

#304

Earlier quoted context omitted.

The magnitude of the delayed flight effect is fairly small: flights at 3pm are only delayed by 10 mins more on average than 6am flights. https://fivethirtyeight.com/features/fly-early-arrive-on-tim...

It's a little disappointing that 538 didn't talk about the distribution on this. I'm looking to avoid the one flight that's delayed an hour that means I miss my connection because my layover was an hour. Only 5 flights have to arrive on time to hit an average arrival delay of 10 minutes. Those are not favorable odds, as I see them. Especially if it's cutting into my vacation time.

Yes, missing a friend's wedding or an on site interview or ..., because no more connecting flights until same time tomorrow, with a probability 1 in 6 is pretty bad odds

Re: Efficiency Is the Enemy

#305

And this is why you schedule flights in the morning: there's so damn little slack in the system that if things go wrong at 10:00 AM at O'Hare, flights for the whole rest of the day are screwed up owing to the cascading delays. At least in the morning the airlines have had the overnight to unsnarl the previous day's mess because of the reduced revenue traffic overnight and the corresponding slack that accrues as a hap…

OK, but the corollary to this is that there are a fair few people sitting around doing not a lot on the taxpayer's dime. That's the visible side-effect of organisational slack (as TFA points out: the secretary spends most of her day doing nothing). There's been a lack of tolerance for that. We tend to feel that if our tax dollars are paying for someone, that someone had better be busy all day long. Politicians have m…

Maybe studying and getting better at one's job, during idle times

Firemen have lots of idle time? I think they play floorball for example (good for them to stay fit)

Re: Efficiency Is the Enemy

#306

One of the uncomfortable conversations we're going to have to have soon is about how 'Flow State' is efficient but ineffective. One of the characteristics of Flow State is a diminished sense of considering the consequences of an action. Exactly the "so busy figuring out if they could do it that they didn't stop to think if they should do it". In particular I've noticed that people get extremely defensive about code t…

I think you're misconstruing the Zone with the Flow State. Note these are really just arbitrary terms with vague meanings, but I think it's still useful to have terms to root the discussion. What they have in common is the aspect of no-self, where you lose your sense of self and become what you're doing. But I think how this manifests is different. In the Zone is where you have the full context of the problem in your…

I find it interesting that Wikipedia agrees with me. What’s your opinion on them treating the two as equivalent?

But for argument’s sake let’s say they are different and I’m talking about the Zone Which is Not Flow. The hazard is still there, right?

What you’re describing is, to me, one of several other mental states, in which you can perform one physical task while your attention can be on any subject, from the subject matter of the task at hand, to philosophy. Because you are working from rote, it’s optional whether you consider the profound long term implications of your actions. In this state you aren’t really going faster than anybody around you doing the same activity. Whereas rearchitecting a big part of your code base invites a trip to the Zone, even if Refactoring teaches us that with enough experience you can achieve similar outcomes without it.

In particular, mastery of a subject involves pushing much of the work into intuitive thinking, where it is cheap and affords you to focus consciously on anything you want. This is just mastery though, or what Thinking Fast and Slow might call Type 1 vs Type 2 Thinking. Maybe I’m weird, but I don’t really agree this is a mental state. Not any more. I’d be curious to see if, as you advance in your career and hobbies, if you still agree with your assertion that this is a mental state, rather than an achievement.

Something I’ve discovered is that a number of different groups lay claim to a Zone-like experience and for at least the ones I’ve tried, I’ve found they are all the same thing. Even though strategies vary for how to enter it, the feeling is exactly the same. Multiple sports, programming, even once in a yoga class (last day of a class, I recall thinking, “uh oh, this could be addictive”). I’m starting to have my suspicions about satori, and wondering if this is just some people’s first experiences with The Zone.

At any rate, this experience informs my comments about practicing entry and exit with the purpose of using it in small chunks instead of all at once (or all the time). The danger is if you can push that button why wouldn’t you all the time? It feels amazing, I wouldn’t doubt there’s a dopamine hit going on. But I don’t for the same reasons that getting buzzed on alcohol once a week or fortnight is one thing, and being drunk all the time is something else entirely. For many it becomes a conscious decision which road to take.

(I will confess that after all these years, including a six year run as an endurance cyclist, I still can’t say which of these states the Runner’s High is. I’ve felt good, I’ve been In the Zone, I’ve gotten lost in thought and had epiphanies, and I’ve had the miles melt away. I never felt a “high” that turned out to be a distinct experience, although in some cases it was my first.)

Re: Efficiency Is the Enemy

#307
post #175

Earlier quoted context omitted.

I was probably too sloppy in my wording. I interpreted the OP to mean work may have negative utility for the individual person, but not in the aggregate. I don't know that the idea that work is essential individual sacrifice for some end goal is particularly healthy.

I would hope for your own health you clean your dishes after you eat. There are a number of distasteful jobs that have to be done.

I understand where you're coming from, but I think it's built on assumptions that I'm saying don't necessarily need to be true. Namely, that cleaning your dishes is "distasteful" which tracks with the originally assertion that you do some jobs just to get them done to get to what you really want. I.e., they are just a means to an end.

My claim is this can be unhealthy because you're not really living in the present and constantly stuck in the mindset of "once this distasteful thing is done, then I can get to the stuff that makes me happy." Or to steal from The Good Place, "Humans only live for 80 years and they spend so much of it waiting for things to be over."

Re: Efficiency Is the Enemy

#308
post #209
post #42

Earlier quoted context omitted.

Iff you consider your work a net-negative or just a means to an end. There's certainly a case to be made for optimizing for work that is an end in itself where more work may increases positive utility in some areas (joy, fulfillment, whatever) and possibly decreasing it in others (money, status, whatever).

My idea is that "work", or maybe more precisely, a "job", is something that you only do because you have to, because you need something it gives in exchange, and otherwise won't do. If you do something because you enjoy it, it's a "hobby". If you are paid for that, too, you are just lucky to have the best of both worlds :)

I agree that's a goal, but I think it's overly concerned with the product (job) rather than the process (how the job is done). I think focusing on the latter is more sustainable for enjoying something because the job itself will undoubtedly get stale at some point and can lead to the hedonic treadmill of constantly looking to the next thing to make you happy. I've known people who have had jobs that people would traditionally consider unenjoyable, but they had the mindsets to truly enjoy the work by focusing on the process, constantly bettering their performance, etc.

Re: Efficiency Is the Enemy

#309

Earlier quoted context omitted.

> The US are quite relaxed in comparison. This is basically a myth at this point, bolstered by how much more we complain about it. The US made the colossal mistake of trying to do regulation at the federal level, basically equivalent to doing it at the EU level, which the EU is now attempting to do more of and discovering what a trash fire it is. And one of the big reasons for that is that the more centrally the regu…

That centralization leads to corruption is a common claim but I have seen the exact opposite. Being smaller and unwatched leads to more corruption. Smaller towns can have plenty of their local corruption and parochial influence which are more accessible. National level winds up cared about by everybody as it isn't a "someone else's problem" situation and thus winds up watched far more. Then there is the matter of con…

Local jurisdictions have to compete with each other. If one town has a 40% tax rate because it's giving half the money to the mayor's brother and the town down the road does not, everybody starts to move out of that town and the economic decline ousts the corrupt politician. When the same thing happens at the federal level (with the money going to Lockheed and drug companies), "move to Canada" is a lot harder than "move 5 miles to the other side of the town border where you're already still a citizen."

This doesn't imply that small governments are never corrupt -- you can certainly find examples -- but it keeps the corruption in check. It adds vote with your feet as a means to avoid corrupt governments.

And the idea that everybody is paying attention to what happens at the federal level is contrary to evidence. Remember "we have to pass the bill to see what's in it"? It's too easy for lobbyists to sneak language into multi-thousand page bills that nobody is ever going to read before it becomes law. Whereas at the local level you shouldn't have multi-thousand page omnibus bills that have to address every edge case for everyone everywhere.

It's also easier for local muckrakers to prevent corruption when they find it, because federal corruption tends to have coalition support. The F-35 is a boondoggle but the people in the districts who receive the trillion+ dollars in tax money are very in support of the program and you're not going to convince them to cut it because the money comes from outside their districts. That doesn't happen at the local level -- the recipients are in the same local jurisdiction as the taxpayers -- so once anyone identifies the waste you can build support to eliminate it.

Post reply on HN