5

I'm officially at a point of writing software that I know this snippet of code will be absolute hell for the next developer to maintain.

Doesn't matter how well I document it, doesn't matter how well I break down the problem.

The `why` of the problem is gonna drive the maintainer crazy later. The most dangerous part, it might as well be me in the coming months.

RIP the next developer, who will have to maintain my spaghetti (includes me).

Comments
  • 1
    but why
  • 0
    You finish projects and are not doing applications that are under fulltime development more than a year or so. So maybe, it's even efficient someway. Would your customers even pay for source quality?
Add Comment