jprosevear

Solid Queue (by default actually) uses a second, segregated database for the queue. You can scale it independently of your app database.

I would agree, but the manager probably should be in touch enough that they could see the teaming behaviour themselves.

And ultimately every ORM allows raw SQL if you need to fallback

How does this differ from NotebookLLM

Have a process that is structured but not bureaucratic and can be automated over time - people tire of manually upholding process.

One of the challenges with this approach is answering "how much will it cost" and "how long will it take" - that being said, its often hard for non-developers to articulate exactly what they want without connecting it to something more concrete in the form of user interface.

Except if you don't actually know what to do, or even what concepts to apply. This is where I see many start ups fall down.