• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

When to call it quits?

 
Jeroen T Wenting
Ranch Hand
Posts: 1847
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The more I stare at my code (which is all working fine) the more things I find that could be done "nicer" (mind, not necessarilly better, but nicer).

Things like adding an action so the Enter and Escape keys are forwarded to the OK and Cancel buttons on dialogs, tweaking parameter passing, decoupling yet another set of classes by adding an abstract base and a factory in the middle.

When to say enough's enough, now it's code complete unless release critical bugs are found during testing?

This is getting frustrated, I've been (in my mind) "just a few days" from that point for almost a month now...
 
Barry Gaunt
Ranch Hand
Posts: 7729
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Leave it aside a couple of weeks, go ride a bike, and come back and achieve the "why the hell I'm doing all that?" Nirvana. Then start ripping all the superfluous cr*p out of your code.
 
Sam Codean
Ranch Hand
Posts: 194
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey Jeroen,
Something similr happening to me too. So do not worry. You are not alone
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic