You are hitting the nail on the head with the communication issues. Truth be told, I am more senior and the rest of the leadership team understands that this individual needs a lot of management and shouldn't be allowed to implement stuff on their own.
"If his arguments are shaky, he will step down from the pedestal on his own when he realises that this decision is inefficient and unnecessary." - The sad part about this person is that when presented with this type of feedback, they always double and triple down despite the facts on the board, it is really odd and risky behavior to be honest.
At the end of the day, I am the person who has to put him in his place, so I want to make sure I am not missing a major point of consideration with celery.
Oh boy this sounds like quite the situation. You obviously understand the internal affairs far greater than I, but you did say "I am the person who has to put him in his place". Not saying this is the solution but if you're the person who put him in, you're probably the best person to kick him out?
Again, I don't want to meddle with decisions involving total stangers' careers but philosophy that the CEO at my old company had (which was a startup optimising for 100x efficiency) was "hire fast; fire fast" and his startup is doing pretty well under that mantra!
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.
(The usual disclaimer: Take what I say with a grain of salt, I am just speaking from my own N=1 experience here and I am not any good at management).
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.
Thank you for this recommendation. I have heard the name before, but it slipped my mind to really dig in. I am definitely interested here though. Will start to play around and reach out if it looks promising. Do you all sign BAAs?
Sharing a blog I wrote giving a crude demo for how to bootstrap a passkey only login flow for a web app. Hoping it gives you all inspiration to push towards passkeys and OIDC because everyone still screws up MFA when applied at large enough scales.
In one step, Passkeys provide multiple forms of authentication including:
* FIDO2 based credential
* Origin verification of the requesting web app by the Platform Authenticator (this part makes them phish resistant)
* user password, because you had to unlock the platform authenticator in the first place
* device authentication, because the passkeys are stored within device bound platform authenticators
Don't let your lazy compliance people tell you passkeys aren't MFA.
Hello! My name is Jamie. I am a software engineer with a decade of experience tackling complex infrastructure and security problems. I spend half of my focus working with startups and small businesses to build, operate, and certify security management programs to be compliant with frameworks like SOC 2, HITRUST, and ISO 2700x, and the other half with my hands on the keyboard working on GoLang, Python, or Terraform codebases.
I left my last start up at the beginning of 2023 when the general market shakeup led to a change of focus for the company. I took on a role working at a security consultancy to build out their cloud practice. I enjoy the excitement and learning that comes with being exposed to many different customer environments, however, I ultimately view the position as a stepping stone to stay sharp and develop new skills until I find my next opportunity to grow and build with a new company.
Please reach out if you are looking to find a scrappy hacker who builds elegant infrastructure for regulated companies.
"If his arguments are shaky, he will step down from the pedestal on his own when he realises that this decision is inefficient and unnecessary." - The sad part about this person is that when presented with this type of feedback, they always double and triple down despite the facts on the board, it is really odd and risky behavior to be honest.
At the end of the day, I am the person who has to put him in his place, so I want to make sure I am not missing a major point of consideration with celery.