Ranter
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
Comments
-
Create a "side" project and call it the "SixMillionDollarMan". Slowly rebuild the whole thing there.
-
OP if you're serious about this and want your situation to get better: read "Working Effectively with Legacy Code"
-
tedge3071yThe people that made it usually won’t like you calling their work shit, even if it is. Sometimes even suggesting rewrites can be a touchy subject.
I wouldn’t be too hopeful about rewriting it, but I’m also a fan of the side project. Even if no one ever sees it, it’s still cathartic. -
I think I made a ton of enemies refactoring sloppy legacy code while having it work perfectly and not stretching the time lol
-
We3D26711ycope and struggle? just kidding. will refactor it bit by bit in any free minute I have. for a few years ( if not a big project ) you'll be done and nobody will even notice ;}
@tedge I don't care if they got mad at me or not. If it's a shitty code they have to learn their mistake and not continue spreading the diarrhea onto other projects too -
@We3D but we MUST write shitty code because this is a business and we need to produce! If we spend an extra half hour thinking of better architecture WE LOSE MONEY! Because MONEY important! I say this as a PRODUCT PROJECT ANALYST ENGINEER
-
We3D26711y@TeachMeCode I'm really thankful my cur boss values quality over speed... still though prioritizes new features/projects rather than refactoring. I started a huge refactoring in the 1st project they put me to help and the lead is assuring me I won't be left soon finishing it b/c of new assignments unless I do it in my free time ( which won't happen ofc... got so many personal ones I don't have time 4 )
I could use some advice. Immagine this: you recently started a new job where the people are great, the product is pretty cool and pay is good. But the code you have to work with is the biggest pile of shite you've ever seen and your manager does not want to change any of this, even after you suggest you would build something that would be a thousand times better, not only "code wise" but for the users too. What would you do?
question