Tangentical, but relevant for complex systems and organization of them and their code: I’ve started to look at BPMN, a thing I used to shun (bloated java enter

Tangentical, but relevant for complex systems and organization of them and their code: I’ve started to look at BPMN, a thing I used to shun (bloated java enterprise junk that just slows coding down), as a way to actually help organize code. If you have a process layer on top that describes exactly what is supposed to happen and you organize code accordingly it makes changes to complex systems easier to reason about. I know there’s a lot more to it than this, but in my mind concepts from domain driven design, minimal service scopes and a de-coupled process layer really can help. I guess this is why “tech” versions of bpmn-ish like systems have appeared with for example netflix conductor, uber temporal/cadence. Split stuff up in relevant domains and describe their relationships and processes. Try to stay away from massive code bases spaning domain boundaries if possible. No silver bullets anywhere ofc, but this is currently a topic at my employment this very moment. :)