Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I'm​ actually in this same situation except instead of one big comments-less app it's two lol, the only way I could get through it all was using the person code as an example of what not to do. That and I stayed hell away from it, honestly at this point it's have been better to remake the app from scratch using something like xamarin to cut time down
-
@f03n1x I proposed to them to change engine since the once we use is actually quite unreliable and buggy, but they are super eager to get the beta out so I'm stuck with this noodle soup.
Every task takes approximately 15 times longer to complete because of the code base.
Also as a junior developer this is quite the hell hole for me, but I can easily say I've learnt a lot from it and I've only been hired for two months so far. -
@Letmecode the solo-ness in the project is about to be gone. On Monday next week another programmer is going to join the cause, but I'll take your tip and try not having every conversation be about how messy the code is. The application needs to reach beta and it won't do that if no one works on it 🙄
-
Like many before me said, sometimes taking the rewrite route is way more productive than refactoring spaghetti code.
3 months ago, I managed to convince my manager to rewrite our whole system so I can be able to add any given feature in hours, rather than what would take me days with the old codebase.. I also scared him with some security issues.
Next week I'm going to re-build the whole mother fucking database.
These guys were studying for a Java exam...from PRINTED OUT PHONE PICTURES OF CODE ON THEIR SCREENS
I HOPED I WOULDN'T BE BALD AS MY DAD BUT AT THIS RATE I WILL BE HAIRLESS FROM TEARING IT OUT ON MY BLOODY OWN
I got hired for cleaning up a 2 year project of rushed spaghetti code , where they previously only had 1 programmer aND HE WROTE 37 THOUSAND LINES OF CODE!
OH WE NEED A NEW FEATURE?! LEMME JUST RESEARCH THIS COMMENT-LESS CRAP FOR MULTIPLE MILLENIA BEFORE I CAN GRASP WHAT THE FLYING FRICKIN FRIDGE CODE DOES
To top it off, I've about ONE MONTH LEFT BEFORE BETA RELEASE TO FIX THE CODE!
I'm super grateful for this job as it's my first programming job BUT I'M GONNA SET THE REPOSITORY ON FIRE SOON AAAAHHHHHH
HOW CAN YOU, THE PREVIOUS PROGRAMMER, WORK IN THIS ENVIRONMENT WHERE MOSTLY ALL FILES ARE +2000 ROWS OF UNDOCUMENTED CODE
OH AND JUST GOT A MESSAGE FROM THE PREVIOUS PROGRAMMER:
"You can just remove the unused code and refractor it some, izi"
IZI MY SHITTY POOP CAR
AAAAAAAAAAAAAAAHHHHH!!!
Now with that out of the way, how would you recommend handling a stressful release deadline?
undefined
kill me
junior dev
first job