This article made me _really_ curious what manner of awesomeness is going on at Two Sigma, but couldn't figure it out from the website. @spf13, any pointers on where to find a good article on why TS is cool?
Can’t speak for two sigma but I work in a similar company. They are generally only open enough to hire people, there is a huge competitive advantage in sharing as little as possible. Lots of finance firms have a bunch of interesting problems, from scaling to security and many are getting better at treating engineers well. But usually it comes down to the fact they pay really well.
Spf13 is leaving Google
71–80 of 179 posts
Re: Spf13 is leaving Google
#72Earlier quoted context omitted.
Two Sigma is notoriously tightlipped about everything. This guy's short post about interning there in 2015 is probably the most I've even seen about working there: https://evjang.com/2015/08/17/internship-experiences.html
In terms of "tightlippness", they don't come close to TGS Mgmt. All of their employees can't even list their employment at TGS Mgmt on LinkedIn.
It was more common than you may have realized.
Re: Spf13 is leaving Google
#73This article made me _really_ curious what manner of awesomeness is going on at Two Sigma, but couldn't figure it out from the website. @spf13, any pointers on where to find a good article on why TS is cool?
One of the few places that will pay competitive to GOOG.
They pay _interns_ $70 per hour
Re: Spf13 is leaving Google
#74Earlier quoted context omitted.
I'd hope so; it would be pretty damn embarrassing if you couldn't do a slightly advanced fuzz buzz.
A tree is just a type of graph. A graph can be represented as an adjacency matrix. So come up with that matrix, then drop it into lapack for inversion. Lapack is well optimized so this is probably a very good solution.
Re: Spf13 is leaving Google
#75Earlier quoted context omitted.
One of the few places that will pay competitive to GOOG.
*Much better than Google. Two Sigma is one of the top paying companies: https://www.levels.fyi/leaderboard/Software-Engineer/Entry-L... They pay _interns_ $70 per hour
Re: Spf13 is leaving Google
#76Two Sigma (and others) have been poaching senior level google talent at a quicker and quicker clip. Very exciting to watch the exodus happen!
Hedge funds/hf trading companies can't compete with monopolies in printing money. I wonder how they are getting all these people.
Re: Spf13 is leaving Google
#77This article made me _really_ curious what manner of awesomeness is going on at Two Sigma, but couldn't figure it out from the website. @spf13, any pointers on where to find a good article on why TS is cool?
One of the few places that will pay competitive to GOOG.
Re: Spf13 is leaving Google
#78Earlier quoted context omitted.
Wow! Jealous much. His LinkedIn says he started at MongoDB in 2011. The first commit to Hugo was in 2013, a full two years later. Your story doesn't add up at all.
Jealous? NO. Someone just needed to finally call him out on his bullshit. He left in the middle of 2014. He was checked out for a long time. I'd say that timeline adds up pretty nicely. So while Steve would like take credit for Mongo's enterprise adoption he barely had anything to do with it. Not with the Server, not with Cloud, not with Sales, Marketing or Education.
We all contribute to poop. Our level of contribution to said poop does not diminish that, in fact, we all work on poop so we’re all in the same poop boat. Take it easy on each other, and reserve the bullshit calling for those who really earn it, like the folks who initially built the poop you’re claiming by cleverly offshoring their minimum maturity on the financial and sweat equity of every early adopter. Like, say, for example, for no particular reason, my team at the exact time you’re arguing about.
It’s fine, though, I get it, that’s valley capital, fake it until you make it, give us ops teams ulcers, we make goodish money. Just weird to see resentment over who can claim MongoDB success with that kind of perspective is all. Particularly since the success at the time was all lazy developer mindshare (no disrespect, I’m lazy too), and the technical weaknesses started a few ten-year roadmaps that are now in the market and obsolete MongoDB.
Re: Spf13 is leaving Google
#79> I led the team that designed MongoDB’s pioneering user experience As someone who has used mongo, genuinely curious about which part of the user experience is being highlighted here. Thanks for all your work with the Go community and good luck with the new team!
Let's break this down and I'll explain why he is a total liar and bullshit artist.
This makes it sound like he designed the mongodb query language. Only he could pass off inflicting the crappy Drupal website as designing MongoDB's pioneering user experience. He can't be talking about MongoDB the company, it was 10gen so obviously insinuating it was the DB.
The entire Driver and integrations ecosystem had to be cleaned up. His mess. Was barely ever in the office.
MongoDB user manual? You mean the book that Kristina wrote - who worked on the Server team and had nothing to do with you.
Re: Spf13 is leaving Google
#80Earlier quoted context omitted.
A tree is just a type of graph. A graph can be represented as an adjacency matrix. So come up with that matrix, then drop it into lapack for inversion. Lapack is well optimized so this is probably a very good solution.
I haven't thought about this before, but I can't see how this would work. Instead, you'd convert to an adjacency matrix (with edge directions by only populating the upper rectangular region), then transpose the matrix, then convert back to a graph. The transpose should swap the i, j pair edge directions. Matrix inversion is super-expensive and I think it would produce somethign else entirely, probably not unlike matr…