Feb 07

CodeSqueeze has collected 101 ways to know when your software project is doomed.  Here are my 10 favorites:

  • You start hiring consultants so they can take the blame
  • All of your requirements are written on a used cocktail napkin
  • The lead web developer thinks the X in XHTML means ‘extreme’
  • Progress is now measured by the number of fixed bugs and not completed features
  • Every bug is prioritized as Critical
  • Project estimates magically match the budget
  • Developers use the excuse of ’self documenting code’ for no comments
  • Your spouse only gets to see you on a webcam
  • Your boss expects you to spend the next 2 days creating a purchase request for a $50 component
  • “Oh, oh, and I almost forgot. Ahh, I’m also gonna need you to go ahead and come in on Sunday, too… thanks”

101 Ways to Know Your Software Project is Doomed

Check out more funny stuff at Web-Funny!

Share and Enjoy:
  • Twitter
  • Facebook
  • Reddit
  • LinkedIn
  • Digg
  • DotNetKicks
  • StumbleUpon
  • Slashdot
  • Technorati
  • Google Bookmarks
  • Print
  • email

Article published on February 7, 2009

3 Responses to “101 Ways to Know Your Software Project is Doomed”

  1. bobfox Says:

    Are you talking about http://www.mini-tools.com ? 😉

    Seriously: are the Mini-Tools dead?

  2. timm Says:

    Actually, no, far from it. We are hard at work on a new suite of web/desktop productivity tools… mini-tools! I will be talking more about it in this space as we approach release. Thanks for the setup! 😉

  3. bobfox Says:

    Hey, the website http://www.mini-tools.com changed and components are on sale.
    Does that mean that the release of new components is imminent?

Leave a Reply