roggenilsson

This is the same approach as for the 2022 Axie Infinity hack

Why is it a botpost to point out that levying taxes against the top top percentile doesn't generate significant tax revenue? It's a common talking point that is both wrong and disingenuous. Its fine to want to tax them, but claiming it's to generate money to pay for things doesn't make sense.

The total income from tax increases is relative to the gross income. The gross income of the 1th percentile of earners in the US is ~$3.3 trillion, whereas the gross income of the top 25% is ~$10.3 Trillion. Levying a tax against only the top 25% sans the top 1% would yield more taxes than the inverse. Small increases on large brackets tend to generate significantly more tax revenue than large increases to small brackets.

This is the funniest comment I have ever read on this website

In my previous job we worked like this. We had one dev branch that everyone pushed directly to and the dev branch was eventually branched to an RC branch which in turn was merged to master once the release was complete.

The team was small, around 6 people, and the codebase was maybe medium sized (~500k LOC). There was no formal review process, instead it was up to each team member to ensure the quality of their own and others code. In practice I would read through all commits that came in the previous day while having my morning coffee. If there was some egregious I would talk to whoever made to commit to make discuss if something should change, but this was fairly rare.

Formal PR reviews were only ever really used for new members or for bigger/sketchy changes where someone wanted more eyes on it.

Because I ended up reading most commits, I ended up knowing how pretty much the entire codebase worked. It takes a while for this to develop, but the more you do it the better you get at it, especially in the context of a single codebase.

>Rent-seeking is the act of growing one's existing wealth by manipulating public policy or economic conditions without creating new wealth

Would the PC video game market be bigger or smaller without steam?

You can also think of generators as a native implementation of Observables from rx (except you can't replay a generator), especially async generators.

You can implement basic operators like map, filter, take, etc. over generators to create pipelines of operations. Very neat abstraction to work with, but like rx, can quickly get hard to reason about.

Recently I wrote some tooling to read, do some operations, and write hundreds of thousands of files locally. Using generators solved having to think about not loading too much stuff into memory since it only yields files when consumed. Also allows you simply implement stuff like batching, like running X requests to a server at a time, and only starting the next batch once the first one is done.