1,386 karma · joined July 26, 2011
Everybody knows when one person in a text group isn’t using iMessage, and they usually hate it.
Risk aversion doesn’t actually mean you’re good at addressing risk; in fact it may keep you from implementing changes (change is risky) that address real risks.
It’s just irrelevant since you don’t need anything even approaching hyperinflation to have real world impact on people, and the real wage loss over the past several years is clearly in that category.
To save humanity we should destroy humanity.
No thanks.
So the workload you describe — without more detail — may in fact be just fine with that connection count.
But plenty of people also run Postgres with well above 500 max connections.
Using a partial index where it’s obviously matches the use case (like when a majority of values are null) is just correct modeling and should not be considered a premature optimization or waste or developer time.
Some projects put in that work (e.g., PostgreSQL), but it comes at a significant tax on productivity that could otherwise be put into new features.
Never attribute to malice that which can be adequately explained by incompetence [and misaligned incentives].
Designing a good experience and flow for a piece of software is hard. You have to work for it not to be bad rather than work to make it bad.
That’s the thing we need to fix regardless of the power source.
But the difficulty for proving masking helps is: 1. If it only takes ~20 virions to get infected, then masking has to have a basically perfect filtering rate and be worn perfectly 100% of the time, neither of which is obvious. 2. With an endemic virus even if masks slow down spread they aren't going to reduce your likelihood of being infected overall.
More importantly though I think you’re missing something very big about open source projects — the transition from “small project with single maintainer” to “group ownership” has always been a difficult one; that’s not unique to GitHub.