Amazon Scraps Secret AI Recruiting Engine that Showed Biases Against Women
by Roberto Iriondo — 3 min read
Distinguished Professor Stuart Evans mentioned during a lecture at Carnegie Mellon University how biases in machine learning algorithms can negatively affect our society, whether these are unconsciously added through supervised learning or missed upon audits with other types of machine learning. In this case Amazon’s AI research team had been building a recruiting machine-learning based engine since 2014, which took care of reviewing applicant’s resumes with the aim of intelligently automatizing the search for top talent.
Why Should You Invest in Security Tokens?
by John Kenny — 6 min read
Security Tokens are the talk of the town. If you are into cryptocurrency, you must have been living under a rock if you haven’t heard talk of them in the last few months.
But what are they are why should you be interested in them?
I will attempt to explain the difference between traditional cryptocurrency tokens and security tokens in a brief and simple way as well as what I think security tokens bring to the market.
2018: The Year of IoT and its Mega Trends
by Faisal Khan — 3 min read
Internet of Things has been a trending term for the past few years & it’s finally beginning to go mainstream with the advent of super fast 5G networks which would make the transfer of trillions of bits of data it produces, seem like a breeze. IoT applications are being integrated in almost every sector of the global economy with technology moving us a new phase of human evolution — Smart homes, autonomous cars, cutting edge medical technology & advanced technological systems are all around us. The following info graphic shows how we are being propelled to a digitally smart future with IoT.
Avoiding Interface Pollution with the Interface Segregation Principle
by Severin Perez — 6 min read
One of the themes that has popped up throughout our SOLID series is that of decoupling. In short, this theme argues that entities (objects, modules, functions, etc.) in a software program should be loosely coupled so as to prevent changes in one place from propagating to another. The reason this is desirable is that loosely coupled entities are easier to maintain, more flexible, and more mobile. We reviewed some of the reasons why this is the case in part 2 of the series, which covered the Open/Closed Principle, and in part 3, which covered the Liskov Substitution Principle. And yet, decoupling is so important that there is still more to say on the topic, namely, how to avoid so-called “interface pollution,” wherein classes are unnecessarily forced to implement behaviors that they don’t need. It is here that our next SOLID principle appears: the Interface Segregation Principle.
Code Reviews: Common Sources of Extreme Violations and How to Avoid Arguments about Fixing Them
by Collin Rusk — 6 min read
Knives are drawn. Blades are sharpened for conflict. A dispute rages between developers. The passions of coders are inflamed not over buggy software but over egregiously concise or verbose code. Those lines are signs of a hack. Any programmer who disagrees is an amateur. Only a neophyte would produce methods and blocks that so clearly violate good taste. Yet, differing preferences, not laws of nature, are the source this conflict and the vitriol. Hatred between developers is, in this case, the result of different inclinations towards trading succinctness for different ends. These goals, and the tendency for them, are different for every developer, leading to constant conflict in certain areas. One such place is wordy or pithy code. To minimize combat, a team can use code reviews to highlight the most egregious segments, and the group can argue over those parts instead arguing over every line and block of a code base.
DDI Weekly Selection — October 15, 2018 was originally published in Data Driven Investor on Medium, where people are continuing the conversation by highlighting and responding to this story.