Sign in
|
Join
|
Help
Search
Hamza Khalid
Stay Agile, Expect Change
Home
Contact
About
RSS
Atom
Comments RSS
Recent Posts
Need For Speed Pro Street
101 Ways To Know Your Software Project Is Doomed
The Geek Code
SINGLE LINE OF HTML CRASHES IE:
Microsoft Astoria:
Tags
Asp.net
Enterprise Development
General
News
Contact me
Navigation
Home
Blogs
BlogCasts
Level 5
Forums
Photos
Downloads
External News
Technology News
Digg
Slashdot
The Server Side
Dotnet Journal
Asp.net
Java.net
InfoQ
Blogging websites
Geekswithblogs
Asp.net Weblogs
Coding Horor
Asp.net Resources
Favourite Blogs
Technet Bytes
Mohtashim (IT News)
ISerializable
Chris's weblog
Nikhill Koharti
Scott Guthrie
Scott Hanselman
David Hayden
ayende rahien
Bee Log
Wilco Bauwer
Open Source
C# Open Source projects
Hibernate
GotDotNet
CodePlex
Sourceforge
Archives
August 2007 (4)
May 2007 (1)
April 2007 (1)
February 2007 (3)
January 2007 (1)
November 2006 (3)
September 2006 (1)
101 Ways To Know Your Software Project Is Doomed
This is a hilarious post "
101 ways to know your software project is doomed
". If your have been involved in software development at an IT firm then there are good chances that you might have experienced some of these items. I specially liked the following ones.
All performance issues are resolved by getting larger machines.
The phrase ‘It works on my machine’ is heard more than once a day.
Every bug is prioritized as ‘
Critical’.
Your team believes ORM is a ‘fad’.
Your favorite software pattern is
God Object
.
Your white boards are mostly white (
VersionOne
).
Share this post:
Posted:
Aug 09 2007, 12:18 PM
by
hamza khalid
| with
no comments
Filed under:
General
Comments
No Comments