8

I'm faszinated by some dev's ability to write legacy code.
Not maintaining but plainly creating code so horrible, that it can be considered legacy.

I wrote a new API for a silly Application because the old one had hardly anything to do with rest. At all. And despite the code being only 2 years old, it was still unmaintainable.

Now that I'm finish with this task, i got the next generation of the angular Frontend.
A guy wrote a completely new version of the frontend in angular5.
Only untyped variables, no documentation, no tests at all, no idea whats going on where,....

I thought my job was to adjust a few URL's and change some DTO's, but now i have to refactor everything again...
And the pain continues.....

Comments
  • 1
    Sounds like API Guy (or a clone) to me.

    If he's coding again, please break his keyboard.
  • 1
    Who told you to refactor that code? Seems to me like those changes are simple enough that this task won't benefit from refactoring.

    If you are doing this on your own then better do tell about this to your higher ups and give them a good reason or you might look as inefficient, taking so long to do just a few simple changes.
  • 0
    Frontend guy left for another project.
    I'm now on my own with this.

    And the project lead doesn't really care as long as I say, that I can release some day.

    And the task resulted in being not that simple, since the frontend took profit from the poor API design.
    Now some of the logic needs to be changed
Add Comment