LinkedIn and HoaxBuster

The CluedIn team are avid techies. We love keeping up to date with technologies, and kept in the loop on transitions within the market – and let’s face it – cool gadgets that we don’t need but will buy anyway. We constantly run across endless articles not only talking about the problems that we are solving but also interesting solutions that are also trying to solve some of the issues we are addressing. So when we came across this article talking about how LinkedIn and Hoaxbuster are joining teams to try fight the fallacies behind many peoples LinkedIn accounts, it definitely peaked our interest.

http://www.gizmodo.co.uk/2015/04/linkedin-joins-the-hoaxbuster-club-buys-patent-for-fact-checking-system/

The basic premise is that LinkedIn have joined Hoaxbuster in the hope of being able to validate some of the skills, education and history or a user.

I will ruin part of the surprise for you already, the article basically says in summary that this probably won’t solve anything in the end and that it is simply a small stride in the right direction.

You definitely can’t attack the idea of progress, even if it is in small strides. I also appreciate their honesty.

Our main interest surfaced due to the reason that CluedIn actually seems to be part of the solution that LinkedIn and its users may be looking for. Can CluedIn surface the education history of a user? No. Can CluedIn verify university documentation? No. Can CluedIn know the skills of a user? Yes! Not only yes, but more than any other tool on the market today. But why?

When you are at work, you use a lot of different systems to do your job. If you are a developer, you will e.g. work in Sublime Text, Visual Studio or IntelliJ. You will then commit this code to Github, Bitbucket, TFS or SVN. After this is done you will mark off tasks in TFS, Pivotal Tracker, Trello or Github. To accentuate the grandiose of the situation, you may have only fixed a small bug, however the act of using all of the systems above have indicated to us that you have some level of experience in using these different tools. The tools however are not the most important part. What is important is the content (code) that you wrote. It not only indicates the style of your coding, the practices you adhere to, but your experience in using different parts of the coding framework, the libraries you depend on and more. In fact, through our research and through the algorithms we have designed, we now know that it indicates so much more and on a deeper level.

So at the end of the day, even if you don’t use CluedIn on an everyday basis. Even if you don’t publish the results of your skills to LinkedIn from CluedIn, wouldn’t it still be interesting to see what your work tells about you? Not even a little bit?

Signup now at http://www.clued.in/signup

 

Tim Ward

Founder, Developer and Loudest Employee at CluedIn.