March 2017 - From passion to profession Skip to content →

Month: March 2017

Winter has gone, spring has come. Let’s integrate it.

In the “At the red-green-refactor carousel – implementing conversion unit” post I described how I have developed basic functionalities for conversion unit. I also mentioned that there is no Spring Framework integration and why I decided to implement CU in that way. In the following post, I’m going to show you this mystic integration process.

Leave a Comment

Improving Aksesi usability – refactoring frontend

It’s been a week since the last post. In the following one, I’m going to summarize you what I’ve changed it the Aksesi since then. I decided to refactor some parts of the frontend application. Moreover, I managed to simplify installation and configuration process. The major part of integration is done “in the background” and a user does not have to care about it.

Leave a Comment

Is mixed password secure?

When I came up with an idea of Aksesi project, I started to think about its security. First thought was that it will be as safe as HTTP(s) protocol is. Realizing it, I stopped any considerations. Three weeks later I realized that this solution will be very safe or, at least, safer than ordinary password usage.

In this post, I’m going to cover a few reasons why Aksesi will be safer than classic authentication which bases only on passwords consisting of characters.

Leave a Comment

At the red-green-refactor carousel – implementing conversion unit

After having gestures handled and stored, we are ready to create simple logic for the Conversion Unit. In the following post, I’m going to describe created architecture. All of the code was written with TDD, because one of my goals for “Get noticed 2017” competition is to become more fluent in using TDD as a daily basis. Up till now, it’s going well.

The short introduction for those who are not familiar with TDD. Test Driven Development is a technique where, at the beginning, you write a test that does not compile (red part). When it is ready, then you start to write the code until it passes (green part) written test. At the end of an iteration you should look through the code and do refactoring if needed (refactor part). Good practices show that tests should be as simple as possible. In the ideal world, when a class is completed, then tests cover 100% of its lines.

Leave a Comment