3,948 karma · joined January 11, 2012
@joeblau everywhere
1. The arrogance/confidence that people had towards AlphaGo assuming that it was not going to be competitive.
2. The lack of understanding tt even the programmers had for the game. At one point the devs were saying "I don't even know if that's a good move or not", yet their program is playing at superhuman play.
3. The amazement that commentators and other players experienced when AlphaGo performed move 37 in game 2.
4. The disappointment experienced by everyone when they came to the realization after game 3 the computer won.
5. The confusion when the computers neural network fails in game 4 and everyone (except the engineering team who sees the probabilities) is confused about whether the machines play is brilliant or terrible.
Can't Facebook just issue a takedown request and have these files removed?
shift + zz
Save and out!I'll get around to open sourcing the whole project and I'll write a proper blog post about the process I went through to build this, but for now I'm looking for feedback on whether people here think this tool is personally useful or not.
edit: Also, the the training set for teaching this model is extremely small (1700 examples) which I paid mTurkers to tag. If you see sentences that look like they should not be redacted, add them to the training data set[1].
[1] - https://github.com/getshields/newslist/tree/master/TrainingD...
code
formatting.That being said, every time promo time rolled around, I had nothing to show for it. You needed metrics and some plan of how you were going to show your manager you were performing at the next level or it didn't count. The software that I worked on over a crunch week that made the news papers, doesn't count. My managers would put me on project that didn't lead to any favorable trajectory for promotions. Every project they ever suggested, which I took up is now deprecated or severely paired back to the point where it doesn't matter outside of my personal development.
Now, I'm 4 years in and starting from zero in terms of building my foundation for working on a project that is valuable enough to the company to reach a higher role. I'm still willing to do the hard work, spend the occasional late nights, get lost in my passion of working on customer solutions, and try to have an impact. My question now is whether it makes sense to build for my company or build for myself?
1. founder starts company
2. board replaces abrasive founder with operator
3. founder fully exits company (except for 1 share)
4. founder starts new company
5. original founder company nears bankruptcy
6. founder executes reverse take over of original company
7. founder revitalizes original company
At the time, we were at step 2 with Dara becoming the CEO,
now we're at step 4.