145 karma · joined January 25, 2019
From the college board's description of the tool, it weights applicant scores by the quality of their neighborhood and high school. So a disadvantaged student whose family focused on moving to a neighborhood/school where lots of students succeed is not given a high score in this analysis.
The OP had the same opportunity, but because they did the traditional things for a poorer family to encourage their students to succeed (moving to a good school district and sacrificing on the commute) they will be considered a privileged student in this analysis.
I've worked at several places where the designers made a big show of interviewing/looking at data, but then could not incorporate any aspect of it into their designs. Unsurprisingly, their tools weren't used or appreciated.
I was literally the model customer for taxis. No car, disposable income, goes out drinking a lot. Even so, I actively avoided taxis whenever I could before uber hopped on the scene. It wasn't a question of money - their dispatch services actively left money on the table with their terrible, terrible quality.
Whether Uber/Lyft took out too much money remains to be seen. But the dispatching technology is an immensely profitable business by itself.
"sustainable industry" is not the term I would use to describe taxis. Their dispatch systems badly needed replacing.
Things I saw in taxis pre-uber:
- Calling a dispatcher and giving an intersection, to receive a "we don't pick up at intersections, you need a valid street address" message. This was in the city without a lot of taxis. Gee, wonder why.
- Drivers speeding off once they realized you didn't mean to go to the airport.
- Drivers intentionally using both feet to drive, so they would stay well below the speed limit. If confronted, it was in the name of "safety". Dispatchers couldn't track locations so they had no idea how long the trip should take, and weren't interested in you as a repeat customer enough to do anything to the driver.
- Multiple broken card readers.
- Generally, it was impossible to understand dispatchers. Almost every one I talked to had a thick accent beyond what I would expect from even a newer first-generation immigrant.
Everything is single threaded, but events happen constantly and at times you don't control. However there's no good atomics support. The environment uses async for pretty much everything non-trivial but has some of the worst async primitives ever (until very recently, at least).
That make things very different to develop for, and won't be solved by writing your code in Java. It will just run into the same fundamental browser limitations.
They may only be calibrated when enough of the facts are in to make predicting easier. Still useful, but not calibrated in the way the general public might think.
I genuinely have no idea what this means. What are you trying to say here? So I can be in any feeling except frustration when I'm conveying that I'm being frustrated? This sounds like snake oil.
Personally, I don't get it either. No one I'm frustrated with seems to understand that if I tell them in an unhurried, matter-of-fact way. They may say that they prefer me to express frustration that way, but it gets no results. I don't see the appeal.
By the time [Joseph Pulitzer] actually composed his thoughts for the North American Review, his bed chart included rheumatism, dyspepsia, catarrh and a bad case of shame for the Spanish atrocities in Cuba deliberately invented by his reporters to goose the circulation of his newspapers. - Michael Lewis (1)
It was a part of the news culture of the time, too. It wasn't just restricted to Pulitzer. (2)[1] Michael Lewis, "J School Confidential", 1993 [2] David R. Spencer, "The Yellow Journalism", 2007