Some of you veteran guys who are here since the early days know that each and every release consisted of doing all-nighters and 18 hour workdays before, and ended up with some silly bugs that could have been prevented easily with a bit more time. These happened because of the things unaccounted for during planning. Then after I was done and released, I wouldn't do anything for the next couple of days because I was trying to put as much distance between me and my computer as I could of course, after spending a 100 hours working in front of it that week.
Shit, man, that's just development! I don't know how many times I've seen that, and shaken my head at professional developers who keep falling into the same trap over and over again. By professional, I mean software engineers.
So this time I have decided I'll instead I'll take those extra couple of days and not work to exhaustion. You've been waiting for quite a while and I hope this few extra days won't matter as much to you as it does to me and the development process.
Good. Don't burn yourself out. As I said, I've seen this over and over, but I can tell you that doing that will just lead to more issues you need to fix later. And the later you find something, the more expensive it is to fix.
I say both of these from personal experience (as a very experienced software engineer) and from info from studies on the subjects.
There's an adage I really like about software development. It applies to many other things.
"The first 80% takes 80% of the time. The last 20% takes 80% of the time."
"very experienced" means old.
"software engineer" as opposed to "computer programmer" - software engineering is a discipline. Computer programming is just coding.
10/10 game 
