In ~2015 I wrote a task scheduler for the sensors that covers 5 systems at two sites.
A project started in 2019 that (among other things) was supposed to replace that. They partly used my design. In 2025 they still only kind of cover two of the systems.
A couple years ago, some new projects needed to be covered as well. To avoid them being stuck in a tarpit, in a meeting I proposed a "federated scheduling" system that would farm out responsibility to the sub-projects and then the central scheduler just deconflicts/approves those requests.
Last month, some higher-ups did a study and decided that's what they want. The called a large meeting to announce it. The "design team" is me and the 2019 project head.
We are both #software #engineering and we have one #EE who can also write good #code but he's a <1y new hire who doesn't know anything about the existing systems and is petrified of making a move without three approvals
All of which is to say: I need some good resources on designing #distributed #system