Probably one of the best exercises in restraint, is leaving behind a partially inconsistent solution and knowing it's OK for today.

I've been writing this application now for about 3 weeks. Its so far come together but as it gets more advanced, it requires more complex manipulation(But it is warranted - it's not complex for the sake of it) and the solutions needed, need to be quite elegant ones - to fit in and facilitate the overall design and implementation.

I'm getting there, but the more complex things get the less I remember ALL of the parts - as you do with a more simple construction.
So as you get more complex, your milestones become simpler and simpler while the issues become more difficult to "just fix" so it takes longer to fix/overcome them. I guess this is where constant design and documentation pays off and if you're stuck smack bang in the middle of a fix, and you need to leave(it's the end if the day eg.) - that's difficult.

Now I could stick around until it works but then I loose valuable "me" time plus I don't get to work with something tomorrow - so it's not that I'm a clock-hugger, just happens that when it's time to leave, and you're in the middle - it's temping to loose your time and be there until a ridiculous hour.

Essentially restraint - the balance of resisting a need, especially when you want that need - this is difficult, and essentially it comes down to willpower vs need to fulfil in the short-term goal, coupled with foresight to rationalise priorities - I don't *have* to fix it *today* - today's effort is sufficient, tomorrow to fix it is suitable.

I'm consistently fighting with myself