How Slashscore was developed

The idea behind Slashscore started in 2017 when we were internally debating “What defines who you are” as a developer. We took this to the next step by asking ourselves, “Having so many developers with various skills around the world, what metrics would you use to determine what makes developer A better than developer B?” for your projects pending implementation.

At that time, we asked this question on several Slack channels frequented by developers, and the outcome was crazy. Some of the more hilarious answers were:

• Lines of code
• Number of ping-pong matches won
• The numbers of monitors used
• Pints of coffee consumed
• Trolls trolled

The majority of them, however, were on point and professional. They were pointing out that it would be cool if we could find a fair system that could be

• Measurable in a meaningful way
• Applicable to ALL developers in general (especially considering how much work can vary)

We’ve started to add some metrics into a spreadsheet, and then, step by step, we put an entire system in place that we called "the resume of the future for anyone who codes."

The first version of Slashcore had just one big score. As you might already know, some football players have a higher rank in defense, others have higher ball-control skills, and still others are better at scoring goals. It can be the same with developers. Some of them are really good professionals but lack communication or soft skills, or the other way around.

This determined us to split the score in version 2 into four categories-professional, extra, community, and community.

We were pleased to discover, after launching it, that there are many developers who have both.

Made by Developers for Developers

It’s about time we tell a new story about developers.

See, being a developer is like a sport. Now we may not hit baseballs, but we do smash cables and monitors :), which requires a great deal of passion.

A great boxer always has someone guiding and assisting them in their corner. They are indispensable. A great developer needs Slashscore to do more, become more, reach their full potential, and show how valuable they are and how they affect the ecosystem.

Many people believe that being a great developer is a natural talent. But this is a misconception that must be destroyed.

The best developers are not born, they are made.

Does it take hard work? Well, yes. Will it take late nights or early mornings? Yes! Will it take courage? Yes!

Software development is one of the most important activities of our time, and great developers are needed now more than ever.

So let’s turn the page on the old ways and create a revolution of great developers. Let’s stand out, let's be different, and show the world what we're worth.

As Slashcore is built by developers, each feature was created with a “we are building this for ourselves” mindset. Because of this, we'll always care deeply and understand intuitively what our audience values.

We know what core problems developers are facing because we’ve faced them too:

• Need to realistically auto-evaluate their own activity.
• Need a platform that also assesses their human skills and devotion to knowledge sharing.
• Need a platform where to add all the info in one single place in a well-arranged manner to give them real leverage in discussions with technology partners.
• Need a product that shows WHO THEY ARE AS DEVELOPERS.

We promise that wherever Slashscore continues this amazing journey, the model of dev-centricity will be forever in our hearts.

What kinds of challenges can Slashscore help solve?

Being a software engineer is not without challenges, regardless of how many years of experience you accumulate. In fact, each new level of experience can come with a whole new set of challenges related to the tools of the trade, code quality, work values, and many others. This can make it difficult for developers to evaluate themselves, which in turn can diminish their value when hunting for a job.

Slashscore has been developed as a self-assessment tool to analyze and combine activity statistics from multiple relevant and undisputable sources. In doing so, the platform offers software engineers a helping hand not only when looking for a new professional challenge but also when comparing their performance to other peers.

It offers an objective way to self-evaluate by bringing together information from web-based version control repository hosting services (GitHub, Gitlab, Bitbucket) and community websites (Stackoverflow, Medium, Meetup, Reddit, and others).

What are the benefits of the Slashscore developer modules?

Slashscore profiles take into account three different perspectives, based on professional activity, community contributions, and spare-time hobbies. Our algorithm calculates the Professional, Community, Extra and Popularity scores using integrations with several platforms.

When it comes to the Professional score, we rely on integrations with GitHub, Gitlab, Bitbucket and Wakatime. The Extra score is based on activity on Medium and Dev.to. The community score is based on activity on StackOverflow and Meetup while the Popularity is based on integrations with Twitter, YouTube and Reddit.

Ultimately, Slashscore is meant to help developers:

• To shape their professional views by learning from actual people; They can get a better picture of what's going on, their feed is populated with really interesting articles, projects from other developers from their network, meet-up recommendations, and so on
• To interpret their expert profile beyond technical skills, adding value and meaning to their capacity by having all the information at hand in a well-structured, up-to-date manner.

If what you’ve read up until this point resonates with you or with a software engineer that you know, all that’s left to do is to join Slashscore, to also see in practice how it works.

LAUNCH SLASHSCORE