Development Principles

We use these development principles to make it easier for us to make decisions and ensure we do things our way.

You may disagree, so keep in mind these are the principles we feel apply the best to Tjek. Principles can be stupefying so it's important we always question and refresh these principles.

Put People First

Always try to question what is right and put yourself in someone else's shoes when building products. Examples:

Exploit We’re a Small Team

Don’t adopt the practices of large corporations. We are a small team and we need to use that to our advantage. That means we can't just throw a lot of money and people at a problem. We need to be thinking in terms of simple, efficient, and low-cost solutions. Also: Working with boundaries are a good thing, as it usually fosters more creative solutions.

Don’t Reinvent the Wheel

Use open-source libraries and spend time searching for existing solutions instead of trying to solve them yourself. Try to spend your time in the places where we are unique and can provide value. And let's contribute to existing open-source projects instead of making our own half baked solutions.

Always Seek the Simple Solution

What does simple even mean? We define simple as few moving parts. The more parts, the more complex it is. While this is sometimes hard to do, the initial investment in finding the simple solution usually pays off in the long-run.

Our Products Should Feel Nice

Quality should be the common denominator in what we do. For example, making our apps and API's faster. It’s not good enough to have a feature if it sucks to use. Example:

Incrementally Improve

Instead of working on something for months and months, strive towards incremental improvements. We want to deliver value to people using our products continually. And we want to get feedback quickly and make small changes until we get to a point people really love.

We're Software Writers

We are writing code for others to read. Make it elegant and easy to read. Code should be viewed as a user interface.

In a perfect world the code you write should be easily readable and self explanatory. But sometimes you lack the proper context, historical reasoning, limitations in 3rd party libraries and services. Here comments can be helpful. Sometimes comments can be helpful to prime your mind and that of the reader of a complex code-block or algorithm, so that there are no ambiguities of the intent. Always consider this though: if you need to comment some code to make it understandable maybe a refactor and simpler code is the better solution?

Watch Out for Abstractions

Abstractions can be great when you need the same logic again and again different places and you're pretty sure of what functionality is needed now and going forward. Abstractions, however, can also make things unnecessarily complex. Just because you have to do the same thing twice, doesn't mean you need to abstract it away. Duplicating the code might be just as fine, if not better. Abstractions can make the code more abstract, harder to follow, harder to read, and they also lock you into a specific design that might not be future proof.

Use abstractions with caution because it can make code so much harder to read and follow. And we're software writers, writing for others to read.

Use Few Technologies and Languages

Our primary programming language at Tjek is JavaScript.

For Android, it's Kotlin. For iOS it's Swift. And in some cases we go for Python and Go depending on the use-case. Sometimes, Go is better if we need more performance.

That's it.

We prioritize using as few languages as possible because we have to consider it in a larger picture. When selecting a new programming language, we now have to support it, maintain the services using it, hire for it, teach people etc. A new language can make things more complicated for Tjek as a whole.

Also, no language is ever perfect. You might have certain issues with a programming language but switching to a new language just gives you a set of other issues. Maybe it's not the language and perhaps you just need a refactor?

Avoid Silos

In general, we strive towards as few silos as possible to foster collaboration, knowledge sharing, and better/easier/simpler technical solutions. Examples:

In practice, this is not always possible and you sometimes have to compromise.

We support Danish Red Cross