As a DDD (Domain-Driven Development) person, I like to be able to read the code as I read a book. This is of course very hard, but something that I strive for. Therefore I often use the builder pattern for unit tests.

Independent IT Professional
As a DDD (Domain-Driven Development) person, I like to be able to read the code as I read a book. This is of course very hard, but something that I strive for. Therefore I often use the builder pattern for unit tests.
Are there any good reasons to not continuously work with a system’s architecture? I don’t think so.
This year's hackathon at Systemite is now finished! The challenge trophy is handed over to a new winner, Thorsten Jakobsson, and we've had 24 hours with a lot of fun!
When I've tried to learn more about functional programming, I've always felt that something is missing. There is a lot focus on the functions themselves, but less on where to put them in a structure.
From my perspective, micro services (either compiled together or completely separated) is the only way of making a system survive over time. Even the most modern, high tech technology eventually gets old-fashioned, and if we don't want to completely rewrite the whole system every 20th year, we have to split them into smaller units.
I found it rather common that developers have only a vague idea of what business logic is. I also sometimes find it hard to describe it myself, even though I've spent many hours of my career working with it.
This is a pod about the developers' perspective of how to succeed with a project. Which roles should the team consist of and what do we expect from the project manager.