25 karma · joined March 30, 2017
You said: "an interesting opportunity for someone to skip implementation of anti bias and potentially end up with a more effective model."
Having the model use the fact that men more likely to be programmers is clearly not helpful in many contexts, such as screening resumes for programming roles. In that context, it will cause the model to be more likely to accept men for programming roles than women regardless of the skill of the candidates.
Edit: Edited for clarity
EDIT: fixed typo
As a data scientist I often run code that takes hours, and getting a slack message when it finishes is super helpful, and it has often helped me catch when a script finishes too early due to some error.
I get that most of the polling error benefited Trump, and the industry needs to reflect on why that happened and how to prevent underestimating republicans again in the future, but I don't yet buy the narratives that "the polls got it wrong."
1. POC/MVP: Showing that what you want to do will work before making a full structure. 2. Creating PDF/HTML documents with code and output. 3. Exploratory data analysis and visualization.
I think many of the data scientists in the article go well beyond what a notebook is. A notebook is where you start, but should never be a production tool.
You should also consider posting this on the chess subreddit: http://reddit.com/r/chess
The company I currently work at has very few employees, and each new hire is a big cost. If a new employee does not work out, that can be a major dent in the budget. We still haven't figured out a great way to interview, and we are open to new ideas, as we have had hires who looked great on resume/interview who did not end up working out.