«« Next » « Previous
«« Next » « Previous

Link Details

Link 47817 thumbnail
User 201185 avatar

By xelipe
via juixe.com
Published: Oct 14 2007 / 17:51

Top reasons indicating you might be in a broken project… If two or more of the reasons listed apply to you, find yourself another job.
  • 9
  • 0
  • 2117
  • 987

Comments

Add your comment
User 236137 avatar

dzonelurker replied ago:

0 votes Vote down Vote up Reply

From my own experience I can confirm:
* Everything starts to look like it would be quicker to rewrite
* Everyone on the project has architect on their business card
* Conversations always start with ‘oh that, that is really simple…’ followed by a thirty minute discussion of what is required
* The Project X is a homegrown web framework
* The lines of XML outnumber the lines of Java 10 to 1
* You ask about JUnit tests and you get blank stares from everyone

User 181930 avatar

jwenting replied ago:

0 votes Vote down Vote up Reply

"The guy that is supposed to train you, throws a file full of notes, and runs away"

What about being brought in to replace the guy who died (actually had that happen)?

User 200744 avatar

johannz replied ago:

0 votes Vote down Vote up Reply

I've had the consultant that was hired to replace me have a heart attack a couple of months into the project. Makes me glad I left

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (9)



Voters Against This Link (0)