Ask HN: The Worst Engineer I Know Is Demanding We Start Using Celery (Python)
I work with an engineer who consistently advocates for terrible architecture and design patterns with a ton of confidence. Every time one of his ideas is implemented it turns into a flaming bag of complexity dog shit, and everyone else is left holding the bag to clean up.
His new tirade is demanding we start using celery to solve every problem we have. I instinctively want to dismiss him out of turn given his previous track record of thinking himself into a pretzel, however, I don't want to fall into a trap myself of negative thinking.
The way I see it, we would already be sending async job messages to a durable queue like SQS. 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 (as I have a done with great success a number of times in other environments). What is the benefit of pulling in all the complexity of celery for these simple asynchronous tasks?
His new tirade is demanding we start using celery to solve every problem we have. I instinctively want to dismiss him out of turn given his previous track record of thinking himself into a pretzel, however, I don't want to fall into a trap myself of negative thinking.
The way I see it, we would already be sending async job messages to a durable queue like SQS. 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 (as I have a done with great success a number of times in other environments). What is the benefit of pulling in all the complexity of celery for these simple asynchronous tasks?