Interesting. Informally (anecdotally), I think the norm is quite the opposite: noblesse obliges to never drop the H-bomb in conversation --whence the irksome "went to school near Boston" trope [1,2].
It could well be a HBS-only thing, though. They have their own thing going on.
In my anecdotal experience, I only find out people I meet went to Harvard when I see them in a school sweatshirt. Or if they write for The Simpsons, in which case I just assume it. Heh.
Wharton grads, on the other hand... Never more than 10 minutes before they drop it in.
my graduate advisor had studied CS from Harvard. She never mentioned it. I got to know one day when I was going through her Bio. I mentioned it in the next meeting and all she did was smile faintly.
People with substance don't need to flash their Ivy League emblem everywhere.
Just wondering, is there a reason why twitter doesn't use one of the many distributed in-memory database solutions?
It seems like they had to write a lot of custom layering on top of it just to scale
At a certain point of complexity and scale the in-house, custom distribution layer is almost always going to outperform a general purpose distribution system built into the database.
General purpose distributed database clusters are progressing, and if Riak, or one of the other in memory cluster focused system had been stable and production ready when Twitter was developing their cache layer it might have been a strong contender.
However, Riak is still much, much slower than Redis, especially when it comes to accepting writes. Overall, when you have the money that Twitter does and the team that it has you can come up with something better in house that it is more efficient for your use case. And that's what they've done here by building on top of Redis.
At my previous company we experimented with a 12 node cluster (128GB per node) used as a datastore. At one point we had over 1 billion keys. This was back in the 1.x version where they persisted data into sqlite files so each file would have 100+ million rows in it. Persisting data took forever. Rebalancing took forever.
When it worked, it was very fast. When you lost a node, things went bad. The java client would lose it's mind trying to cope with an outage. We ended up writing a connection pool were we could just recreate our connections when we detected a node went out.
That said, it was the best distributed NoSQL solution we tried and might have improved a lot since I last used it.
This is exactly my problem with HBS. Their cases are heavily geared towards financial and exit situations, where PE/bankers will excel at. This also reflects on the fact that a lot of their students come from those backgrounds. They don't really focus on actual technology problems as much, and it would be harder for an engineer to bring their experience to the table.
Actually their cases aren't geared towards financial and exit situations. I gave those examples because I don't come from that background, and so found those illustrative of what I personally learned.
I'm a computer scientist by training, and found that my experience helps me excel in the classroom, rather than serve as a burden. Classmates do appreciate the technological perspective, and former Microsoft, Google, Apple and startup employees do a great job of giving that perspective in Entrepreneurship, operations and technology classes. Engineers are highly regarded at the school...
I bought a domain from them once.
Later during that same day, I forgot my password so I typed it incorrectly like 3 times. This automatically puts my domain BACK IN THE OPEN MARKET. I was appalled. When I emailed their support, they said I had to verify my identification by sending them personal documents -- I believe it was two pieces of ID. Total BS.
I simply bought the same domain through Gandi and never looked back.
What could have happened: I could have bought a domain and someone else could have typed my password incorrectly, losing my domain. That person could then steal my domain by registering it else where. Crazy.
This sounds like you never actually bought the domain in the first place. No one likes issuing refunds - namecheap would be flat out crazy to implement such an automated system. Not saying it's impossible, it's just improbable.
For those who are downvoting - I have a Namecheap Order Summary email so I technically bought the domain. Maybe in their system it wasn't acquired yet, but I still had the right to it at that time.
I have comment down vote capability. Maybe >1k karma and mods haven't explicitly turned it off for me or ghosted me? Probably some sort of conditional.
