I was joking to my wife tonight that a good reboot would be nice on one of them.
Somehow in the great development project called Parenting, some rogue error causes certain attitudes and personality issues which conflict with the primary program.
Naturally it is the mistake of the developer which has been shaping and adjusting the daily builds, forever, with no end in sight. An expensive and long drown out program indeed that at times may lie dormant while other sub routines are running.
Don't think the administrator is not to blame either! After all, some guidelines and policies must be in place to provide a framework for the developer to do their jobs and provide the program boundaries to work. And these policies are always evolving as future capabilities become accessible.
But sometimes it would be nice to have the ability to step through your code, find your errors and fix them and then restart it all. But this process doesn't run very well on human life forms. No, it's easy to reboot a server or change some code on it.
The real effort is from those of us that just look at what we have and just make it work or fix what is broken within reason and sometimes upgrade the software when all else fails. You can upgrade your kids software also but you have to work much harder to do it because you are the developer creating the fix pack. Start with the end in mind helps and if you haven't yet, now is a good time to do so.