adesso Blog

In general, a professional programmer is someone who has a high level of expertise in one or more programming languages and is able to utilise that expertise to design, develop and maintain software systems or applications. When do most people begin their profession? How long do they work in their profession? How do they train, and which programming language pays best in terms of salary? We will answer these questions in our blog post.

Are software developers simply ‘manufacturers’ or engineers? Should new software just work, or should it add value, too? This blog post will introduce the Manifesto for Software Craftsmanship in order to answer these questions.

Clouds are changing the way we run and develop software. Many of the limitations that used to exist are no longer an issue when we embrace cloud-native approaches. This, together with new influencing factors such as costs, has an impact on our software architectures. In my blog post, I will explain what new services the cloud provides.

When you think of legacy code, frustration, a fear of change and having to deal with disproportionate amounts of complexity immediately come to mind. Having an in-depth analysis is a must if you want to get an overview of your legacy system. In my blog post, I will explain how to do this using the analysis tool at|analyze and a Neo4J graph database.

In the first part of my blog post on recurring tasks in Planner, I showed you how to set them up. The second part of this blog post is all about adding tasks of categories and creating the necessary conditions.

MS Planner does not (yet) natively offer the option to create recurring tasks. In my blog post, I’ll be describing how you can achieve this by also using Power Automate and expand the flow with additional features.

Low-code development platforms are becoming increasingly popular with companies because they enable them to create applications independently, even if they have little or no programming knowledge. In my blog post, I’ll describe the origins of low-code, explain how it works and list important considerations for its implementation.

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.