The day-to-day work in software development is work that requires a lot of brainpower. It involves high cognitive demands and skills in which perception and attention play a special role. The problem with this is that the way people think can be distorted. A distorted way of thinking leads to thinking traps and consequently to mistakes. Anyone who has mastered a few perceptual-psychological basics can adapt their way of working and especially their programming style in a way that avoids thinking traps and recognises mistakes more quickly.

Interim and completion forecasts are just as important in large agile projects as they are in traditional projects. Unfortunately, the Scrum Guide is no help at all here and classic methods are inadequate in most cases due to the complexity of the requirements. However, simple statistics and a transparent estimation method can be used to arrive at a reliable forecast. I will explain how this works in my blog post.

Agile approaches are now very widely accepted. Scrum is often used as a framework and fixed events (meetings) are specified, among other things. Projects in the insurance industry often employ an agile approach, too. Despite that, employees and stakeholders sometimes harbour prejudices. I used to be project controller in a previous life, during which time I was involved in an agile project and was confronted with prejudices at the beginning. In my blog post, I would like to talk about prejudices and my own practical experiences regarding agile approaches based on Scrum.

CSS is short for cascading style sheet. But how exactly does the cascade work? I'll explore this topic and lead you through the CSS inheritance process on the pages to follow. You will also learn all about the different types of style sheets and how the weighting of individual selectors is calculated in detail.

Imagine the following scenario: a company wants to test its software internally without accessing external services. It goes without saying that costs play a role in this. That’s why in this blog post we are going to explain how container-based testing can reduce the costs of testing.

Even the most impressive UX design will not sell well if the user interface is no good. So in this blog post, I want to provide creative developers and UX designers with a hands-on guide.

Microservice-based architectures are a current trend for transforming information systems. But how can these architectures be implemented? The most commonly used solution is Camunda's BPM engine. In my blog post, I show you how this solution also enables microservice choreography.

Not every project has a UX designer. The requirements engineer is often asked to perform a kind of dual role – ‘they can do that little bit of UX as well, no problem’. I’d like to use this post to expand your UX horizons a little to help you understand the basics and possibly highlight a few important points to consider when designing software solutions.

‘Will a software project be completed on time?’ or ‘What costs will be incurred?’ - there are many situations in which estimates are made. However, regardless of the type of estimate, my conclusion will remain the same: I believe we should not make decisions in software projects based on estimates. There are better alternatives.