3 ms·

Can you give some examples of some bad habits you might learn? 40 hour weeks?

by slewis 15y ago

bretthellman 15y ago
During my first month at Intuit as Product Manger who coded, I pitched some ideas to my leader at the time. His feedback was to try to come up with ideas that were more practical. That pretty much sums it up. To credit Intuit, that leader is no longer with the company. The problem imo is this type of thinking shapes the way people think. On the flip side, VCs/Investors/Angels are only interested in the big ideas that sounds crazy that big companies reject.
- Choppen5 15y ago
  >only interested in the big ideas that sounds crazy that big companies reject. Great! I've got that covered... we'll see though seems like a lot of VCs like safe a sure bets, proof that it is already working.
pkteison 15y ago
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.

Can you give some examples of some bad habits you might learn? 40 hour weeks?

by slewis 15y ago

Can you give some examples of some bad habits you might learn? 40 hour weeks?

During my first month at Intuit as Product Manger who coded, I pitched some ideas to my leader at the time. His feedback was to try to come up with ideas that were more practical. That pretty much sums it up. To credit Intuit, that leader is no longer with the company. The problem imo is this type of thinking shapes the way people think. On the flip side, VCs/Investors/Angels are only interested in the big ideas that sounds crazy that big companies reject.

Choppen5 15y ago
>only interested in the big ideas that sounds crazy that big companies reject. Great! I've got that covered... we'll see though seems like a lot of VCs like safe a sure bets, proof that it is already working.

pkteison 15y ago

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.