First to market is not necessarily the best, case in point: many video sites existed before Youtube, including ones based on Apple Quicktime. But in the end Flash won.

To me it looks like there is a better way to do things and the better one eventually wins.

bits == entropy.

Everything else is word play.

1) Build a mobile platform with wheels that starts at the beginning of the runway

2) matches speed with the plane as it enters runway.

3) Plane will “touchdown” on the mobile base gently since speeds are matched.

4) Lock the plane to base and decelerate the base in a controlled manner.

If you can gently lock the base and plane you can even save the plane

That's an episode from "Thunderbirds".

Implementing a mobile landing platform for commercial or high-speed aircraft is a theoretically sound concept for emergency recovery or weight reduction but faces massive technical hurdles in precision, synchronization, and infrastructure.

Just make a huge baseball glove to catch the plane as it's approaching.

You’re after a fast aircraft carrier.

Ha ha, but seriously that couldn't possibly work with any significant crosswind.

it just means the mold should be tilted with respect to the travel direction: if you have the technology to match the speed, surely you have the technology to rotate the receptacle in the horizontal plane to match the horizontal plane rotation angle induced by crosswind.

The problem with such a silly, unrealistic Rube Goldberg style scheme is not only the aircraft attitude but the lateral velocity relative to the runway centerline.

But don’t you think that’s how silly Elon’s rockets look like while they are landing?

Next project: interstellar jump craft

That seems like incredible overkill for a 1950s era bomber jet, no?

It can be reused.

Compare this with how customer requests end up in products in startups:

Step 1: Customer <-> Sales/Product (i.e., CEO). Step 2: Product <-> Direct to Engineering (i.e., CTO)

The latency between Step1 and Step2 is 10 minutes. CEO leaves the meeting takes a piss and calls the CTO.

- Simple features take a day: CTO to actual implementation latency depends on how hands on the CTO is. In good startups CTO is the coder. Most features will make its way into the product in days.

- Complex Features take a few days: This is a tug of war between CTO - CEO and indirectly the customer. CTO will push back and try to hit a balance with CEO while the CEO works with the customer to find out what is acceptable. Again latency is measured by days.

Big companies cannot do this and will stifle your growth as an engineer. Get out there and challenge yourselves.

Things you shouldn’t spend time on in a start up

A startup shouldn't prevent their main product from irrecoverably crashing?

The “pros” list is exceptionally weak. This was clearly written by someone who doesn’t like exceptions. Can’t blame them.

Spot on. There are disproportionately few people who care for the product. Most people care for making that fat promotion package so they can move up. Both eng and non eng.

Frog & Toad is a grown up book disguised as children’s book. I very much enjoyed reading it to my boys.

Hard no buddy. Junior dev means junior code and junior judgement. Countless times we had prod issues because some dev thought the change was harmless and they didn't need review.

In the article, they specifically exclude juniors and people who are still being onboarded.

I can’t find that disclaimer in the article.

OP here. In this one the closest is probably: "I love the process at Pylon: engineers merge their own code and only request reviews if they need input, think they have a risky change, or are still onboarding. "

But I fully agree that for juniors it makes sense to have it mandatory.

Sorry I’m too paranoid about this stuff.

I couldn’t get past ”Paste the private key file id_ed25519 into the .git directory of your current repo,”

I stopped worrying after I began protecting all keys with a passphrase.

Then the access of your git repos is protected by a single factor, the private key, since the private key is already in the wild.

Copying a private key on a removable storage or to another device than the device that generated it is never a good idea.

I protect mine with GPG for SSH authentication.

The only use of the passphrase is to give you time to rotate out the key after it's been compromised. It's not meant to be your main line of defense