[ENTP]

We share a similar mindset. I actually get a kick working through crappy code as I find reverse-engineering quite exciting, in a kind of "order from chaos" way. Take something crap, make it better, learn something and get paid for it. Ideal!

[ryan-allen]

As someone who usually writes the crap stuff that other people get to live with, now I'm on the other end and having to make this "order from chaos". It's one of the most difficult things I've ever done.

I just hope I can figure out how to enjoy it, eventually.

At this stage the only thing that keeps me going is I'm too proud to feel ineffective and to fail at this, ugh!

[ENTP]

Chin up! Here are some tips:

* Reframe the task as a game. A crime to solve if you like.

* See it as a series of black boxes that you keep subdividing (You are working top-down right?)

* Keep a [cork|black|white]board like they do in the movies with all the suspects and details of the case, with the string linking them (Do this digitally if you like)

* It's more important to know the I/O of the boxes/components than how they work, at least initially

* Be transparent with your employer about the difficulty. They know it's a mess - that's why you're there.

Good luck!

[jrumbut]

Nothing teaches you how your technology of choice really works like taking apart a massive horrendous codebase.

You'll be at the next level of expertise soon!

[collyw]

I often get more satisfaction from removing code (and keeping / improving the functionality) than I do from writing new code.