What is even worse than getting stuck?

    Every programmer knows how it feels to get stuck. There are various means of getting stuck, sure. You might deal with something trivial that you don't have experience with for an hour instead of ten minutes. You could get annoyed by a task that you don't like or have a little motivation to finish, voila, you find yourself procrastinating a few hours because you don't want to get certain things done.
    But the most dangerous thing you can do is setting a big project aside for a year or more and giving it just a fraction of time while it is sleeping on background. Many factors change in the meantime. Libraries, frameworks but mainly your skills, experience and actual interests and what used to be fancy last year is just good this year. What you found good is crappy now... All this makes you want to rm -rf  the project. You don't have passion for it and you would rather be doing something else or do it from scratch again.

    In the most extreme cases it may happen that a part of your application is an administration, auction system or some Rich UI and you had decided not to use HTML 5 and websockets because of low browser support back then, except that after a year and a half it would be acceptable. Moreover you might learn Google Web Toolkit in the meantime and you can't even smell JSPs and Ajax now. rm -rf ? :-)

    Ever been there ? I truly believe that this is one of the mistakes that one learns a lesson from and pay a very good attention, so that it won't happen again.