Sparkteams Blog

In fast-growing tech companies, it frequently happens that a strongly growing product team reaches its limits. How to deal with this? Do you split the product team? But that also means splitting topics and, if necessary, the code base. What to do, if...

Wenn ein Tech Unternehmen nach 8-15 Jahren langsam erwachsen wird, ist das auch der Zeitpunkt zu dem die Technologien, mit denen man gestartet ist, langsam in die Jahre kommen. Häufig gibt es viele neue, bessere Alternativen, die man stattdessen...

Cloud, Microservices, Serverless, Agile, Scrum, Lean... today there are many methods and technologies that massively improve software development. Nevertheless, many companies still fail in software development. Why is that?

Recently, we've been seeing the idea to set up a dedicated platform team in various places in order to deal with the technical debt. In the following, we take a look at the idea from different perspectives and discuss the question: Is this really...

Sharing code within your team or company is a great idea, but if you do it the wrong way, you will lose a lot more than you can gain.

In this post, I want to share my experience with runtime type enforcement in Typescript. This article is primarily focused on Typescript developers. However, the topic can also be useful for a wider audience.

It is striking that even experienced developers have difficulties in communicating the benefit of reducing technical debt well. In this post, we describe two key points that have helped us communicate technical debt more effectively.

With today's widespread concept of empowered teams, especially in the agile context, it's easy to shift all responsibility for technical debt on to teams. However, it's not that simple.

In this post, we describe seven principles that have helped to deal with technical debt more effectively.

What do Cologne Cathedral and software development have in common? When it comes to lengthy renovations, quite a bit.

How does technical debt arise? And what is it anyway? In this blog, we address three typical misconceptions that we encounter time and again when dealing with technical debt.

In this blog post, we'll take a look at the book "Working Effectively with Legacy Code" and why it can be considered a standard reference for dealing with legacy code.

Now that we all understand that boring can be good, I would like to present one of my personal favorites. Because, let's face it, which tool could be more boring than Maven?

I want to talk about how to stay enthusiastic in programming, shiny thing syndrome and choosing technology.

We show how a Gridsome-based project can be configured to support type-safe development using Typescript and Composition API while still using Vue 2.

In diesem Artikel beschreiben wir vier Szenarien aus unserer Praxis, in denen wir Camunda eingesetzt haben. Die Szenarien unterscheiden sich sehr stark in ihren Anforderungen und damit auch in der Verwendung von Camunda.