Subscribe via RSS

101 Ways To Know Your Software Project Is Doomed

Filed Under Software Process
  1. Management has renamed its Waterfall process to Agile Waterfall
  2. You start hiring consultants so they can take the blame
  3. The Continuous Integration server has returned the error message “Screw it, I give up”
  4. You have implemented your own Ruby framework that uses XML configuration files
  5. Your eldest team member references Martin Fowler as a ‘snot-nosed punk’
  6. Your source code control system is a series of folders on a shared drive
  7. Allocated QA time is for Q and A why your crap is broken
  8. All of your requirements are written on a used cocktail napkin
  9. You start considering a new job so you don’t have to maintain the application you are building
  10. The lead web developer thinks the X in XHTML means ‘extreme’
  11. Ever iteration meeting starts with “Do you want the good news or the bad news…”
  12. Your team still gives a crap about its CMM Level
  13. Progress is now measured by the number of fixed bugs and not completed features
  14. Continuous Integration is getting new employees to read the employee handbook
  15. You are friends with the janitor
  16. The SCRUM master doesn’t really care what you did yesterday or what you will do today
  17. Every milestone ends in a dead sprint
  18. Your best developer only has his A+ Certification
  19. You do not understand the acronyms DRY, YAGNI, or KISS; but you do understand WTF, PHB, and FUBAR
  20. Your manager could be replaced by an email redirection batch file
  21. The only certification your software process has is ISO 9001/2000
  22. Your manager thinks ‘Metrics’ is a type of protein drink
  23. Every bug is prioritized as Critical
  24. Every feature is prioritized as Trivial
  25. Project estimates magically match the budget
  26. Developers use the excuse of ‘self documenting code’ for no comments
  27. Your favorite software pattern is God Object
  28. You still believe compiling is a form of testing
  29. Developers still use Notepad as an IDE
  30. Your manager wastes 7 hours a week asking for progress reports (true story)
  31. You do not have your own machine and you are not doing pair programming
  32. Team Rule – No meetings until 10 AM since we were all here until 2 AM
  33. Your team believes ORM is a ‘fad’
  34. Your team believes the transition from VB6 to VB.NET will be ‘seamless’
  35. Your manager thinks MS Project is the best management tool the market offers
  36. Your spouse only gets to see you on a webcam
  37. None of your unit tests have asserts in them
  38. FrontPage is your web page editor of choice
  39. You get into flame wars if { should be on new line, but you are impartial to patterns such as MVC
  40. The company motto is ‘Do more with less’
  41. The phrase ‘It works on my machine’ is heard more than once a day
  42. The last conference your .NET team attended was Apple WWDC 2000
  43. Your manager insists that you track all activity but never uses the information to make decisions
  44. All debugging occurs on the live server
  45. Your manager does not know how to check email
  46. Your manager thinks being SOX compliant means not working on baseball nights
  47. The company hires Senetor Ted Stevens to give your project kick-off inspiration speech
  48. The last book you read – Visual InterDev 6 Bible
  49. The overall budget is mistaken for your weekly Mountain Dew bill
  50. Your manager spends his lunch hour crying in his car (another true story)
  51. Your lead web developer defines AJAX as a cleaning product
  52. Your boss expects you to spend the next 2 days creating a purchase request for a $50 component
  53. The sales team decreased your estimates because they believe you can work faster
  54. Requirement – Rank #1 on Google
  55. Everyday you work until Midnight, everyday your boss leaves at 4:30
  56. Your manager loves to say “Why do the developers care? They get paid by the hour.”
  57. The night shift at Starbucks knows you by name
  58. Management can not understand why anyone needs more than a single monitor
  59. Your development team only uses source control as a power failure backup system
  60. Developers are not responsible for any testing
  61. The team does not use SVN because they believe the merge algorithms are black voodoo magic
  62. Your white boards are mostly white (VersionOne)
  63. The client continually mistakes your burn-down chart for a burn-up chart
  64. The project code name is renamed to ‘The Death March’
  65. Now it physically pains you to say the word – Yes
  66. Your teammates don’t refactor, they refuctor
  67. To reward you for all of your overtime your boss purchases a new coffee maker
  68. Your project budget is entered in the company ledger as ‘Corporate Overhead’
  69. You secretly outsource pieces of the project so you can blog at work
  70. A Change Control Board is created and your product isn’t even its first alpha version
  71. Daily you consider breaking your fingers for the short term disability check
  72. The deadline has been renamed a ‘milestone’…just like the last ‘milestone’
  73. Your project managers ‘open door’ policy only applies between 5:01 PM – 7:59 AM
  74. Your boss argues “Why buy it when we can built it!”
  75. You bring beer to the office during your 2nd shift
  76. The project manager is spotted consulting a Ouija board
  77. You give misinformation to your teammates so you look better on your personal review
  78. All code reviews are scheduled a week before product launch
  79. Budget for testing exists as “if we have time”
  80. The client will only talk about the requirements after they receive a fixed estimation
  81. The boss does not find the humor in Dilbert
  82. You start noticing your boss’s poker tells during planning poker
  83. You start wondering if working 2 shifts at Pizza Hut is a better career alternative
  84. All performance issues are resolved by getting larger machines
  85. The project has been demoted to being released as a permanent ‘Beta’ version
  86. Your car is towed from the office parking lot as it was thought to be abandoned
  87. The project manager likes to doodle during requirements gathering meetings
  88. You are using MOSS 2007
  89. Your SCRUM team consists of 1
  90. Your timesheet looks like a Powerball ticket
  91. The web developer thinks being 508 means looking good in her Levi Red Tabs
  92. You think you need Multiple Personality Disorder medication because you are Mort, Elvis, and Einstein
  93. Your manager substitutes professional consultant advice for a Magic 8 Ball
  94. You know exactly how many compile warnings cause an ‘Out of Memory’ exception in your IDE
  95. I have used IDE twice in this list and you still don’t know what it stands for
  96. You have cut and pasted code from The Daily WTF
  97. Broken unit tests are deleted because they are obviously out of date
  98. You are sent to a conference to learn, but you skip sessions to go hunting for swag
  99. QA has nicknamed you Chief Off-By-One
  100. You have been 90% complete 90% of the time
  101. “Oh, oh, and I almost forgot. Ahh, I’m also gonna need you to go ahead and come in on Sunday, too… thanks”
RSS Icon

  Don't miss a drop! Subscribe now via RSS or email.

Comments

147 Responses to “101 Ways To Know Your Software Project Is Doomed”

  1. VeronicasLore.com » 101 Ways To Know Your Software Project Is Doomed on July 16th, 2007 6:08 pm

    […] Get the whole scoop here… […]

  2. cenourinha on July 16th, 2007 6:23 pm

    Great list!

  3. Nerdy Inverse Network » 101 ways to know your software project is doomed on July 16th, 2007 6:34 pm

    […] you read that, Duke Nukem Forever’s team ? […]

  4. Karl on July 16th, 2007 6:42 pm

    Ummm yeah and about those TPS reports…We’re gonna need you to use those new cover sheets

    I really thought #100 was going to be a goto statement 🙂

    Thanks from your friends @ http://www.askTheAdmin.com

  5. FeeBee on July 16th, 2007 6:44 pm

    102. The full time staff has been cut from 50 to 25, the $15 million VC investment is gone, and the developers spend 6 of the 8 hours in the office per day playing World of Warcraft. (Also true story).

  6. Brian on July 16th, 2007 6:54 pm

    If being friends with a janitor is sign of doom for a software project … then it sounds like the problem isn’t with the project, but rather, the people running it.

  7. Joe on July 16th, 2007 8:40 pm

    Great! thanks a lot!

  8. Sundry Best » Blog Archive » 101 Ways You Know Your Software Project is in Trouble on July 16th, 2007 9:00 pm

    […] Pretty funny! I like “You start wondering if working 2 shifts at Pizza Hut is a better career alternative” the best, I think. […]

  9. jhummel on July 16th, 2007 9:04 pm

    Congrats on the front page digg placement, due. Great article

  10. retsoced on July 16th, 2007 9:28 pm

    So how many matches does it take to get a free t-shirt? 🙁 Awesome list!

  11. Timothy Haroutunian on July 16th, 2007 9:35 pm

    #46: Go Red Sox, World Series 2007 🙂

    Great list though 🙂

  12. 101 Ways To Know Your Software Project Is Doomed « TheWheat Field on July 16th, 2007 9:48 pm

    […] Ways To Know Your Software Project Is Doomed Source Is it sad that I identify with some of them? … 6. Your source code control system is a […]

  13. The Bleeding Edge on July 16th, 2007 9:54 pm

    How to Tell if your Project is Doomed (funny)

    Hehe: 101 Ways To Know Your Software Project Is Doomed There’s something for everyone in a list like this. 23. Every bug is prioritized as Critical 24. Every feature is prioritized as Trivial Many of us can identify with: 57….

  14. PRO-Grammar on July 16th, 2007 10:09 pm

    Here are few….

    You entire code is an if else block
    You declare all your variables as a class wide variables
    You write system outs for debugging
    You hijack entire directory to check out one file
    and finally
    You develop for 3 days and QA tests for 6 weeks..(true story)

  15. Steve Miller’s Web Sites of Interest » links for 2007-07-17 on July 16th, 2007 10:26 pm

    […] 101 Ways To Know Your Software Project Is Doomed (tags: code developer development fun funny humor humour list programming software projectmanagement tech) […]

  16. ControptoManiak on July 16th, 2007 10:32 pm

    66. Your teammates don’t refactor, they refuctor

    Your teammates don’t know what refactoring is. (true story)

  17. links for 2007-07-17 « Jack The Programmer on July 16th, 2007 11:16 pm

    […] 101 Ways To Know Your Software Project Is Doomed (tags: fun) […]

  18. error is the mother of all inventions on July 16th, 2007 11:43 pm

    […] shelved r restarted.. here is a list of ways whr u cud actually get 2 knw wich way it’s going >> No Comments so far Leave a comment RSS feed for comments on this post. TrackBack URI […]

  19. Confluence: Funny Stuff on July 17th, 2007 12:20 am

    101 Ways To Know Your Software Project Is Doomed

    Might or might not be true. 😉 # Management has renamed its Waterfall process to Agile Waterfall # You start hiring consultants so they can take the blame # The Continuous Integration server has returned the error message “Fuck it,…

  20. shayne on July 17th, 2007 12:29 am

    Oh god. what a depressing list 🙁

    30 is so true……..

  21. Brajeshwar on July 17th, 2007 1:28 am

    Good list of reference.

  22. Timothy on July 17th, 2007 2:15 am

    They are so funny,
    but the sad fact is that we all know at least half of them to be true and we’ve all been through at least a few of them.

  23. La Lista de Listas que estabas buscando - Carrero Bitácora de los Hermanos Carrero, David Carrero Fernández-Baillo y Jaime Carrero Fernández-Baillo. on July 17th, 2007 2:18 am

    […] 101 Ways To Know Your Software Project Is Doomed. vía: digg (Actualización 17-07-2007) […]

  24. admin on July 17th, 2007 2:49 am

    Truth hurts,

    most of what is said above is true.

  25. 101 Ways To Know Your Software Project Is Doomed | Ronan's Blog on July 17th, 2007 2:55 am

    […] 101 Ways To Know Your Software Project Is Doomed […]

  26. Andreas on July 17th, 2007 3:45 am

    Nice list..it’s realistic..some of it anyway..good job…

  27. Quickduck » Blog Archive » 101 ways you know your software project is doomed… on July 17th, 2007 4:34 am

    […] Doomed I tells ya… Filed under Uncategorized having Leave a Comment […]

  28. LankaLife.com on July 17th, 2007 5:35 am

    101 Ways To Know Your Software Project Is Doomed

    # Management has renamed its Waterfall process to Agile Waterfall
    # You start hiring consultants so they can take the blame
    # You have implemented your own Ruby framework that uses XML configuration files
    ………………………………

  29. Interview Question And Answer on July 17th, 2007 6:17 am

    More than 50% projects get scraped. 90% of the work in successful projects are maintenance.

  30. TV Online on July 17th, 2007 6:37 am

    I think by the #60 you’re just about screwed.

  31. herval on July 17th, 2007 8:36 am

    OMG, that feels like it was written by someone on my current project! 😡

  32. marka buku 2007-07-17 « nan tak (kalah) penting on July 17th, 2007 10:27 am

    […] 101 Ways To Know Your Software Project Is DoomedDaftar hal yang lucu tapi kadang benar, mengenai karakteristik suatu proyek pengembangan perangkat lunak yang gagal (tags: manajemen-proyek lucu) […]

  33. fxp on July 17th, 2007 10:51 am

    The PM tells upper management, “It gets done when it’s done — we don’t know what we’re doing.” (Another true one at an update meeting}

  34. Matt on July 17th, 2007 12:16 pm

    Stop watching over my shoulder…

  35. 101 Ways To Know Your Software Project Is Doomed « theHub on July 17th, 2007 12:21 pm

    […] Click here to read the whole list… […]

  36. Musings from the Peanut Gallery on July 17th, 2007 12:40 pm

    Is your Software Project Doomed?

    Someone in our organization passed around a link to this site. I find it entertaining. One person in our organization took exception to #12. Your team still gives a crap about its CMM Level. Actually the issue here is not…

  37. Refuctoring at Shaun MacRae’s Homepage on July 17th, 2007 2:02 pm

    […] that in codesqueeze’s ‘101 Ways to Know Your Software Project Is Doomed’. Very funny! Thanks Jason! Filed under Uncategorized.  | var blogTool = […]

  38. Sucky Fish on July 17th, 2007 3:30 pm

    # Every bug is prioritized as Critical

    I’ve come across the opposite doom-sayer — in a mature but grossly buggy product — every bug is prioritized as trivial (no matter how horrendous the bug).

  39. Tucows Services » Tucows Developer Blog > Blog Archive » 101 Ways To Know Your Software Project Is Doomed on July 17th, 2007 3:33 pm

    […] at codesqueeze, they’ve got a list of 101 signs that your project is destined for failure. While a good number of the items in the list are jokes made up for the sake of being funny (such […]

  40. esm on July 17th, 2007 3:36 pm

    [Brian] If being friends with a janitor is sign of doom for a software project … then it sounds like the problem isn’t with the project, but rather, the people running it.

    The implication is that if you’re constantly staying late enough to see the janitor regularly, you have problems. It’s not a statement on the janitor’s position or worth; knee hit the underside of the table much?

  41. links for 2007-07-18 « Simply… A User on July 17th, 2007 6:41 pm

    […] 101 Ways To Know Your Software Project Is Doomed (tags: humor programming development funny software projectmanagement fun **) […]

  42. links for 2007-07-18 « My Weblog on July 17th, 2007 10:17 pm

    […] 101 Ways To Know Your Software Project Is Doomed (tags: humor management) […]

  43. links for 2007-07-18 « Richard@Home on July 17th, 2007 11:22 pm

    […] 101 Ways To Know Your Software Project Is Doomed funny but true (tags: toread humor programming development) […]

  44. SeoGenetic Blogs » 101 Ways To Know Your Software Project Is Doomed on July 17th, 2007 11:39 pm

    […] read more | digg story […]

  45. 101 Ways To Know Your Software Project Is Doomed « Live2Study on July 18th, 2007 12:27 pm

    […] Read more […]

  46. mnemetica » Blog Archive » links for 2007-07-18 on July 18th, 2007 1:18 pm

    […] 101 Ways To Know Your Software Project Is Doomed 101 Ways To Know Your Software Project Is Doomed (tags: article code fun development programming software project management) Bookmark to: […]

  47. Karen Anderson on July 18th, 2007 4:03 pm

    I loved:

    “20. The phrase ‘It works on my machine’ is heard more than once a day.”

    Yeah! And from the same *&%$ software engineer.

    I sent your list to him. Anonymously.

  48. Subject Code » del.icio.us bookmarks for July 17th, 2007 through July 18th, 2007 on July 18th, 2007 6:37 pm

    […] 101 Ways To Know Your Software Project Is Doomed – 61. The team does not use SVN because they believe the merge algorithms are black voodoo magic […]

  49. Geeqs.Net // Keith's Blog on July 19th, 2007 1:27 am

    101 Ways To Know Your Software Project Is Doomed

    Link to 101 Ways To Know Your Software Project Is Doomed … #102 – More than 50% of this list seems

  50. stefan on July 19th, 2007 4:24 am

    102. you emailed this post to your personal account and went back to coding.

  51. Tim on July 19th, 2007 7:30 am

    Unfortunately, this is SOP for almost all ERP installations, especially:
    *You start hiring consultants so they can take the blame
    *Ever iteration meeting starts with “Do you want the good news or the bad news…”
    *Every milestone ends in a dead sprint
    *Your manager insists that you track all activity but never uses the information to make decisions

  52. Bart on July 19th, 2007 10:10 pm

    101 Ways To Know Your Software Project Is Doomed

    Interesting article. http://www.codesqueeze.com/101-ways-to-know-your-software-project-is-doomed/

  53. Tony on July 19th, 2007 11:47 pm

    101 Ways To Know Your Software Project Is Doomed

    Interesting article. http://www.codesqueeze.com/101-ways-to-know-your-software-project-is-doomed/

  54. Favorite Recent Links 07/20/2007 « Joey JavaScript on July 20th, 2007 1:04 am

    […] 101 Ways to Know Your Software Project is Doomed […]

  55. SquirmMaster on July 20th, 2007 4:24 am

    The team thinks that SCRUM Master is a meaningful credential.

  56. Links from the Trenches #1 | Web Development from the Front Lines at DEVTRENCH dot com on July 20th, 2007 10:53 pm

    […] wrote a post about 101 Ways To Know Your Software Project Is Doomed and its great. In fact these are the kind of development scenarios that got me thinking that we […]

  57. Blah on July 23rd, 2007 4:40 pm

    Murphy’s #1 law of Doom…

    Regardless of shape, form or function, Doom is Universal

    ~~~~~~~~~

    What that means is, I’m a DBA, and I found most of these relevant to that work, too.

    “You think about getting a new job so you don’t have to support the POS you’re building…” priceless…

  58. Blah on July 23rd, 2007 4:55 pm

    #105: when the project schedule is finally set (without any input from you), you find out you’re already behind schedule on half the milestones before even one line of code has been written (you know, because Sales thought you’d work better under pressure).

  59. TechMount » Archive » Daily Friction #254 on July 24th, 2007 1:49 am

    […] 101 ways to know your software project is doomed – To some it may not seem funny. But it is. […]

  60. Rich Ruh on July 25th, 2007 7:16 am

    101 Ways to Know Your Software Project is Doomed

    Humorous post , with a couple of warnings…

  61. Ned Wolpert on July 26th, 2007 1:50 pm

    Doomed…

    Here is an article that can help you decide if your project is doomed.

    Number 95? You have cut and pasted code from The Daily WTF.

    Its a must read…

  62. GenPink » Blog Archive » 101 one hundred and ones on July 26th, 2007 3:05 pm

    […] 101 Ways To Know Your Software Project Is Doomed […]

  63. Ollis Notizblog on July 30th, 2007 1:36 am

    DRAM-Overkill

    Man kann es auch uebertreiben

    nicht exakt das gleiche Thema wie Ramdisks, aber doch ein wenig… es geht um das Erschlagen von Problemen durch massiven Einsatz von DRAM.SUNs X4950 wird als Streaming-Switch verkauft und ist nichts anderes als ein Swit

  64. Aurea Mediocritas » Din categoria “cum iti dai seama ca proiectul tau e dus pe copca” on July 30th, 2007 1:41 am

    […] comment: http://www.codesqueeze.com/101-ways-to-know-your-software-project-is-doomed/ […]

  65. 101 one hundred and ones on July 30th, 2007 11:35 am

    […] 101 Ways To Know Your Software Project Is Doomed […]

  66. Darin on July 31st, 2007 9:02 am

    re: 64. I’ve also heard the project code name “The sinking ship”. true story.

  67. Jerome on August 1st, 2007 3:42 am

    Also a true one :

    Your bug tracking system for a 40 people/ one million dollar project is one Excel spreadsheet

  68. Max Pool on August 1st, 2007 4:11 am

    Jerome – That is a really good one as I have seen that too. As I laugh, I die a little inside…

  69. 101 способ понять, что ваш проект обречен…=) « Блог Серёжи Борзова on August 1st, 2007 6:48 am

    […] стало не интересно писать и я решил, что кому надо – сам прочтет =). Реально, прикольно […]

  70. Intel® Software Network Blogs » Blog Archive » How to identify if your software project is doomed? on August 1st, 2007 10:44 am

    […] happen to across this awesome list “101 ways to know your software project is doomed”. I initially read this post as daily humor, but unfortunately I have personally experienced at […]

  71. Loosely Coupled Human Code Factory on August 1st, 2007 11:06 am

    Software Fuctoring

    Project Manager Definitions from Sedition.com
    The important ones:
    scope creep    hostile…

  72. suelz0mat.de » 101 Weisheit aus der Welt der Softwareentwicklung on August 2nd, 2007 9:50 am

    […] man, man, was habe ich mich eben schlapp gelacht, als ich 101 Way To Know Your Software Project Is Doomed gelesen habe. Die ganze Liste habe ich ausgedruckt, und werde sie morgen früh in der Firma an die […]

  73. Chillisoft Blog » 101 Ways To Know Your Software Project Is Doomed on August 8th, 2007 2:48 am

    […] http://www.codesqueeze.com/101-ways-to-know-your-software-project-is-doomed/ […]

  74. Hamza Khalid on August 8th, 2007 11:44 pm

    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

  75. Siesta… on August 14th, 2007 7:21 am

    […] in cs, software, geek, general at 1:28 pm by alan Found this list(101 ways to know your software project is doomed) while surfing this morning. My favorites: 6. Your […]

  76. Links (8/14/2007) « Steve Pietrek’s SharePoint Stuff on August 14th, 2007 6:51 pm

    […] 101 Ways To Know Your Software Project Is Doomed […]

  77. » Is your software project failing? | IT Project Failures | ZDNet.com on August 16th, 2007 7:00 pm

    […] stuff is so funny, and it’s only partial list. Check out the original post and […]

  78. Michael Krigsman on August 16th, 2007 7:01 pm

    Thanks for such a funny list. I’ve posted some of these over at ZDNet:

    http://blogs.zdnet.com/projectfailures/?p=352

    Michael Krigsman
    http://projectfailures.com

  79. 101 Ways to know your project is doomed at Bernhard Rode on August 17th, 2007 7:52 am

    […] Here I only list the top 10… you may find the rest of the list here. […]

  80. Dashe & Thomson » Blog Archive » Software Project Failure: Early Warning Signs on August 17th, 2007 8:29 am

    […] a great list of 101 ways to know your software project is doomed. From Codesqueeze.com via Michael […]

  81. More on Advertising on StumbleUpon on August 17th, 2007 12:28 pm

    […] in the last two StumbleUpon posts by writing: “On my blog, I wrote a list post titled 101 Ways To Know Your Software Project Is Doomed on the highest traffic day of the week – […]

  82. Oliver Widder on August 18th, 2007 4:40 pm

    Just 3 more suggestions.
    See my small cartoon:
    http://geekandpoke.typepad.com/geekandpoke/2007/08/how-to-know-you.html

    Bye,
    Oliver

  83. 101 Ways To Know Your Software Project Is Doomed « The SOA Guy on August 19th, 2007 8:12 am

    […] Sunday, August 19th, 2007 in Success Ever participated in a doomed project? I did, in 2001. Quite funny the déjà vue while reading this list: 101 Way to know your software project is doomed […]

  84. lee’s garbage collection » Blog Archive » Interesting links… on August 24th, 2007 2:14 pm

    […] but not least… here 101 ways to know your software project is doomed… I did the test today with my colleagues and […]

  85. Top 10 Ways to Know Your Software Project is Doomed « FlashColony Blog on August 27th, 2007 12:55 pm

    […] is the top 10 list Eddie selected from his 101 ways to know your software project is doomed […]

  86. Our project is NOT doomed on August 30th, 2007 2:10 am

    […] project is NOT doomed augustus 30, 2007 10:08 by Rob Especially not because of #99. Be the first to rate this postCurrently 0/5 Stars.12345 Tags: Categories: Software Engineering […]

  87. bugaga on September 7th, 2007 5:44 am

    omg that was very fun 😀

  88. Confluence: 1. Agile Corner on September 7th, 2007 8:27 am

    101 Ways To Know Your Software Project Is Doomed

    Ca peut se rajouter a la liste de JR (11 ways Agile Adoption Fail https://www.pyxistech.ca/confluence/display/AC/2007/08/28/11WaysAgileAdoptionFail)

  89. 101 Ways To Know Your Software Project is Doomed на Артем Большаков on September 8th, 2007 4:57 pm

    […] того, что не Вы трахаете проект, а он Вас». Оригинал по-английски — “101 Ways To Know Your Software Project Is Doomed” […]

  90. IT Юмор on September 10th, 2007 10:33 am

    101 признак того, что ваш проект горит синим огнем!

    101 Signs Your Software Project is Doomed 1. Руководство приняло решение перейти с модели разработки

  91. IT для бизнеса: it4business.ru » 101 признак того, что ваш проект горит синим огнем! on September 14th, 2007 7:29 am

    […] Оригинальный английский текст […]

  92. » 101 moyens de reconnaître que votre projet logiciel est condamné on September 19th, 2007 4:00 pm

    […] gratuitement PowerPoint 101 Ways To Know Your Software Project Is Doomed, une liste assez étrange pour les dévelopeurs de logiciel. Relevé chez […]

  93. » 101 Ways To Know Your Software Project Is Doomed on September 19th, 2007 4:01 pm

    […] free PowerPoint 101 Ways To Know Your Software Project Is Doomed, a strange list for software developers. Thanks to […]

  94. 101 Signs Your Software Project is Doomed » Абдрахманов Руслан on September 24th, 2007 12:48 pm

    […] Оригинальный английский текст Русский перевод, Стибрено здесь […]

  95. 101 Ways To Know Your Software Project Is Doomed « Programming News on October 2nd, 2007 2:14 am

    […] read more | digg story […]

  96. weekly linkdump - max - блог разработчиков on November 2nd, 2007 1:26 am

    […] 101 Ways To Know Your Software Project Is Doomed — штук 30-40 действительно неплохих примет […]

  97. Skakunov Alexander on November 2nd, 2007 3:32 am

    Our project seems to be doomed too :]
    Thanks, very funny article!

  98. Marco on November 4th, 2007 2:48 pm

    “FrontPage is your web page editor of choice”

    “Your SCRUM team consists of 1”

    Hilarious!

    Thanks for this article!

    Keep on bloggin,,,

  99. 2 « My Weblog on December 3rd, 2007 7:37 am

    […] 101 Ways To Know Your Software Project Is Doomed […]

  100. FollowSteph.com - Quick Links on January 17th, 2008 9:21 pm

    […] 101 Ways To Know Your Software Project Is Doomed Almost funny except that it’s all too real. […]

  101. Mind Gravy » Blog Archive » links for 2008-04-02 on April 2nd, 2008 6:35 am

    […] 101 Ways To Know Your Software Project Is Doomed (tags: humor programming) […]

  102. Doom » Blog Archive » 101 Ways To Know Your Software Project Is Doomed on April 10th, 2008 6:09 pm

    […] read more | digg story […]

  103. 101 formas de saber si tu proyecto está condenado al fracaso | Seraphinux on April 16th, 2008 7:50 am

    […] | 101 formas de saber que vuestro proyecto software está condenado al fracaso Link: Codesqueeze | 101 Ways To Know Your Software Project Is Doomed Categoria Geek […]

  104. Hacheka Kacharras » Blog Archive » Frase del dia on April 16th, 2008 1:27 pm

    […] Sacado de 101 maneras de saber que tu proyecto está condenado […]

  105. kill -9 me » Blog Archive » 101 maneras de saber cuando tu proyecto fracasará on April 17th, 2008 3:04 pm

    […] que ya se haya vendido [nota cultural]. Creo que la lista hasta se queda corta. La lista completa esta por aquí y hay algunas que casi me sacan la lagrimita […]

  106. software » Blog Archive » 101 Ways To Know Your Software Project Is Doomed on April 19th, 2008 6:38 pm

    […] read more | digg story […]

  107. çiçek on April 26th, 2008 3:12 am

    Thanks for a funny list

  108. 101 Ways To Know Your Software Project Is Doomed « Mozman34’s Weblog on April 28th, 2008 4:54 pm

    […] read more | digg story […]

  109. Online cicek on June 4th, 2008 4:35 pm

    Your manager could be replaced by an email redirection batch file.

    That’s very funny 🙂

  110. RipiRip.Org on June 16th, 2008 8:36 am

    funny vhahaha

  111. çiçek on July 8th, 2008 12:56 am

    that’s very funny:)

  112. rugs on July 10th, 2008 3:05 am

    Ha ha, I liked the second one : “You start hiring consultants so they can take the blame.” Now, isn’t that like so true? The minute we see a whole lot of consultants come in, we know something’s gone wrong. Either we’re all going to lose our job, or we’re looking at some way of shifting the blame for why things have gone so horribly bad. Loved the Napkin as well – that was too funny.

  113. yahoo on August 7th, 2008 5:14 pm

    New #1:

    Your sprint planning meetings are so broken that your sprint planners skip them to attend sprint planning conferences.

  114. Jay on August 14th, 2008 9:50 pm

    Hahahaha! This is so funny! number 51 it is very funny! “Your lead web developer defines AJAX as a cleaning product”

  115. 101 Ways To Know Your Software Project Is Doomed - [neoRackle Kawayi] on August 28th, 2008 3:07 am

    […] 101 Ways To Know Your Software Project Is Doomed […]

  116. web design company on September 11th, 2008 11:34 am

    It’s too bad the Vista dev team didn’t read this.

  117. Coder Blues on September 13th, 2008 9:05 pm

    This should be mandatory reading for all employees. Funny and sad at the same time

  118. 101 Ways to know your software project is doomed : Coder Blues on September 15th, 2008 7:36 pm

    […] 101 Ways to know your software project is doomed. […]

  119. 101 Ways To Know Your Software Project Is Doomed | der-eremit.de on September 22nd, 2008 1:30 am

    […] 101 Ways To Know Your Software Project Is Doomed […]

  120. kieron laurence on October 1st, 2008 4:39 am

    haha its my birthday and this made my day ive never laughed so much, number one was a little bit rude but fuck it who cares hahahaha god im laughing like a little girl who just got her new pony.

  121. Nishchay Shah on October 21st, 2008 11:36 am

    “Now, Iphones take care of your million dollar software” !!

    “devs complain .. sorry there can’t be a launch tonight as I am vacationing in hawaaii where 3g is weak ” => thus can’t login through my top SSH APP

  122. 103 Ways To Know Your Software Project Is Doomed | Think Lamp on October 21st, 2008 11:45 am

    […] inspired from: codesqueeze.com […]

  123. Effectize on October 27th, 2008 10:59 pm

    89 Ways for You to Become the Coolest Programmer in the World…

    Since there are dozens of posts on becoming a better developer, but no single post with all the advice you need, perhaps, you’ll find this short guide useful.
    1. Learn the Skills You Need

    Learn the programming basics

    “The goal of this guide is to b…

  124. Etienne Savard on November 11th, 2008 2:46 pm

    […]What make this list so funny (for a software developer) is that many items are so close to reality — or simply true![…]

  125. amasra on February 1st, 2009 4:34 am

    that’s very funny:)
    hahahaha 🙂

  126. PM Hut on February 7th, 2009 10:02 am

    Published a similar list, “10 Signs That You Should Give Up on Your Project”

    This can be easily applied to your list: “The original project charter has nothing to do with what you are doing now”

  127. 101 formas de saber que tu proyecto está condenado al fracaso on February 16th, 2009 4:52 am

    […] VariableNotFound ha traducido, con el previo consentimiento de su autor. Post original en inglés: http://www.codesqueeze.com/101-ways-to-know-your-software-project-is-doomed/ sin comentarios en: tecnología, software karma: 7 etiquetas: gestion de proyectos, […]

  128. 101 formas de saber que tu proyecto está condenado al fracaso | sudo on March 1st, 2009 11:42 am

    […] Post original: 101 Ways To Know Your Software Project Is Doomed […]

  129. neon on March 4th, 2009 6:03 am

    VariableNotFound ha traducido, con el previo consentimiento de su autor. Post original en inglés:

  130. Hazel Q. on April 17th, 2009 3:48 pm

    hahaha this list is somewhat true and very funny 😀

  131. Weeks Nerdly » Blog Archiv » Weeks Nerdly #12: unser Senf zur WWDC on June 18th, 2009 10:44 am

    […] Kühler Zalman ZM-NC1000S Push the Button iCascade MTV: True Life, i am addicted to video games 101 ways to know your software project is doomed/    Standard Podcast: Play Now | Play in Popup | Download Datum 18. June 2009 […]

  132. QA Hates You » Blog Archive » Link Dump from My Open Tabs on September 4th, 2009 7:09 am

    […] 101 Ways To Know Your Software Project Is Doomed. […]

  133. 101 Ways To Know Your Software Project Is Doomed | kran.lt on September 24th, 2009 11:21 am

    […] iš Categories: linksmai, programavimas Tags: linksma, programavimas Comments (2) Trackbacks (0) Leave a comment Trackback […]

  134. sevgiliye hediye on October 1st, 2009 2:10 am

    You think about getting a new job so you don’t have to support the POS you’re building

  135. Chand on November 8th, 2009 4:18 am

    This is soooo true for me

  136. A bit of humor for the day — is your software project doomed? | AMD Developer Central Blogs on February 22nd, 2010 2:42 pm

    […] this list floating around recently, it has been digg’d up to the top. It’s the “101 Ways To Know Your Software Project Is Doomed” at codesqueeze. Throughout my various jobs, I’ve experienced 12 of these items — […]

  137. Content-Stealing Jerks | Kevin William Pang on March 11th, 2010 8:35 pm

    […] http://www.codesqueeze.com/101-ways-to-know-your-software-project-is-doomed/ […]

  138. Worse Software « Avventure sul Web on May 7th, 2010 5:20 pm

    […] Segnalato da Luca su Twitter questa interessante lista: 101 Ways To Know Your Software Project Is Doomed. […]

  139. Doomed Software Project? | Ask the Right Question on May 9th, 2010 2:45 pm

    […] 101 Ways to Know Your Software Project is Doomed […]

  140. Nurmelat » 101 tapaa tunnistaa umpikujassa oleva ohjelmistoprojekti on July 15th, 2010 1:16 pm

    […] via codesqueeze.com […]

  141. celebrity fuck you on August 24th, 2010 12:27 pm

    Sign: zdbrw Hello!!! pwvep and 4852wgqyupwtyn and 1127 : Hi! I was surfing and found your blog post! nice! I just came across your blog and wanted to say that Ive really enjoyed it.

  142. Otomasyon on September 7th, 2010 12:58 am

    otomasyon sistemleri

  143. Kevin Thompson on September 7th, 2010 6:14 pm

    Great List. Some of the points made me laugh

  144. koltuk yıkama on September 27th, 2010 4:52 pm

    hm yeah and about those TPS reports…We’re gonna need you to use those new cover sheets

  145. Crawford on October 8th, 2010 4:16 am

    One of the best articles I have read in a while. Thanks and keep up the good work.

  146. Juaramir.com » Blog Archive » 101 formas de saber que vuestro proyecto software está condenado al fracaso on January 18th, 2011 9:20 pm

    […] Aquí tenéis algunas traducidas al castellano por mundogeek. El resto las pueden leer en inglés en Codesqueeze. […]

  147. How to cancel a failing project gracefully « Fear No Project – A Project Management Blog on September 8th, 2011 3:16 pm

    […] I would like to add a few of my own observations – I have borrowed a couple, some tongue in cheek, from Code Squeeze’s “101 Ways to Know Your Software Project Is Doomed.” […]

Max Pool - © 2024 - {codesqueeze}. Sycorr Banking Solutions