If a company like Uber can be divided into multiple Ubers that have to compete with each other, then the over-investment by venture capitalists can still be turned into a societal win.

If the early-stage employees have significant equity in the company, then they'll be very interested in how the company is doing. If their upside is paycheck, bonus and equity proportional to their salary (as you'd find in an established company), then one employer is as good as another.

I think the question of how much information to share is heavily dependent on how loyal the employees are to the company, and loyalty is almost entirely a matter of how much equity they hold (and more specifically how much equity they hold relative to the founders.)

They should change the name; it's difficult to understand why the maintainers are so attached to something so self-defeating.

Sometimes it means "trans-Atlantic", an accent which Buckley, Burns, and many pre-1950 movie stars spoke with (while on-screen anyway). It falls somewhere between the accents found in the USA and accents found in the UK.

In the context of this thread, I think it means the mid-Atlantic states in the US. It's close to the American "television news accent".

EDITED TO ADD: It's worth noting that the two accents called "mid-Atlantic" sound very different.

I hate cars, and I hate how expensive housing is, but as far as I can tell, housing is even more expensive in places (in the USA anyway) where cars are less necessary.

I can't find the reference, but consistent with that, I remember reading someplace that the number of items in your queue should typically be zero, since queues can't actually make the rest of the system any faster. All they can really do is buffer temporary bursts, or buffer while the rest of the system recovers. And for that you'll definitely need your recovery system working as a prerequisite.

If this professor is unconnected to the sanctioned Tornado Cash service, then Github shouldn't have to worry about running afoul of the sanctions by hosting the code.

Because it's being publicly revealed.

If the lax security you describe at other companies were also revealed, maybe more would be done to fix it.

> Pete concentrated on building a system [in COBOL] that works for him and his clients.

If that system isn't replaced before Pete retires, it turns into a significant hidden risk.

You don't know how dependent on something you are until you try to replace it with something else. If hype is driving the replacement, so be it. An organization can make replacement a regular practice and get good at it; or it can find out when it unexpectedly becomes necessary.

In the long run it might be better to treat software as "fast fashion" rather than something meant to last forever.

Charles Darwin was in his early 20s, and the captain of the Beagle was only a few years older, when they blasted off to sea to do their surveys.

I'm not a lawyer, but I don't think it follows that every financial transaction is a 1st amendment issue, just because spending money to promote a message is protected.

Oncall is a scourge not because of the experience of technical problems, but because people already working full time have to arrange their lives outside of work around a second "oncall job". A job which occurs after hours, one out of every X weeks.

A dedicated, pure "Ops" night shift (perhaps in another time zone) would be more humane.

> Speeds in residential areas are high, so dangerous to play in the streets.

Speeds on trunk roads are ridiculous, but the streets with the actual houses on them are not the nightmare you describe.

Everybody just biked from place to place and spent like 18 hours a day outside of the house, playing basketball, duplicating cassette tapes and making music in various garages.