> It seems extremely trivial to me to run a service that polls the queue for new messages and dispatches the jobs on its own from there<p>Are you handling retries, timeouts, disconnected clients, logging failures, dealing with perma-failing jobs, priorities, execution metrics, etc.?<p>You may or may not be interested in those features, but that's why projects like celery exist. It's not "extremely trivial" to replicate them all. If you have only extremely simple tasks that you don't critically depend on, that's fine to use simple solutions instead.<p>If you want a constructive discussion about things like that, the questions are: what problem are we trying to solve, what features we need today/soon, how long will the implementation take, what is the risk in not changing anything.<p>> Every time one of his ideas is implemented it turns into a flaming bag of complexity dog shit<p>How sure are you it's due to the idea itself rather than due to the implementation? If it really is due to the ideas and it repeated, that's a management problem more than that person problem. Maybe start chatting to them?