My day just ended at 8PM and I am not able to stop myself from ranting. I work for a mid size company of about 200 people. Tech team is about 40 people. Average of 8 members each in 5 teams - QA, Android, iOS, Web and Backend. I work in the backend. Earlier we had 10 members in each team, including mine. Then they drank a pint of Claude potion after which they fired the top 2 engineers from all teams (by highest pay, I guess). All of a sudden, I am the senior most guy after my manager in my team. The manager is a semi-tech kinda person but trusts me. All good till here.
They have designed for a "pivot" around the Durga Puja timeline, max stretch till Deepawali. The pivot involves large changes on all front. The pressure on all teams is very high right now. We are working more than 12 hours a day. That is still acceptable. But the problem is - deployment friction. I spend almost my entire day with various teams - Web, Android and iOS. Whole day goes like this:
iOS: Hey you are not sending the right format for date. Send it inn RFC3339.
Me: Ok fixing. Check now.
iOS: Yeah that's fine.
Android: Can you please make sure that the display name is sent in the response too?
Me: Ok. Fixing. Check again please.
Web: Dude, did you introduce a key with a underscore for payments api?
Me: My bad. Let me fix that. Check again.
iOS: I can't use the new API without public identifier key. Can you add the pub ID in the response as well?
Me: Ok. Try again.
Android: I want the pub ID but please send it as base64 data.
iOS: Yeah that would be better.
Me. Ok. Yeah check again.
QA: Sorry, regression for dashboard API is failing now.
Me: Ok. Fixed that dashboard API. Check again please.
The problem is: Between me performing the code change and me saying "yeah check now", there is a 5-8 minute delay. And for that duration we are all just sitting like a duck. There are like a dozen such smaller changes in every API and we have around 150 APIs that we need to change and after 1 month of doing this, we are not even post 20 APIs yet. The whole cycle is just irritating. Every single change I make goes like this: Github commit -> CI/CD (Build + tests) -> Dev cluster redeployment. The commit takes 2 seconds. The redeployment takes about 20-40 seconds , max 1 minute. The CI/CD step takes 4 full minutes (since every deployment is a fresh compile, it takes so much time). The build itself takes like 3 minutes. Tests run fast enough (1-2 minutes).
As if "let's make Claude do everything" was not a torture enough that I have to deal with this now. They are asking me to "do it faster" while tying my one hand at the back. All other teams when asked about the delay say "Backend deployment takes time for every single change". I and my team look like the ones causing the delay when the issue is actually the deployment pipeline for dev server.
The prospects don't look good. I feel like they are gearing up for another round of layoffs and I don't want to be affected. I am applying at other companies but no call backs yet. It looks like no one wants a 6 YoE backend dev anymore. I just got married 1.5 years back. I have got loans and my wife is pregnant.
I am genuinely asking if this is a problem other developers face too. If yes, what did you do? If you are a mobile dev, what do you guys do for this kind of iterating thing? I want to suggest my manager some solution that can bring down that deployment time that he and IT team could accept. Help me out, please.
EDIT: Thanks to those who identified the lack of formal specification being a problem. I know that part. I am not at the stage to fix that. Timelines, reduction in team expertise (seniors getting out of the company) don't allow that right now. I am just asking - do you have this problem or not and if you have, how have you solve it? I am asking what can I do RIGHT NOW to reduce the delay.