Kotlin Hashing

Hashing is an important concept, it has numerous applications, and it’s at the core of many other computer science concepts.

HashUtils.kt is a very simple, yet very helpful snippet I’ve used in some of my applications when I need some basic hashing. It’s an extension function, one of Kotlin neat features.


val text = "hello"
val hashedText = text.hash(Algorithm.SHA256)


Los Cracks – Fútbol Virtual

Los Cracks – Fútbol Virtual it’s a cool game for soccer lovers, built by EPCON CCS; it allows you to choose your favorite soccer players from the Liga MX and earn points every week based on your team performance.

Challenge yourself and compete against everyone in the general group or play with your friends in private groups.

This game works exclusively with real data from Liga MX.

Available for iOS and Android.

.NET Core Exclude from Coverage

It’s great to have your code covered by tests, right? And if you’re like me, you’d like to know how much of your code gets covered, the higher this metric, the lower the chance of having undetected software bugs, assuming your tests are good quality, of course.

Sometimes you need to exclude some classes from this metric to get more accurate results according to your project specifics.

For a .NET Core project, the framework provides the attribute ExcludeFromCodeCoverage. Tag your class with it and make sure to add the import to System.Diagnostics.CodeAnalysis.

This attribute is available to .NET Core 2.0 or superior.

tired good night GIF

Flutter + Travis CI + Codecov

The term Continuous Integration has been very popular in the last years, the way we work has been evolving and distributed teams need an effective way of collaborating while ensuring the quality and fast paced delivery required by software development nowadays. This evolution has triggered the development of tools and practices for continuous integration and delivery.

By adopting CI/CD practices and tools we are able to integrate work more frequently, solve problems quickly, gain better quality on our products, help collaboration on our teams runs smoothly, make sure our team’s code is always building and stop the most bugs from getting to the users.

Fortunately, these practices are not something only the big companies and teams has access to, there are great available free tools to integrate CI and CD processes into our projects.

Here’s how to implement Travis CI and Codecov with your existing Flutter project.

1. Get your repo ready

You’ll need a GitHub repo with your Flutter project loaded up and ready.

2. Setup Travis account

Go to travis-ci.com and sign up if you don’t have an account already. After you accept GitHub authorization you’ll be able to activate Travis and select the repo you’d like to integrate

3. Create .travis.yml file

This file tell Travis CI what to do, here’s a template that should work with Flutter projects, you can start here and modify due to your project needs.

Add the file to git, commit your changes and push them to the repo, a new build should be triggered automatically.

4. Add Travis Badge

Now you should be able to check the build status of your project in Travis so why not make this info available through your repo by using travis badge.

To do this you should visit your repo on Travis and add the markup to your README file.

Now it’s codecov turn.

1. Run your tests

Make sure your tests are running and coverage reports are generating correclty. You can do this by running in your flutter project

flutter test --coverage

2. Setup Codecov account

Same as travis account, go to codecov.io and sign up if you don’t have an account already. You should accept GitHub authorization and activate Codecov.

3. Set upload step to run on travis

Edit you .travis.yml file to trigger coverage files to codecov automatically

Trigger a new build on Travis and you should start looking at your coverage data automatically

4. Add Codecov Badge

Visit your project’s page on codecov and go to Settings > Badge to get the markdown and add it to your README file.