jazzkingrt

I think Levine fails to note one benefit of invalidating non-debtor releases.

Yes, the current victims suffer from having less money available to a settlement.

But future victims may be better protected, as non-debtors now can't exploit a bankruptcy case to settle their liability. They are more vulnerable to expensive litigation, and draining of their assets unless they shield them offshore and probably stay out of the country. This could be a potential deterrent to future malfeasance.

Why would fixing driver problems be bad for doordash? The incentives are fairly aligned. A more effective and efficient delivering experience means more deliveries can be sold to customers, at a lower price.

Disclosure: I work for a food delivery company competing with DD

I agree with the premise of the article, that some of Kandinsky's work is not readily "decoded".

But at the Guggenheim exhibition, I found that to be an appealing element, rather than a problem.

In the more "decodable" work, like Several Circles, you can mentally set aside large areas of the painting because the structure is predictable from those parts you've already looked at. In a way, much of the painting can be abstracted in the mind during the visual experience.

But in the more "heiroglyphic" paintings, the eye doesn't get to settle. New details emerge each time you adjust your gaze.

Allegedly, Kandinsky took visual inspiration from diagrams in medical and biology books. What better example of mind-bending complexity than our own biology.

I agree. Maybe in a few decades we'll just stick to China Standard Time.

Both my parents are 60+, my father is in his mid seventies, and they are as productive as ever.

I think that a lot, perhaps most, AI diagnoses would involve a feedback loop that tracks the patient's health outcomes.

Here are some examples of feedback: - The AI misses a cancer that gets worse and is later detected on a blood test. - The AI detects a cancer on an x-ray but a (more accurate) CT or biopsy indicates that there is no cancer

These kinds of feedback loops should allow the clinical performance of AI to be measured and hopefully improved over time.

Recently visisted a "staff show" at Pace Gallery, in which the entire staff (assistants, front desk, archivists, art handlers, ...) was invited to submit their own art.

It seems to have done well!

https://www.pacegallery.com/exhibitions/atmospheres/

Superb tool!

In 15 mins, I was able to get rough answers to questions like:

* When am I financially independent if I keep living the way I do now?

* What if I lowered my expenses right now seeking earlier FI?

* When could I hypothetically stop working by lowering my expenses at the point of retirement?

* How much would be left in my estate?

I bought the lifetime subscription, which seems like quite a good deal!

Doesn't this just provide another (perhaps more nearby) remote?

You still end up doing some kind of large checkout.

I think this is quite exciting, as it solves a major unsolved problem for large git monorepos: enabling development or CI/CD inside a git monorepo without requiring a large checkout.

As monorepos grow huge, this comes to be very costly or even prohibitive, and companies like Google simply don't use Git.

Here are some problems with alternative approaches that have been mentioned:

* VFS for Git: I believe abandonded by MSFT in favor of improved client-side tooling: https://github.com/microsoft/VFSForGit/blob/master/docs/faq.... .

* Sparse checkout: limits ability to use a build system to dynamically find any dependencies and rebuild them

* Submodules: can't atomically update both the parent and the child repo, have to manually update the referenced commit of the child repo in the parent repo, and each collaborator must manually update their child repo when the commit changes

I've used depop a fair amount, I think it's a big leg up over eBay because of it draws some useful features from social media.

The feed allows you to follow and discover sellers whose style suits you, and stay informed of their offerings. You can see who they follow, and so on.

I used reviewable.io at my last company, and now use phabricator. I actually still prefer reviewable, so give that a look.

This raises an interesting point.

I think we already live with this kind of tension much more than in the past, as made clear by the voting patterns of young vs old.

Sharing a country with people of such different values is hard. Particularly when the older generation is always the shrinking demographic and feels its way of life is at risk.

What can alleviate this? More federalism? More geographic clustering by age? A culture that puts empathy over shame?

I think if you read the two parent comments to "this is the correct take", they also take an authoritative mood.

Rather qualifying a statement with "I think", or "I believe", they basically assume some reality to be true and then describe it. And that's ok, as readers we assume that the author is giving their opinion.

So "this is the correct take" should be read as "in the reality that I believe is true, this is the correct take".

That doesn't solve the the software/architecture problems that led to these huge hosting requirements.

Yeah, SDI doesn't do a very good job of actually solving that chicken and egg problem. It tends to give a "solution" without motivating the design decisions.

After reading about 80% of SDI and not much else, I failed a system design interview when I provided the "right" answer of putting an async task on a messaging queue, but couldn't explain how at-least-once delivery could be used to deal with a flaky task.

I think I've filled a lot of these gaps now (passed L5 system design at Google for example) but there wasn't really a single efficient resource that helped me do so. DDIA is awesome though.

I completely agree, but that population would be a pretty small readership.

"Gender and sex are different" isn't intended to mean that they are completely independent concepts.

I agree. A big missing link at my organization is a VCS that can make it easier to checkout and operate on only a subset of a large (many GBs) monorepo.

Unfortunately, microsoft had to move away from VFS for Git to some a more limited-in-scope approach: https://github.com/microsoft/scalar

The "marketing service" just means being listed at all on GrubHub itself. So restaurant owners are agreeing to a big fee to get customers from the GrubHub website and app.

But it sounds like they often don't know that they are also being made to pay a fee for their own customers who are simply looking up the phone number.

GrubHub isn't obviously adding any value there, these customers could just as well have pulled the phone number from Google Maps of the restaurant's own website.

I think GrubHub could be acting incorrectly in few ways: 1. Restaurants don't appear to be well informed of the cost. Deceiving your customer (eg by sneaking clauses into the contract) doesn't feel right. 2. GrubHub could be deceiving the restaurant's customers, who may be making a sincere effort to order from the restaurant directly. 3. In some local markets; GrubHub might have a kind of monopoly power. I think are a lot more constraints on how these kinds of businesses can dictate terms to other business: https://en.wikipedia.org/wiki/Vertical_restraints

Certainly possible. Glibc has the sysconf function which can provide the cache sizes at runtime.

https://www.gnu.org/software/libc/manual/html_node/Constants...

However, consider a scenario like a database where you might store on disk once and don't get cheap opportunities to reorganize data when the memory or processor hardware is switched out.

Or when your data is sent over the network for processing by some arbitrary client hardware.

I don't think "conflated" is the right word. Romer doesn't imply that these problems have the same cause, or are even correlated (although I suspect they are).

He just lays them out as stark examples of FDA getting in the way of the public interest in this pandemic.

I think that's right, but organizationally challenging to implement.

In my experience engineers don't really think through this question carefully, and have to be prodded to do the right thing, or at least the thing that better serves others or their future selves.

There's also a hump to get over until network effects take over, where engineers have strong incentives to participate in the monorepo.

In your iOS vs web team example, we might imagine that they eventually want to run an integration test against the same API, whose team helpfully provides a hermetic version of the service for testing against. (Dropbox wrote some bazel rules for this sort of thing: https://www.youtube.com/watch?v=muvU1DYrY0w)

This was helpful to me. How does the PE company fare in the bankruptcy scenario? Have they put up collateral or are somehow on the hook to the lenders?

It's my understanding that the bankruptcy applies only to the purchased subsidiary, so the PE firm only stands to lose the principal they put in at the start.

If so, it sounds like the PE firm gets all the upside, but is less exposed to the downside. So they are incentivized to rachet up the risk.

Great timing! Current conditions are WeWork's nightmare scenario.

WeWork's raison-d'etre is short term leasing. Leaseholders will end those leases if everyone is working from home. Add to that that an economic recession was always going to be the real test of WeWork's ability to keep up with its huge long-term leases.

I disagree. The SLA ought to be made on a per-customer basis. 1% of users affected would mean 1% of users would be entitled to refunds/remedies that the SLA prescribes.

What I've seen work well, for multiple migrations, (at an admittedly smaller scale) is using shadow writes/reads and a source-of-truth toggle.

The API layer made requests to both the old DB and a new DB that had been populated during a small window of scheduled downtime.

We spent a couple weeks/months running checks in production that the old DB and new DB were returning identical results, though still returning the old DB's results as source of truth. Eventually, we flipped the source of truth to the new DB, and some time later decomissioned the old DB.

I don't think the author is a googler?

Her adulating tone frankly undercuts her claims, namely that the Louvre is not questioning the attribution.

Maybe not the Vision fund itself. But analysts seem to think that Softbank stock is really cheap when measured against its paper assets.

https://www.barrons.com/articles/softbank-stock-wework-and-u...