The 501 Developer Manifesto

Talk about a false dichotomy. I evade this problem by being friends with the people I work with.

Overall, I think there are some good distinctions made here. And there is a good point to the thing: “To us it is just a job, but we still do it well.” I almost feel like the page should lead with that. That this isn't an indication that this approach is better than the other approach, simply that it's… Different.

Maybe I don't have a family nearby right now. Maybe I am at a point in my life where I can have free snacks and free time, where I can have sustainable pace AND muscle-man heroics AND still enjoy life outside of work. But that's beside the point of the page. The point here is to understand that not everyone has that perspective, and that it's important to respect those that leave their work at the office and dedicate more time to all the other things than you do (if you're one not one of the “501 developers”).

The more interesting part is the second half, in the smaller print where the author addresses his teammates. He uses words like "respect", but what he's saying feels contemptuous and passive-aggressive. That's the real tell here. Well, that and the suggestion that he doesn't believe in what he's working on. No wonder he feels like checking out every day.

Does it matter what time someone leaves? Only if people feel it does. What matters is that a team be aligned. If there's disharmony, work it out. If you can't work it out, change the team. Writing a "manifesto" is not working it out (though it might start a real conversation).

Personally, I want teammates who are passionate about doing great work. Come and go whenever works for you. But passion doesn't get turned off like a light switch at the same time every day.

I certainly don't see that in what bguthrie wrote.