debergalis
Joined 15 years ago
Joined 15 years ago
> So assuming what we did wasn't good, what is a way you might make this work? Do you have a single code base like we did and just be more disciplined? Do you have a project whose job is to stitch together other schemas and pull in submodules? A monorepo for the entire company? Do you actually limit what the idea of the company is at some point to limit what the scope is that this should cover?
I think these are great questions. One approach that looks promising is the idea of modular schemas that can be stitched together into a larger graph. Quite a few large organizations are doing this now. I recommend watching a recent talk by Martijn Walraven for more on this idea: https://www.youtube.com/watch?v=OFT9bSv3aYA
Yup, we see this pattern a lot. You get the benefits of fewer bytes on the wire, typed APIs, elimination of data fetching code, etc.
But it leaves a lot on the table. The bigger wins come when new features can draw from all your data (in unanticipated combinations) without new API or services development, when you can make new data available for every team's use just by plugging it into the central graph, and when you have a birds-eye view of exactly how all your data is being used so you know where to make further investments.
Yup, all three are customers.
Yeah, budget and familiarity. I doubt Cessna is selling many 172s to anything other than flight schools.
Cessna doesn't call it this, but the Mustang is pretty close to VLJ sizes. (Not many being made though, as their M2 pretty much took over that space of the market.) The Embraer Phenom 100 is similar. Both have been reasonably successful.
You target an appropriately rich mixture at sea level when tuning the carb or adjusting fuel flow for injected engines. The pilot manually leans the mixture as the aircraft climbs to maintain a reasonable fuel/air ratio.
Owners sometimes call that mixture lever the money lever because it governs fuel flow, aka "dollars spent per minute".
For the most part, commercial operators must adhere to these recommended times, but aircraft operated under FAR Part 91 (roughly, those that aren't used for commercial transportation) aren't required to follow the TBO recommendation. You can run it as long as you want.
In practice, most operators do follow those guidelines. I've never heard of any engine doing much more than 2x the TBO before requiring major overhaul. And you'll often need various repairs to cylinders and engine accessories along the way.
Interestingly, manufacturers also specify calendar time limits on TBO, but private operators commonly ignore these. Lots of airplanes only fly 25 hours or so a year.
the suggestion was “orthocode”.