I have all of it on my keyboard: neo-layout.org

They implement the design pattern.

It sounds like they do it in a functional style rather than the object orientated one I see a lot.

It's not useless in promoting UBI given the uncritical news coverage in Germany.

Doesn't help. I just cannot center that div or make it look pretty.

I'd say it's e-dem-po-tent. Not eye, but eagle.

I am on-call for a week every ~8 weeks. I get 500 € and two additional days of vacation for it. If I do get a call, the additional hours go to my time account.

Fair deal, I'd say. Only problem is that most of the applications are from vendors, so getting problems fixed is an ordeal.

I have been working for large European utilities and even within AWS/Azure deploying something takes weeks.

Fairly certain this is true for large anythings if they haven’t been explicitly set up to avoid that problem.

Wehrmacht was mostly supplied by horses.

> DDD is against the idea of having a single unified model; instead it divides a large system into bounded contexts, each of which have their own model.

If you have a large system it makes sense to divide it into smaller independent pieces. If you have a (micro)-service architecture you have distinct services, in a monolith you might have modules.

It is a hard problem to know where exactly the boundaries between services or modules should be, in any case DDD calls the things that make sense to decouple bounded contexts.

It does not matter if function foo is reused, only if the code inside foo that is to be pulled into new function bar is.