Hacker News new | past | comments | ask | show | jobs | submit | db48x's comments login

Same here, except I use an HP48 emulator because TI sucks and HP rocks.

It’s because there was no iteration. There was only one attempt to actually use the discovery to influence society. There should have been at least one smart bad guy who used knowledge of psychohistory to search for conditions that would favor his preferred outcomes over Seldon’s.

There’s a smarter treatment of the idea in the John C. Wright’s “Count to the Eschaton” series.


It’s not actually burning the oil, just dumping it into the airstream in the form of tiny droplets. Some of that gets sucked up by the bleed air system, the rest continues on to the combustion chambers to be burned.

> […] stops short of recommending some very, very simple steps in aircraft configuration prior to takeoff that would completely mitigate the issue […]

Well, the configuration changes during takeoff mitigate the issue if it happens during takeoff. If it happens at any other time then they don’t do anything to help.

> I can see no reason to drag feet on this recommendation […]

I can. Perhaps the FAA believes that it is better to minimize change fatigue. Since the problem can apparently be fixed in software, and Boeing has decided to make that fix, they might want to write just one airworthiness directive requiring everyone to install it instead of two, one telling pilots to adopt some procedure followed by another telling them to abandon it.

> (It is yet another difference from older 737 design , like the deadly MCAS system, that was not disclosed to pilots transitioning to the new aircraft)

Keep in mind that for most aircraft the airline can pick and choose between different engines. The pilots don’t have to learn the myriad different engineering decisions that go into those engines; from the pilot’s perspective they are supposed to be interchangeable.


>Perhaps the FAA believes that it is better to minimize change fatigue.

Additionally you might want to avoid the association that specific pack supplies air to the cockpit, as it varies across generations. https://en.wikipedia.org/wiki/Kegworth_air_disaster


Oooh, that’s rough.

> Well, the configuration changes during takeoff mitigate the issue if it happens during takeoff. If it happens at any other time then they don’t do anything to help.

There are no birds at higher altitudes


Fewer perhaps, but not none. :)

Right? I remember there was a bird strike incident at 37,000 feet, a vulture iirc. Hard to imagine how they can get enough oxygen to fly up there.

> Keep in mind that for most aircraft the airline can pick and choose between different engines.

737 Max can only have CFM Leap engines.

A320 can have either Leap or PW GTF.


They’re readily available, but most households don't actually have one. Many more households have a coffee maker, which is essentially the same thing but specialized for dripping the boiling water through coffee grounds. Anyone else who needs boiling water just puts a pot on the stove, or possibly an old–fashioned metal tea kettle.

We could even use 240v electric tea kettles here in the US if we wanted to; most kitchens with an electric range and oven have 240v (or 208v) outlets to plug them in to. But those outlets are usually inconveniently located for counter–top appliances. It wouldn’t cost much to add another above the counter, but it is rarely done in practice. Of course, in many parts of the US natural gas heating is cheaper than electric so the houses there are built for gas ranges and ovens instead.


If the cheaper 14guage wire was used in the walls then only the 15 amp socket is appropriate, otherwise you might plug in a 20amp device and melt the wires or burn down the house.

    if [[ "${TERM}" != "dumb" ]] || [[ $- == *i* ]]; then
        PROMPT_COMMAND='printf "⏎%$((COLUMNS-1))s\\r"'$'\n'"$PROMPT_COMMAND"
    fi

This is actually really impressive coverage of the launch system. The photos and videos of the maintenance and upgrades are extremely impressive considering that so many of them are made by a guy who just sits across the street all day.


Maybe you could have just told us what the "unbreakable law" is, so we can all see in 2 seconds? Instead of posting a link to video that doesn't seem very keen to tell us even in the first couple of minutes?

Thank you for compounding the problem. Skipping ahead to the conclusion, I am guessing the law is "be lean and flexible"?

No, the unbreakable law is Conway’s Law (not that Conway):

    “Organizations which design systems (in the broad sense used here) are constrained to produce designs which are copies of the communication structures of these organizations.”

Oh, ok. Thanks, but curious why that link instead of so many others which talk explicitly about that law

He talks of nothing else for most of an hour, and provides several salient and memorable examples.

But you only have to figure that out once. Amortized over many contributions the cost is essentially nothing.

But the initial cost is what determines whether the first patch will ever be sent, so the amortization may never happen.

I guess technically that’s true, but it cannot possibly take long to learn how to use `git format-patch`, and everyone should already know how to attach a file to an email. Even if you have to spend half an hour reading the entire output of `git format-patch --help`, is that really enough to prevent you from sending your first patch?

Yes.

Ok, let me get this straight. You diagnosed a problem in the Linux kernel. You debugged it and figured out how to fix it. You edited the kernel source code, recompiled it, and tested your fix. After all that, if you have to read a man page you’ll just give up?

That’s seriously lame.


What time is more valuable than that, and I don’t owe it to anyone.

By that same token, there’s no reason for you to expect kernel developers to adopt a different way of working either. Their time is even more valuable than yours.

We only have so many hours in our sadly finite lives.

Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: