Re:Why I Quit Intuit and Started Hall.com - An Update
by pkteison on Monday October 10, 2011 @02:21PM
(#3095074)
Bad habits I observed at a very big company:
* I don't know [insert new technology here], I'd rather stick with [insert thing I know well here]
* That isn't my problem
* Is there a ticket for that?
* Can you file a ticket for that?
* I've hit my 40 hours
* But it's always been done this way.
* We need to schedule a meeting
* [20 people in one meeting]
* [20 people in one meeting every day for a month]
* [More time in meetings than programming]
* We can't use that open framework, who will support it?
* We need this to be on [X] hardware platform because that's what ops has available
* What does the vendor say / Has architecture reviewed and approved this technology? (this may have a useful point somewhere, but I have seen arch. approval mainly be a function of who took the arch team out to a nice restaurant or went golfing with them.)
* We can't use [insert appropriate thing to use] because it's too hard. We should use [simpler thing] because our devs can understand it better.
I know this list reads almost a stereotype of big dev at this point, but I personally saw all of these. I could probably come up with a few dozen more given a few hours of cringing.
* I don't know [insert new technology here], I'd rather stick with [insert thing I know well here]
* That isn't my problem
* Is there a ticket for that?
* Can you file a ticket for that?
* I've hit my 40 hours
* But it's always been done this way.
* We need to schedule a meeting
* [20 people in one meeting]
* [20 people in one meeting every day for a month]
* [More time in meetings than programming]
* We can't use that open framework, who will support it?
* We need this to be on [X] hardware platform because that's what ops has available
* What does the vendor say / Has architecture reviewed and approved this technology? (this may have a useful point somewhere, but I have seen arch. approval mainly be a function of who took the arch team out to a nice restaurant or went golfing with them.)
* We can't use [insert appropriate thing to use] because it's too hard. We should use [simpler thing] because our devs can understand it better.
I know this list reads almost a stereotype of big dev at this point, but I personally saw all of these. I could probably come up with a few dozen more given a few hours of cringing.