|
|
|
|
|
|
by theorlandog
492 days ago
|
|
|
That's definitely the core point. To this guys credit, he figured out that in the 2020's you don't need to be technically correct to sell solutions; you just need to liter your documentation with emojis and horse shit to win people over. I just want to make sure in this case, I'm not missing out on some super special sauce or advantage that celery provides. Consuming a queue seems trivial that I am worried I am missing something. |
|
|
To me the discussion about Celery vs polling the queue didn't seem like the core theme, in that they are different tools with different trade-offs and you most likely can end up solving the problem with any of them even if you pick the wrong one (and learn from it!). Rather the problem seems to be that you think that your team is picking the wrong tool and you have no power to change it, and you feel that there isn't going to be any consequence, change, reflection or learning whatsoever if/when that's shown to be the case because you have been there before.
At least for me this was a pretty big component in burning out in the past, I put a lot of care and effort into what I do, so when I felt that someone else was continuously and stubbornly making bad decisions and I had no mechanism/leverage to push back against that, it caused a lot of resentment and burned me out.