Learn More
Resend Email
36
TheCodeMonkey
4y

How the fuck am I expected to salvage a fucking project that has been handed down to me with.
- No fucking clear architecture
- No fucking documentation
- Fucking shitty ass code base with no fucking coding standards
- The previous team was fucking learning a whole fucking new technology stack *Not fucking kidding* making fucking mistakes left and right
- No code reviews
- Mixing fucking local and cloud enviroment together
- No fucking testing
- Feature that were supposed to be implemented and are not working
- No configuration all the stuff are hard coded
- Full responsiblity for the whole stack
- Only one other guy with me
- And this fucking project has been delayed for a year
- MUCH FUCKING MORE WHERE THAT CAME FROM

Like what the fuck am I expected to do? I took the job thinking that people knew what the fuck they were doing and surprise surprise that was a fucking bust.

the problem is also I am the junior and these fucking people have more experience than me, what the fuck happened to over seeing people's work, PM doesnt give a shit, developers dont give a shit nobody gives a shit.

But when I got this surprise surprise now everyone is interested in finishing the project

BULLSHIT

rant
Favorite
Ranter
Comments
  • 2
    4y
    Think this is often the case in software. Been thinking about this a lot recently; is most software just flung together and the role of the software dev. is to do incredibly manual tasks updating it etc.

    Idk might just be rambling.
  • 2
    4y
    @BooFar I get where your coming from, but there is an extent. I would not have complained if the technical handover was a few months after the start. But that fucking team had a whole year. If they were to come back to the project again they would not understand jack shit
  • 2
    4y
    Sounds like the dev that's gonna take my job in the future if I don't correct my mistakes in time...
  • 3
    4y
    Do what I will be doing this year, pull it apart slowly, maintain duplicate code as you rebase everything, and add BDD, Unit and integration tests before you start, if possible to prevent any issues with end users.

    Then as you go, enjoy hitting delete on blocks of code.

    And slowly but surely and you haven't gone insane by the end of it... you'll have a clean project to start burning holes into again.
  • 1
    4y
    @c3r38r170 😂 At least you're gonna do it
  • 0
    4y
    @C0D4 It would have been plausible to do that if I had the time. Between this project and another it is a nightmare. It hard when you're working with only one other guy, it's not impossible but much harder
  • 1
    4y
    Curse Word Count: 21 / 50+

    Rant Rank: Cantankerous Vietnam Vet
  • 1
    4y
    Learning how to read shitty code. That's one of the things every good developer eventually does. Good luck 👍
  • 1
    4y
    You'll get by, be thankful it was not in React/Angular/VUE. The gods are with you
  • 2
    4y
    Same happened to me when I was a jr. Old team basically reverse engineered all the code I was handed over by a team that basically left.

    In a different team now but I'm the only one that writes docs.... And everyone wonders why I seem to know how everything works and can fix any problem....
  • 1
    4y
    I see it as a challenge to lead by example, bring the project, your team and yourself to the next level, bit by bit, therefore putting yourself in a position to give direction and thus givng you more control.
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment