Excellent post! I really enjoy reading your blogs. One question- I heard Google engineers work overtime a lot. Is it because they spent one day on their own project and then have to work over time in the other 4 days to catch up?
Overtime? What's that?
Dr. Whittaker, I'm a huge fan. Great post, although I'm curious about what sounds like an anti-startup bias.."Any company worth working for has any number of projects that are worth working on.""Anything more is so dot com."IIRC, Google sprang up from a small group working on a single project (search) in the midst of the dot com era..
More often that not perks are offered just because it's easier than building a strong engineering culture.As a rule of thumb I just distrust companies and engineers putting perks first.
Great post James, wish more companies would realize these three points.
willy, I couldn't agree more. Faizal: touche! It's amazing how much big company thinking has crept into my soul!
We need to implement this at Zappos :). TY for an awesome post!
I don't fully agree with the 'Project Mobility' concept. While I understand the importance of having fresh ideas flowing, and it is good to rotate staff, I see a downside. In my organization, there are quite a few projects that require deep domain knowledge, and people with many years in it are invaluable to the organization. I have seen far too many people coming in due to 'mobility' and breaking things that were built on the solid foundation of experience and deep realization.
Excellent....Keep posting things like this dude....subscribed
The comments you read and contribute here belong only to the person who posted them. We reserve the right to remove off-topic comments.