Hey Nils, thank you for the change of perspective and added context.

As someone who has seen these things unfold as well I have yet one observation to add. Change is a constant with businesses as demand changes and new trends emerge, so far so good. However with these big bang changes we as — software engineers — often are forced to adapt to changes to the tools we’re allowed to use to actually build the business. That's something I'd call a false-believe within the software industry.

When you are a carpenter, you build different things with different intentions, but your tools won't change.

When it comes to software development, there seems to be a believe that not only the business has to change, but also the tools, be it the methodology or the actual tech stack.

It’s like thinking because the house you’re living in doesn’t suit you anymore (new kids or kids move out etc.), you need a totally new one built in a completely different way with a completely different set of tools.

I think this is adding extra risk as the people working on the business not only have to adapt to the change in domain, but also cannot rely on their skills and experiences. There's literally nothing to hold onto anymore!

To management the tools used might all look alike, are all the same. But take the hammer from the carpenter and give him something else and there won't be a carpenter any more.