I empathize with this so much. Burned out a few years back writing an admin panel mobile app for an embedded device. The actual panel and the interaction with

I empathize with this so much. Burned out a few years back writing an admin panel mobile app for an embedded device. The actual panel and the interaction with the device was fine, it was the insanity of the customer architect who only had time to design the system but not build it. You'd think that would have informed them on their excessive creativity, but alas. One use case was that an operator working with a device could at times need external support. One feature was to be able to dial support from the phone whilst using the app such that the operator could receive instructions, or have support remotely change settings for them. At least, that's what I thought. That would make sense. But no. They wanted a full real time socket connection between the hardware, the mobile app, a server, another server and the support app. Important detail is that operators often worked in areas with bad reception. This meant ensuring that all these connections were up at all times, with error handling, ensuring that messages were delivered and the gist, whilst simultaneously serializing and deserializing these messages and running whatever algorithms over them, often calling other services written in node that would take ages to respond if they didn't just timeout completely (30s!). Oh, and they wanted to sell this forward so everything, everything, needed to be customizable. Every meeting with said architect and he had new ideas, new protocols, new solutions. Eventually I needed to fix a bug in their code, which turned out to be a 15Gig monorepo where 1/3-2/3 of all code was commented out. You can imagine what the final product was. Which was rolled out to everyone on day one without any testing in live environments. I'm tired just talking about it.