Client has an "urgent" release that needs to be launched immediately... So they keep changing the spec every few minutes with new changes, but are upset that the product isn't launched yet. Lol. Got to love clients.

Me: Hey, guys, this stuff is seriously flammable. Like, I’m surprised it hasn’t caught fire yet. I really want to clean it up. Here’s how I’d make it better.

Management: No. It’s fine, it works. Don’t touch it. It’s getting replaced anyway. Just add the things on top like we asked you to, and call it a day.

Me: Are you sure? This is seriously going to be a problem.

Management: We just said it’s getting replaced. Don’t. touch. anything. OK?

Me: alright.

… Eight weeks later …

Management: so this thing caught fire over the weekend, and the fire spread to other areas. We’re doing some emergency cleanup. The new guy looked at it and figured out why, and has some great ideas on fixing it, so give him some well-deserved praise!

Me: Hey! I told you about this months ago!

Management: Yes. I tuned out during today’s firefighting meetings. But it’s important to strike a balance in everyone’s style. Do you have any other concerns?

Me: Why are we spending time building reports for Support? AFAIK they never read or use them.

Boss: Seems they expect you to do it.

Me: Then what exactly are they supposed to be doing? All the issues seem to just escalate back to us.... We should just make sure issues never get into PROD

Boss: I agree, they're always firefighting... we gave them more funding so eventually they should catch up **Me: I highly doubt it, you should just stop hiring monkeys** esp. if we prevent PROD issues.

Me: Yea... we should prevent production issues because someone always has to pay off the (technical) debt and interest rates in PROD are very high

For all my friends here who have known me for years can easily notice there has been a drastic change in me.

I used to be confident. That shit was hollow but I used to laugh in the face of fear. I was ignorant and that ignorance fueled a lot of the much needed confidence.

Over the years, I learned a lot. The more I know, the more I realised how much I don't know. And for all that I know, I have to use the brain power to retain and implement it, else it rusts.

This image is of my 2021 goals that I drafted last December. Wasn't able to achieve the first, the last and the art one. But surely got myself surrounded by some of the smartest people I have ever worked with.

Now they have rightly said, be careful with what you wish for.

MY CONFIDENCE IS SHATTERED.

I feel dumb. Constant imposter syndrome. While I am learning every moment and there is no measure to it, I feel incompetent to an extent that I have started questioning how did I even reach this far?!

While, yet again I am the youngest in my team, my manager is bit micromanaging and agressive with OKRs/KPIs and tech team isn't very supportive creating constant friction (something I never faced with developers in my life because devs are my best friends), I fear how much more time will I take to ramp up in this new job and feel confident enough to tackle things on my own without constant nudge from leadership or different teams?

Or is it just that I have burnt out firefighting and lost the motivation I had?

After all, what does this all even mean?

Hollyyy Shiiit
Here we go again
Unrealistic deadlines

We calling it FireFighting

I did it y'all, I just put in two weeks. Goodbye tech debt, goodbye anti-patterns, goodbye constant firefighting.

FUUUUUUUUUUUUUUUUCK I hated this day! Get out of bed to a direct fire and firefight all fucking day long, cook while firefighting, shit while firefighting, make dinner while firefighting and now I finally get to eat my fucking dinner without a laptop in front of me. I just want to scream FUUUUUUUCK so very loud but I'm a nice neighborhood. Fuck, shit cunt day. Fuck.

It's not a new year unless you spend your first day back firefighting shit that broke over the holidays 🙃

I’ve stopped caring about firefighting cause evidently, no one else cares

Do you ever feel your job is too demanding compared to other software engineering jobs?

I've worked in two companies for now.
First company, Kotlin microservices and we had QAs, didn't have to write a lot of tech specs and no post mortem or on call at all (not yet atleast), it was just talk to PO, he tells the business requirement, we work together to make tickets, no legacy code so was easy to know what to do for tech, no monolith to handle or anything, much easier, just code and meetings.

Current job is meetings with PO telling you what he wants, have to write a full on tech spec and also know business requirements and product knowledge as the current PO doesn't know anything about how the products work, writing huge tech specs, communicating on requests sent my clients on slack, pretty much always firefighting, the system is so fragile and legacy, coding is actually less its mostly spending hours finding out how this shittt legacy flows work (no docs) , PO pretty much does fuck all, just wants meetings and wants us to do very very stupid tedious low impacts projects. This bundled with oncall and onpoint and the absolute sheer amount of incidents our team is involved in (on average we have 4 a week LOL, varying size but they're all very annoying) and the overtime oncall benefit is so bad too, if you do get paged out of hours, you just get that hour back during work hours. In other companies like friends, you get paid for the whole time you're oncall, whether you get paged or not. I can't go out anywhere on weekends or anywhere at all during on call in case I get paged, which happens a lot. Its a cluster of a mess. This bundled with manager stoll not wanting to promote me to IC3 despite all I've done so far.

My question is, is this more normal than I think it is? Is this just how crap our career can be? Mind you I'm in the UK so not getting those mind boggling US wages sadly either. Have US colleagues in same team doing same job but obviously getting more

#Suphle Rant 9: verbatim exception scare

In multiple rants, I've bitched about laravel stealing suphle features. By some very weird coincidence, it appears I've been given a taste of my own medicine. Let me explain:

We're having a chat this morning on a laravel group chat when someone says he uses their notification component a great deal. Curious, I ask him what he uses it for since I only used it sparingly during my laravel days. To pry an answer out of him, I ask whether he uses them for sending app error alerts to a slack channel, and he responds with an eerily familiar term. I quickly look it up and the results on the docs are chilling: errors can be sent to bugsnag (which suphle has an integration for), sentry and Co. Errors can either be broadcast or disabled. Specific kinds of errors can be caught. My heart sunk. My brother called for something while I was going through it and I was struggling to pull myself together

Their exception component is almost identical to mine and I'm only just realising. It's shameful that I'm just learning about functionality present since 5.8. I thought my creation was novel. BUT! The good news is, the implementation differs

Too many errors went unnoticed during my time there because error broadcasting is optional. Since none of my colleagues read that part of the documentation, we were firefighting by pulling and wrangling production error logs. This informed their abolishment in suphle altogether

A relatively minor difference is in the APIs –their philosophy makes significant use of global functions, violating SRP, etc.

But the most important difference, that still cheers me up, is that they only catch known errors. Suphle has a construct for isolating calls to a decorated service. Any unforeseen error to occur during its execution will do a series of things before control is returned to the caller