How it should be:
- First: solve the problem
- Second: Write your code.

How many people do:
- First: Write code
- Second: solve code problems
- Third: Adapt code with requirements
- Forth: get lost on your spaghetti code
- Sixth: make a suicide

- Seventh: come back as a zombie & bother everyone.

What happened at fifth that made him decide this?

- Fifth: Travel back in time and do 6th before this

Employ TDD or BDD and see your issues die :>

I'm trying to covert from the latter to the former. It really makes more sense once you experience the process, it's just hard to change your mindset to not try to write the code first.

Is Forth a pun?

Actually I just did this for Code Sprint:

1. Read the problem
2. Go WTF
3. Try to decipher the problem
4. Think about a solution
5. Give Up

In the real world, I actually do a mix but make sure my own code is clean enough so I avoid killing myself.

However, whenever I read and have to fix other people's code, I feel like turning into a murderous maniac.

yes, forth. (from a fellow catlang enthusiast :p)