Hacker Newsnew | past | comments | ask | show | jobs | submit | mlyle's commentslogin

1. I don't think adding robustness necessarily requires changing how systems are presented to the flight crew.

2. Bigger changes than this are made all the time under the same type certificate. Many planes went from steam gauges to glass cockpits. A320 added a new fuel tank with transfer valves and transfer logic and new failure modes, and has completely changed control law over the type. etc.


Yah, but that's a case of the package not being opaque enough.

> Point #2 ("somewhat less fit... on average") is totally inaccurate if the parents are statistically average in the modern/Western world.

I wonder if you've misunderstood the point. Offspring are expected to be less fit on average because -things can go wrong- (mutations, birth defects, etc). But selection is a counterweight to this.


Seemed to me that the author was referring to regression to the mean, as another commenter noted.

De novo mutations have a negative effect, to be sure, but it is extremely weak on an individual level. In parents who are extraordinary, the effect of regression to the mean is going to be 20x to 40x stronger than the effect of de novo mutations. For instance, if you have two parents who are both 195cm tall, the regression penalty might be 4cm, whereas the mutation penalty would be somewhere in the millimeters, so a statistically average child would be ~190.9cm. If both parents are statistically average, there'd be no regression penalty and only a vanishingly small mutation penalty.


There's already been a Cider; it used some Wine code to ease porting games to MacOS.

For reasons that I do not understand, the company behind Cider pivoted to real estate investing, and got out of the tech field entirely

Hard Cider

I think they were saying that smoke/particulates could be sufficient to upset the rear engine-- things short of what we ordinarily call "debris".

That's assuming that the distribution is purely gaussian and nothing weird happens at the tails.

I agree 276 is unlikely (and how would you even test/norm such a thing?)


Well, compliance itself is costly, but the cost is stuff that society decided it wanted to spend money on.

But uncertainty in compliance and time spent navigating compliance is nearly pure waste.


To continue a conversation from another thread on another post, uncertainty, complexity, ambiguity, and out-of-band context required are all costs that just happen to act as moats for entrenched incumbents. And no surprise, such incumbents often have so much influence over politics that they literally write the laws that regulate them.

The folksy aphorism goes, The more wild cards and crazy rules, the greater the expert's advantage.


I'm not sure.

Complexity is clearly hired by lobbyists all the time, but uncertainty and ambiguity seem to me to be mostly caused by incompetence. It's not even clear if uncertainty benefits incumbents more; it can just as likely destroy a market or benefit new entrants, and you can't predict which will happen at the time you create it (otherwise it's not uncertain).

Legislative houses need technocratic QA. And that QA needs to be independent from the law-writing process.


Yes-- I think most of us are familiar with regulatory capture. But the solution to regulatory capture isn't "no regulation."

Wild cards and crazy rules versus no regulation is a false dichotomy.

Easy to not play the card game, by only collecting the data needed for your service.

It's perhaps practical, though, to ask it to do a lot of verification and demonstration of correctness in Lean or another proof environment-- to both get its error rate down and to speed up the review of its results. After all, its time is close to "free."

They -are- decent modular chunks. They have a bit of opinion pushing you in certain directions as far as sound goes.

Each one does a pretty limited set of things and combining them can be annoying.

But you get a lot for the money you spend on them.


combining them can be annoying

The strong design opinions about how the Pocket Operators interact with other musical gear are a big part of why I haven’t had high enthusiasm for using the small PO’s when I’ve had small PO’s.

For me, Volca’s are a similar ecosystem but to a lesser extent…maybe because the Monotrons sit lower in Korg’s product portfolio while the PO’s are rock bottom of TE’s product line.


I gave my kids (5 and 2) two Volcas (Beats & Keys) to play with. The Keys is a bit too advanced (too easy to get no sound at all, or something that sounds horrible), but the Beats is a wonderful machine for kids, as it's virtually impossible to make it sound bad. Also great to teach them rhythm.

That's true, but the number of paperclips you'll produce if you only devote effort to things that directly produce paperclips is also very low.

It can be really difficult to strike that productive balance.


Somebody once said in light of this dilemma: Do things that don't scale.

This never meant: "It's fantastic if things don't scale". It means: "Trying to start by doing things that scale is probably bad". I mostly believe that.


I also believe that in order to bootstrap a viable system, start with system 1. The OP is partially sniping at people who creating all kinds of elaborate structures for systems 2-5, without attending to the first order of business, which is system 1. I've been guilty of this myself.

But it's easy to find dysfunctional organizations that focus almost exclusively on System 1, and it looks like grinding, hustle, "doing the thing", being stuck at CMM Level 1, and in my experience, it leads to burnout. So there has to be a balance.


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

Search: