1,048 karma · joined February 28, 2012
I would pay money for this in the safety amusement park, but in real life way more people would get hurt operating the fake one at the airport than we'd help in real emergencies. Plane crashes where the emergency exit gets operated are so rare they effectively don't happen.
For context, "In the 2025 incoming class, this group constitutes roughly one-eighth of our entire entering cohort."
39% got this right:
Round the number 374518 to the nearest 100
34% got this right: Find 13/16 ÷ 2.
2% got this right: If a=-2 and b=-3, evaluate ab² - a/b
https://senate.ucsd.edu/media/740347/sawg-report-on-admissio... page 49Still it's 3 to 4 cruise ships a month according to that article and, while probably hugely dirty, I would be surprised if the asthma rates of kids in affluent Greenwich and Blackheath are among "the highest in London" because of this.
Wait, what? There are no container docks in London. The nearest container port serving London is Tilbury, near the coast. Occasionally a single cruise ship moors in the Pool of London against the HMS Belfast, but that's happening only one this month, for 12 hours on April 7, according to the Tower Bridge lift schedule: https://www.towerbridge.org.uk/lift-times
The disclaimer amounts to "we're not insider trading and we really believe this stuff" many different ways. Insider trading is illegal so they are scrupulously careful to stay away from MNPI (and want you to know that). Really believing this stuff is important because if they turn out to be wrong, it's sort of ok to be honestly wrong, it's not okay to be knowingly wrong and put out the report anyway to manipulate the stock.
And so paragraphs and paragraphs of
>"Reports are based on generally available information, field research, inferences and deductions"
We're not insider trading
>"Our opinions are held in good faith, and we have based them upon publicly available facts and evidence"
We really believe this stuff, also we're really not insider trading.
> "We conducted research and analysis based on public information in a manner that any person could have done if they had been interested in doing so."
Did we mention we're not insider trading?
Found this helpful comment about the background and timeline https://news.ycombinator.com/item?id=38417192
The battery API was rolled out by all the major browsers between 2012 and 2014 as a way to let web pages avoid doing compute-intensive stuff on low battery, but it was pretty much immediately used for fingerprinting as the battery level number was so precise that if you hit two web pages at the same time, the battery level was as good as a cookie. Firefox and Safari/Webkit disabled it in 2016 but Chrome just capped the precision at two digits.
But 1 in 3.5... idk, if you assume households with kids have a couple of kids, that's getting pretty close to saying the median UK household with a 9 to 18 year old has a 50+ hour caring situation. I don't see that being invisible.
> Not immediately clear if "caring for family members" includes older children caring for younger children, but that would certainly bring up the numbers.
Suspect this is basically right as well.
Without quibbling with this basic directional correctness, the numbers in the article are bunk.
> "In the United Kingdom, about a million young people under 18 years old spend more than 50 hours a week caring for family members"
There are 14 million people under 18 in the UK [1]. If 1 million under-18s spend 50+ hours caring for family members, and only a few thousand tragic cases are under 9 (as the article claims) then the claim is that something like 1 in 3.5 children aged 9 to 18 spends 50+ hours caring for family members?
[1] https://data.unicef.org/how-many/how-many-children-under-18-...
157 had chicken pox, 47 had enterovirus, and 194 were negative for all four viruses tested.
That's not the distinction. Good software engineers solve problems. That's what the paycheck is for. The distinction is whether code has to be maintained.
It's the scientist's job to solve a specific problem at a specific time. Who cares if the metaphorical wood rots next winter, the paper's been published.
It's _often_ the software engineer's job to build things that deliver business value over years, evolving and expanding requirements, in a development team, without grinding to a halt under the weight of accumulated complexity.
"Quality" software engineering is just heuristics for keeping the pace of change high over time without breaking things.
When I was in high school in a US suburb, if you wanted a pair of jeans, you had to take an hour out of your day, get in your polluting car, drive to the mall, go to Old Navy or someplace staffed by real human beings at all times (and there were thousands of these places stores selling the same live cookie-cutter experience staffed by live people).
Now, the postal service does more work and more clothes get destroyed but how many person-hours does it take for society to bring you a pair of jeans? How many pollution-units? Surely less than it took when everyone had to drive to central place and do a transaction with a person?
Oh man, purist side quests like this are exactly how I would procrastinate a philosophy dissertation. But building a complex process for _reproducibly_ handling the once-in-a-lifetime event of accepting your dissertation examiners' signatures is taking it to a whole other level.
Where do you drive where the speed limit is 85 mph?
He says he regretted implying that he dropped out of Harvard College.
Isn't the article assuming you already are a practitioner?