65
bunk3rp
7y

First rant here!

So i just inherited this legacy application in my new job.

I started looking at the code and it just doesnt make sense!

What the fucking fuck!!

Comments
  • 6
    And I thought I wrote bad Rails apps
  • 3
    Also, welcome to DevRant!
  • 1
    print logs is your friend
  • 2
    Experience and headache are what you will get from that legacy treasure!

    & Welcome to devrant!
  • 2
    Does that mean I can be a programmer too?
  • 8
    Legacy application maintaining rule #101: (if it is working) please look but don't touch!

    Welcome to devrant !
  • 2
    Hahahaha, oh man... Shocking.

    Good luck, mate!
  • 8
    when working with legacy app keep in mind that each line you read is not only storing info about current function(ality) but also years to decades of history of changes of itself as well as the surrounding context.

    you're an archaeologist now, not an engineer. think about what has most likely happened through the history with the thing, not what function does the thing have now.

    XD
  • 3
    @Midnigh-shcode also assume every bug you find is being exploited as a feature by some user somewhere
  • 3
    Don't touch that. Took over a old program and added error handling. Broke the workflow. He freaking counted on errors happening! -.-
  • 2
    hahahahahahahahah, we all passed into this, it always happens to me, i write a code and after i comeback to it later, i'm like WHO THE STUPID FUCK WHO WROTE THIS, then i remember that it was me :')
  • 2
    Atleast it has a few comments.
  • 1
    I'm quite intrigued by the "##file included no dashes in filename" comment — does that mean that only files with dashes are handled at all? :o
  • 2
    I may see an Sql injection issue BTW..
  • 1
    @Flygger thats exactly what it means haha. The application splits the filename by dashes and then use this values as tags.
  • 1
    Showing to my wife: <sarcastically> Good! At least it's going to be saved 😂
Add Comment