26 Ways To Know Your Software Project Is Doomed
August 4, 2011 1 Comment
- You are friends with the janitor
- Progress is now measured by the number of fixed bugs and not completed features
- The lead web developer thinks the X in XHTML means ‘extreme’
- You start considering a new job so you don’t have to maintain the application you are building
- All of your requirements are written on a used cocktail napkin
- Your source code control system is a series of folders on a shared drive
- Your best developer only has his A+ Certification
- Your manager could be replaced by an email redirection batch file
- Developers use the excuse of ’self documenting code’ for no comments
- Your favorite software pattern is God Object
- You still believe compiling is a form of testing
- Your team believes the transition from VB6 to VB.NET will be ’seamless’
- Your spouse only gets to see you on a webcam
- The phrase ‘It works on my machine’ is heard more than once a day
- The last book you read – Visual InterDev 6 Bible
- Your lead web developer defines AJAX as a cleaning product
- Requirement – Rank #1 on Google
- Everyday you work until Midnight, everyday your boss leaves at 4:30
- The night shift at Starbucks knows you by name
- Management can not understand why anyone needs more than a single monitor
- You secretly outsource pieces of the project so you can blog at work
- Your boss argues “Why buy it when we can built it!”
- You start wondering if working 2 shifts at Pizza Hut is a better career alternative
- All performance issues are resolved by getting larger machines
- You are using MOSS 2007
- You have been 90% complete 90% of the time