Press "Enter" to skip to content

Tag: Commutee

Week #5 – Ports and Adapters

Another week has come to a pass and unfortunately, I did not manage to work on a project at all – again. But I have some ideas that may push the progress a bit forward. As I have been on conference week ago I heard some new buzzwords, saw few interesting technologies and architecture patterns so it would be good to test them out. I’m thinking about using Consumer-Driven Contracts for designing REST API for Commutee, but it is still far from that stage of the project. For now, let’s try Hexagonal architecture! The ports and adapters approach. I will probably overengineer it, but hell, better here than in production 🙂

Continue reading Week #5 – Ports and Adapters

Commutee functional requirements

When you want to create an application, first, you have to know what this app will do. That’s a pretty important thing to know. You may know technology, know how to use it, how the user interface will look like, how data will be stored, but if you don’t know what this app have to do, you won’t be able to make it. An application must have some use cases so that users would use it for something. But wait, we know what will Commutee do, it will find me a route from here to where I want to get to, right? Yes and no. That is a general idea, but we need more than that to even start thinking about the implementation.

Continue reading Commutee functional requirements

The Choice

I did not manage to get an idea for another, third,  project, so I have to choose from those two that I described before. The choice wasn’t easy because both of these projects would be fun to do. Some of you advised me already on which one of these two do, even though I’m sure that you guys would not use it ;). And I have my own preferences in terms of which app I would use daily. But let’s look at this from another perspective.

Continue reading The Choice