More from Simon DeDeo
As a dean of a major academic institution, I could not have said this. But I will now. Requiring such statements in applications for appointments and promotions is an affront to academic freedom, and diminishes the true value of diversity, equity of inclusion by trivializing it. https://t.co/NfcI5VLODi— Jeffrey Flier (@jflier) November 10, 2018
We know that elite institutions like the one Flier was in (partial) charge of rely on irrelevant status markers like private school education, whiteness, legacy, and ability to charm an old white guy at an interview.
Harvard's discriminatory policies are becoming increasingly well known, across the political spectrum (see, e.g., the recent lawsuit on discrimination against East Asian applications.)
It's refreshing to hear a senior administrator admits to personally opposing policies that attempt to remedy these basic flaws. These are flaws that harm his institution's ability to do cutting-edge research and to serve the public.
Harvard is being eclipsed by institutions that have different ideas about how to run a 21st Century institution. Stanford, for one; the UC system; the "public Ivys".
This is the first deletion, back in 2014. A bit hard to read between the lines, but the basic story that an admin had Stickland's page "speedy deleted"—i.e., deleted without debate. The method was something called Copyright Jujitsu.
In particular, the admin had the page deleted not because of notability, but because it included a photograph of Strickland that had ambiguous copyright status. This is a method that people developed to get rid of content they didn't want, but also didn't want to debate.
"Copyright Jujitsu" because it is usually used against spam from companies; a PR officer uploads promotional material to Wikipedia. Instead of debating whether it's neutral, the admin can say "we'd love to have it, but the material appears to violate your company's copyright".
Usually the PR office and the IP office are separate in a company, and the idea of releasing promotional material under public domain is such a legal nightmare that the PR person goes away.
You May Also Like
Ironies of Luck https://t.co/5BPWGbAxFi— Morgan Housel (@morganhousel) March 14, 2018
"Luck is the flip side of risk. They are mirrored cousins, driven by the same thing: You are one person in a 7 billion player game, and the accidental impact of other people\u2019s actions can be more consequential than your own."
I’ve always felt that the luckiest people I know had a talent for recognizing circumstances, not of their own making, that were conducive to a favorable outcome and their ability to quickly take advantage of them.
In other words, dumb luck was just that, it required no awareness on the person’s part, whereas “smart” luck involved awareness followed by action before the circumstances changed.
So, was I “lucky” to be born when I was—nothing I had any control over—and that I came of age just as huge databases and computers were advancing to the point where I could use those tools to write “What Works on Wall Street?” Absolutely.
Was I lucky to start my stock market investments near the peak of interest rates which allowed me to spend the majority of my adult life in a falling rate environment? Yup.
2 Research conditions are theoretical and/or idealized. A huge problem for so-called NLP or AI startups with highly credentialed academic founders is that they bring limited knowledge of what it takes to build real products outside the lab.
3 A product is ultimately a thing that people pay for - not just cool technology or user experience. But I’m not even talking about knowledge gaps in go-to-market work. I'm talking purely technical gaps: how you go from science project to performant + delightful user experience.
4 Most commoditized NLP packages solve well-understood problems in standard ways that sacrifice either precision or performance. In a research lab, this is not usually a hard trade-off; in general, no one is using what you make, so performance is less important than precision.
5 In software, when you’re making something for real people to use, these tradeoffs are a big deal. Especially if you’re asking those people to pay for what you’ve made (can’t get away from that pesky GTM thinking). They expect quality, which includes precision AND performance.
2/ Sales is often viewed as either a saving grace or proof that the product isn’t good enough (because it should sell itself). Neither are ever true. Some common mistakes that result in...
3/ Mistake 1: Hire a sales rep before reaching product/market fit to get your initial batch of customers. This is a mistake because founders need to work through their MVP with early adopters to truly understand what it is they’re selling.
4/ Mistake 2: Reach product/market fit, need to scale, and rely entirely on self-serve. For enterprise products that require big commitments and internal shifts, almost no product is self-explanatory enough to sell itself.
5/ Mistake 3: Make a first sales hire who isn’t scrappy enough to help mold the sales process from scratch. Some salespeople are amazing at their jobs, but not cut out to establish the processes that others end up following. This skillset is what @rdedatta calls a “sales ninja”.
This limitation, which is still found in the very latest Windows 10, dates back to BEFORE STAR WARS. This bug is as old as Watergate.
When this was developed, nothing had UPC codes yet because they'd just been invented.
Back when this mistake was made, There was only one Phone Company, because they hadn't been broken up yet. Ted Bundy was still on the loose. Babe Ruth's home run record was about to fall.
When this bug was developed, Wheel of Fortune hadn't yet aired. No one had seen Rocky Horror. Steven Spielberg was still a little-known directory of TV films and one box-office disappointment. SNL hadn't aired yet. The Edmund Fitzgerald was still hauling iron ore.
WHEN THIS STUPID MISFEATURE WAS INVENTED, THE GODFATHER PART II HAD JUST OPENED IN THEATERS.
So, why does this happen? So Unix (which was only 5 years old at this point) had the good idea of "everything is a file" which mean you could do things like write to sockets, pipes, the console, etc with the same commands and instructions.