I think part of why (some)? engineers may not give a shit about the project they're working on isn't necessarily because they have no interest in it, but because they haven't met anyone with an interest in it. In github's case, it just happens to be themselves.
I like to know what I'm doing actually matters. Meeting people my stuff impacts helps with that.
Whatever the purpose of IT middle management, it does not appear to accomplish much.
I wish I could give you ten upvotes. I get a lot out of interacting with the people that actually use my software. It makes things more personal and that makes me more motivated to work on a project. And the feedback helps to make what they actually want instead of having to second-guess, or build to some abstract specs.
That the project is technically interesting/challenging also goes a long way, of course, but that's not everything.
Worst would be a project that is boring and you don't know whether anyone, including yourself, is ever going to use it.
In essence, I think if they were crappy to work for, they wouldn't have an easy time hiring, because a lot of the cool stuff they do just wouldn't happen.
I'm currently unemployed by choice and what they describe is basically a dream job, imho.
But it's easy to see how a programmer was hired and came to work on a project he didn't like. He was hired to work on a project he was interested in, and was moved over to a project he dreads. They won't stay long though.
Which is the difference GH has from many other places: The work is interesting (to many). Therefor they have an easy time hiring and retaining good employees.
I throwing hipster around is a waste of time, especially considering these are extremely successful hipster programmers.
Create product everyone loves, create environment everyone loves to work in, live in San Francisco: fucking hipsters.
>He was hired to work on a project he was interested in, and was moved over to a project he dreads. They won't stay long though.
There is always shit work to do. It's a constant of the universe - there will always be work you're not super interested in. The difference is, is the rest of your job good enough to suck it up and take one for the team?
(Do you even think of it in terms of taking one for the team, or do you think you are just being shat upon?)
Even if they were crappy to work for they would probably have an easy time hiring.
THAT SAID, "finishing the internal CRM system" is a problem that happens in organizations an order of magnitude larger, methinks.
My finishing platitude is, how did you hire - and why do you retain - engineers that don't give a shit about the project they're working on?
Also, why is your PM screaming? A project meeting deadlines is his or her responsibility. Sounds like you have a crap PM to boot.