Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
DubbaThony153142dWell, you can in theory play it out to own advantage, but brace yourself as it dosent sound like its gonna be easy on you.
Good luck, buddy.
And dont believe u fucked or sth, becouse human is weird creature that what he believes, it slowly becomes, so if you believe u fucked, u will get self fucked.
CatFoodParty21142dSurely, they would hire a replacement senior dev, but I think I kinda get what you're saying about the codebase's 'uniqueness'. If the company isn't asking questions or even batting an eyelash at a senior dev leaving with little to no documentation, then that's a red flag.
-- at my last job, I was suddenly stuck managing (and learning how) the servers and cloud services were set up. It was a mess, but we got through it. I learned a lot from that experience. I'm glad I didn't lose hope when it felt like a trainwreck. Don't go into panic mode yet.
junon286442dAgreed with @CatFoodParty, which is rare since green dots tend to be iffy. :D Set an avatar, yo.
They should hire a senior dev to replace them. If they rely on a junior dev without consulting them on whether or not they think they can handle it, that's the company's fault when it inevitably fails.
PepeTheFrog31642dSame thing happened to me in a previous job. I got left alone on the core project of the company after 2-3 months of being hired.
This is what I focused on to be in control and to make it easier on new potential devs (if not already done):
- making doc covering the usage, requirements and design of the project
- defining levels of tests and test plans to cover the features
- implement the tests gradually with the most business value. Focus on high level black box tests if you can.
- organise tasks in order of priority and speak to stakeholders
It takes time but expecting you to do everything without a ramp up would be stupid from a manager's point of view. Don't accept the pressure and just be organised.
Don't be afraid to leave if they are being assholes. They need you more than you need them.
Thanks everyone. i talked some of my troubling thoughts with my tech lead and now am somewhat less worried. he says that i have to work on the left guy's tasks for the current sprint (!!!) but new joinings would be coming from next week (not sure how is that gonna play since i have been working for last 3 months and still 70% clueless about the codebase) . He also said that he and other people will be around if something comes up that is out of my knowledge.
I just wish that i could go through each and every LOC and create a spreadsheet of a million questions mostly in the format : "why is it done like this way ? why can't we do it like that way?" . But i wouldn't be going forward this thought as its an incredibly irritating thing to answer lol