metanoia

I definitely point and call to myself when doing deploys and running DB migration scripts... just to make sure I'm not changing production when I don't mean to.

HART (the light rail system they're building) is a complete disaster, for the same reasons.

I can't see the government there being able to handle much of any major infrastructure project. The airport expansion is moving at a glacial pace as well. And it's a miracle the H3 ever got built.

This sounds really great, and I think that this will open up a new frontier in winemaking.

One question I have is how you plan to replicate terroir. TA, Brix & pH are great indications of when to harvest but drainage, soil composition, sun direction, duration, diurnal temperature swings, seasonal temperature patterns, wild microbes, etc. all have a significant effect on the outcome of the wine.

For those who aren't into winemaking: the most enduring, famous wines such are not just famous because of winemaking technique but because of the specific place - even down to the rows of vines - the grapes are sourced from.

Assuming consistent winemaking technique from a cellarmaster, when you get to the point where you can control all those variables and get to the outcome you want at the individual vine level, then comes blending, which takes flavor profiles from wines made from various plots and/or vineyards and selects for specific flavor profiles to make up the final wine.

So, you'd have to achieve what you're proposing at scale as well as with variation across different "lots" so that you can "replace the vineyard" for a given winemaker.

Just food for thought, I like the idea but I think there's more thought that needs to go into your product development and target market.

They say that wines are made in the vineyard, and that has been true for a long time, but with modern techniques, it's hard to tell if a wine was made in the vineyard, the cellar, or in the lab.

Before 9/11 we could easily tour an ATC facility with a group of pilots - tower, center, tracon - under Project Raincheck. Not sure if they've started that back up again or not, but it was definitely eye opening.

Edit: Just read the section under "Line Up And Wait" and lol'ed to myself when I saw this:

"Do not authorize an aircraft to LUAW if an aircraft has been cleared to land, touch−and−go,stop−and–go, option, or unrestricted low approach on the same runway."

I'm pretty sure SFO lines up aircraft on the 28's and simultaneously clears someone before the San Mateo bridge to land, while waiting for a landing aircraft to clear the runway.

It's a bit out of date as far as some regulations go, but I am a big fan of Rod Machado's Private Pilot Handbook. Really simple but rich explanations of most of the concepts in a digestible way.

I love the DA-40, it was definitely a step up in capability from the 172 after I got my ticket. But the one time I flew it through the Mojave I definitely felt the DA-40's roots as a glider, I got pretty tossed around!

throttle (v.): (1) to compress the throat of; choke (2) to kill by such action

The OP was about sub-launched ballistic missiles - I was trying to make the point that when a ballistic missile flies from a sub, you cannot tell the yield, and the potential hair trigger-response will be the same regardless of yield.

This type of weapon is essentially destabilizing, as the article said.

I agree with you on other weapons, the flight profile will be vastly different.

Exactly this. An infrared flare from a missile launch, seen from a launch detection satellite, looks exactly the same, 20kt or 450kt warhead.

Called off due to high winds above the limit for first flight.

(2 days in a row)

On MacOS, iTunes/Finder stores (optionally) encrypted backups at

   ~/Library/Application Support/MobileSync/Backup

I was thinking of creating a symlink to Dropbox, for instance and having my cloud backup there. I don't know if the backups are incremental which could be a storage problem, but that can be managed through some scripting.

Since we hold the key it's a blob nobody can get to without brute forcing it.

It's precisely due to this lack of real accountability that these kinds of things happen in C-suites everywhere. Massive golden parachutes are the "punishment".

Asset seizure and jail time work wonders, too bad they're not being used.

I listened to the ATC tapes on LiveATC (and now can be found compiled by VASAviation on YouTube).

When DL98 first declare an emergency, Socal asks the crew if they need to dump fuel and they indicate they do not, but end up doing it anyway, even at low altitudes. Something happened along the way that made them decide to dump fuel and try to get under max landing weight, but when you're single engine, you want to get down on a runway ASAP as you don't know that the problem affecting one engine won't happen to the other.

I am not a 777 driver, but an overweight landing is always an option - in fact, required when you're single-engine. Checklists for engine out say "land at nearest suitable airport." Holding and dumping/burning fuel is, in my limited knowledge, reserved for instances where there is a fault that prevents forward progress but does not necessitate an emergency landing.

Can't think of any examples off the top of my head right now though.

It's brutal because of lack of easy access to data, and more importantly, the ability to create bookings. IATA NDC API's should theoretically change this and get around the GDSs but I'm not holding my breath.

I've had a number of travel startup ideas but all were held back by access to data.