my gut reaction here is to cringe and generally be revolted. with some thought it seems like an okay idea... it gives you a place to start in the morning that

my gut reaction here is to cringe and generally be revolted. with some thought it seems like an okay idea... it gives you a place to start in the morning that is easy and helps you overcome the 'start working' hurdle at the beginning of the day. with more thought it reveals bigger problems in methodology which enable this to be practical imo. ranging from not having a plan through to not having discipline. imo you should be able to leave things in 'a convenient state' which may be broken or not, and then pick it back up... as long as you are working to a plan, and the code is sufficiently clean and friendly then you should be able to approach /someone elses unfinished work regardless as to what state it is in and start working immediately/. On the other hand I know that most people struggle with reading code... maybe this is part of the problem more than anything else? The context switch involves some dallying around reading code and making sense of it in the morning - I don't see how leaving things broken removes this. Rather this seems like a prescribed way to force yourself to leave at least the bare minimum documentation you should to do your job as a programmer with a little more efficiency. Write things down, don't trust your memory, its easy to think when you are in your late teens or twenties that its an immutable record and highly reliable - especially if you have been inflicted with an especially good memory - the truth is that its a bug riddled system where data constantly degrades. Work around it like you would any other faulty system and keep backups too...