It doesn't provide 100% privacy from everyone, but it does provide privacy from the web service: A worker at a physical store checks your ID, and if it says you are 18, they hand you a token with a unique key on it, which they have a stack of behind the counter. You put the unique key into the web service. It's not necessarily one time use, but if you don't want to risk correlation, you can use each one only once. It's just like alcohol sales, and has all the same failure modes as alcohol sales, but if it's good enough for alcohol sales it's good enough for web services.
The problem with insider trading in prediction markets isn't the "prediction" part, it's the "markets" part. Once there is real money changing hands, then the purpose of the prediction market stops being "surface information" and starts being "make money" (POSIWID sense of purpose). Since the money changing hands is a necessary incentive for the insiders to provide the information, the parts cannot be disentangled and the problem is fundamental.
Note also that prediction markets can't be too different from financial markets because prediction markets are in some sense a generalization of financial markets e.g. you can make a prediction market that predicts the price of some stock on some day.
If 20 people take advantage of your buffer, then you are delayed by a distance of 20 vehicle-lengths + 20 follow-distances. This is about 1000 meters, a distance which you can travel in about 45 seconds. So the net effect of all 20 people merging in front of you is less than a minute delay on your trip. Unless there is an almost constant stream of people merging in front of you, this isn't adding up to more than a percentage point of two of your whole trip.
Hackers deliberately create strange circumstances, it's the primary way to find exploits. Any code that relies on a lack of strange circumstances is a time-bomb.
0.1-1% hire rate based on applicants, or based on candidates interviewed? 0.1% hire rate of candidates interviewed doesn't seem compatible with your described growth rate, even if you very conservatively assumes you spend 1 hour interviewing each candidate, thats 25 weeks of straight interviewing per candidate hired. And thats 1 hour of time across the whole company, if you have 2 interviewers spend an hour each, thats now 50 employee-weeks, or an entire year. To double the company size in 5 years, you would have needed to spend 1/5th of your entire tenure interviewing. If you go up to 10 total hours spent per candidate (including all interviewers, recruiters, and time spend in discussion and negotiation) it becomes straight up impossible.
Most people don't start shopping at grey/black markets in order to avoid paying sales tax. Most people don't pay their employees under the table to avoid paying income tax. Most people don't move or de-value their own homes in order to avoid paying income tax. Those taxes make up most tax revenue, and wouldn't get caught in that definition.
> I - and I get the impression that's true for many developers - learned early to minimize the custom config.
I get the exact opposite impression. My understanding is that as developers become more experienced, they tune their setup more, and have more and more persisted customizations. I consider sshrc[1] a critical part of my workflow for this reason.
> But why would one need that? Is your environment that random?
Most shells by default will occasionally spew out "garbage" text into the terminal like ^[[A. If you know why this happens it's possible to fix, but it's definitely a pain. Personally I consider it very important that all the places that I input text work consistently (e.g. move cursor by word, move cursor to end of line) and Warp providing that is a huge selling point to me.
It's also entirely plausible that every apartment DOES have high VOC levels, but she is the only one reacting to them. Or that other people are also reacting to them and haven't figured out why yet.
The map also explicitly lists "number of homes that would be illegal", presumably for that reason. If you make it illegal to build anything smaller than a duplex, on a lot that currently contains a single family home, the "number of illegal homes" on that lot is still zero.
We have a give and take, it's called a "protected class". It lists reasons you can't fire people and includes reasons like being black or being a woman. We can update the laws to protect people in other classes as well, but I don't see anyone clamoring to make "defenders of pedophiles" or "creeps who alienate their coworkers" a protected class.
No, it's actually undecidable. C++ templated have been determined to be turing complete, which means that template instantiations can encode the halting problem. Determining whether a program compiles or not therefore requires solving the halting problem.
In practice, compilers work around this by limiting template instantiation depth.
People continue to influence their children long after they stop reproducing. Genes that help you children have more children are selected for, so something like a gene that keeps you alive long enough to care for your grandchildren seems plausible.
What he means is that the deduction has been "priced in" to the price of homes/mortgages. In a similar story, a company I used to work for once offered employees a $x incentive to live close to the office. They then found that the price of homes in the area immediately went up by $x.
To most people, there is no difference between "your chances to to carry or possibly have or develop health issues" and a diagnosis. Sure, I suppose I can see some small technicality that makes them different, but really, the way you react to either is about the same, which makes them about the same.