I'll bet my left nut this thing is not going to solve my issue 😞

Hey everyone,

During some backend improvements to the devRant infrastructure, some of our async queue processors (SQS) stopped working which caused many notifs to not go out/stop working. Unfortunately our alerting didn’t pick up on this since there were still queues being processed (just not specific ones) and some aspects of notifs working. Big apologies for this issue!

It is now resolved, and while very delayed, no notifications were lost and all were processed after the queue processors started up again. Sorry for the bulk notifs, but we wanted to make sure all that were supposed to go out went out.

Additional alerting will be put in place to prevent this from happening again.

Thanks for your patience!

Manager: Does anybody having any money saving ideas?

Dev: By switching our supplier from X to Y we could save $10,000/year and they have much better customer service.

Manager: So? I’m looking more for savings opportunities in the +$100k range. That’s a small idea, I’m looking for *BIG* ideas.

Dev: Do you have any big ideas?

Manager: No, but I really really want to save big money like that. I thought you would have something worthwhile.

Dev: $10,000 still a lot of money

Manager: I guess…. Ok we can do it. But don’t bother me with peanuts like this again.

Dev: ??? You asked me buddy

Manager: I like nested ifs

Dev: They can be difficult to maintain

Manager: No they aren’t I write them all the time!

Dev: Have you ever maintained one?

Manager: No, I don’t do code maintenance. I don’t have time for it.

Those unit tests can be commented out, they’re failing right now.

Jr. Dev: We got an issue in prod.
Sr. dev: Okay, what is the issue?
Jr. dev: Don't know, just got an email.
Sr. dev: Did you check the service?
Jr. dev: Which service?
Sr. dev: What have you debugged so far?
Jr. dev: I explained you the issue and waiting for your inputs.

😑😑😑😑😑

HR sent around updated contracts asking everyone to sign them since the company changed its name, fair enough.

In the contract it stated "Your normal place of work will be X" - only X was many miles away, and I'd never worked there, never planned too. Assumed it was a mistake, sent it back. HR refused to change it, stating that the "normal place of work does not need to be the place where you normally work."

A lot of back and forth entailed, I refused to sign, I was reprimanded for not doing so, I was asked what my problem was as it made no material difference, and then I eventually replied with:

"Angela, I'm refusing to sign this as it's factually incorrect. No further explanation is required. I'll maybe consider signing this if you sign a piece of paper declaring you believe the moon is made of cheese, and you're the cow the milk came from to make it."

A very strongly worded email came back about how this was going on my record, I needed to offer a formal apology, etc. - all cc'd to my manager. I replied back, again copying my manager in, stating that this was ok, as I couldn't remain at a company who forced employees to sign dodgy contracts anyway.

Problem was (for them), I was a *massive* single point of failure for them at this point owing to some others leaving with no handover - hence I knew I wasn't going to be the casualty here. My manager flipped the lid at HR, got the CEO involved on threat of *him* leaving, and the whole thing massively blew up. Happy ending in that the HR person in question was fired, everyone else's contracts also had to be redone (I assumed everyone else just signed without looking which is worrying), and I actually got a pay rise out of it when higher ups realised the massive single point of failure I was.

But damn, I would've walked over crap like that. Walked pretty soon after anyway!