[JaTochNietDan]

Quote:

Originally Posted by spookie I generally write hacky code to get something working, then optimise the hell out of it. If I try to do something nice and maintainable the first time, I find myself taking much longer to get a result (no fun there), and skipping the optimisation step, which is probably still necessary once the code is actually functional. IMO: 1. Get it working. 2. Optimise. 3. Prettify.

That doesn't work too well in my experience most of the time. The issue with that is in the past I would've tended to just say ah well, I'll move on and optimize it later. Then that stuff builds up swiftly.

I tend to plan ahead myself these days though and optimize as I'm going along rather than get it working first, I personally find it easier and more efficient instead of going back. I like to spend a lot of time thinking before actually doing it, making a plan in my head of how I'm going to do it.