In the past months, I have asked myself a lot why we always strive to write perfect code. Picking up coding again for an internal project made me realise our team (and probably a large part of the rest of the software development world) spend a lot of time on...
It is quite easy to see pair programming as using double the resources for writing the same piece of code. If wrongly applied, this might even be the case, so why do experienced pair programmers feel like it is more efficient than working on their own? Let’s take a...
Most developers are familiar with the concept of imperative and declarative programming. Imperative programming is when you provide the program with the exact steps to achieve the output with an emphasis on how. Declarative programming is a coding style where you focus on what the piece should achieve with less...
Back in 2016, we wrote about our company benefits for the first time. With being honest as one of our fundamental company values and the impact of employee benefits on happiness, we don’t see a reason in keeping them secretive. Here is a detailed and updated look at the...
Why immutability? When working on a React application that needs to handle state, one of the main pitfalls to watch out for is accidental mutations. This is fancy talk for mistakenly modifying stuff you didn’t want to change: let user = { name: "foo" }; let updated = user; updated.name...
For the record: I started writing this blog post laying next to a nice blue pool. The pool and the rest of the quite amazing resort is situated in Kos, Greece. Together with the rest of the company, I was enjoying the retreat that madewithlove organises each year for its...
What is Prettier? Originally from the Javascript ecosystem, Prettier is a code formatter which means it takes your code and makes it – as its name suggests – prettier. There are code formatters for many languages; even Javascript has quite a few of them. Prettier, however, is currently one of the most...
In an ever-changing industry, it’s important to constantly keep re-evaluating your own methods and processes. Do they still serve the needs of today? Are you trying to solve yesterday’s problem? Are you setting yourself up to tackle tomorrow’s biggest issue head first, or are you digging yourself...
Most software engineers are aware of the fact that pair programming can have some huge advantages. It’s one of the most efficient ways to share knowledge, it gives you an almost instant feedback loop, and it results in higher quality, less error-prone code. Pair programming can be draining though....
