@cho-uc this is bizness

Keep giving interviews, learn from your mistakes and repeat.

It's only a matter of time when you crack the next one.

@dIREsTRAITS i was in a project like that. Oh the horror 😨

Push for hiring new talent, or a consultant to help with refactoring.

Raise an alarm about underlying issues and escalate asking for help

Or , spend 10+ hr workdays and solve everything by yourself .

The latter is guaranteed route to a burnout .

He skipped a bullet if u ask me , good luck to you

I would sometimes say yes the bug is fixed and do it few days after ... in most cases , neither the client nor the pm actually care about the "critical bug" that needs to be fixed asap

I think it's upto the junior dev to decide , some guys don't mind a intrusive senior guy meddling their code while some stand their ground and push back

Its a matter of preference and boils down to how close of a bond the senior and junior guy have

I don't think subjective opinions and practices like such should be generalised @alexbrooklyn

I usually give up after 2 exchanges .. it's a lost cause

@alexbrooklyn ocd

Escalate the fuck out of it

I used to be the quiet guy untill I realised I've turned into the scape goat and the punching bag for the entire team

Send an email for every PR - cc every fucking guy - send gentle reminders , send friendly reminders , become really aggressive - that's the only way to fix this

I know it might be out of your nature. But I think it's better to adopt that style of work than to lose your shit all over something that's not in your control

If it still doesn't get approved , go ahead and fucking say that you're done with your task and forget about it .

If questioned send the barrage of emails and reminders as a proof of work and let the concerned party deal with it

May I know what does SE stand for ?

Idk if scaling up is the right solution ... But that's just me

So when user clicks a button I assume it triggers a rest call to your backend

If your backend is already under stress and is not having enough resources to accept the request ... Can it not just throttle it ?

You can embed some exponential retry in your client layer when api gets throttled

Sure your user will experience latency but from what i experienced the request will still not be lost

Make tech tutorials on YouTube

Cheers my fellow workaholic friend ... I would have done something similar too if i was in your place

Shouldn't apps like such have a dedicated sre in place who can assist with urgent issues ?

Which company is this ? Just asking because I'm curious ... Don't feel pressured to share incase you want to remain anonymous

The company can't really control how you implement a feature , they're really concerned about what value it delivers and how it can be monetized

It boils down to you as a professional to call out the drawbacks of big ball of mud and whether or not you want to clean it up

Superimpose both and you'd get a team of fullstack devs

Jokes aside , Isn't this a facade pattern usecase ?

I can't help but wonder how many devs waste their time pondering over decisions like these ... Only to realise it doesn't matter in the long run

Hear you brother, hope things will turn around for you soon

The sheer amount of jokers in this industry is appalling

Worst part is when they ask how long till completion

Why don't you measure the number of words in my commit and divide it by 60 wpm . And then question me why the 120 word method that I wrote took me 2 hours and not 2 minutes ?

I read it as baby sitter lol

We once had a wierd race condition in our code that we couldn't figure out after hours of debugging .. we were on call for almost 3 hours and it was nearing midnight , the senior dev was like let's sleep it off guys ... The next day when I login , I saw him push a commit at 3 am which fixed the underlying issue , I asked him how he figured it out , he said .. it came to him in his dream

Unrealistic expectations while recruiting and unrealistic deadlines when you get the job 😏

Probably log that payment system is not QA verified in your jira comments and attach the mail to the same wherein mgmt shot down your QA request ... Might help you save face

P.S : your situation screams red flags , maybe look for another opportunity or escalate

I've encountered a similar situation , honestly it's frustrating to see how narrow minded people are

These days only people who glorify their accomplishments and use that to get a better offer are praised and admired

I guess you could use a code smell metric like sonar and show the improvement before and after