Hacker News new | past | comments | ask | show | jobs | submit login

After reading that, I cannot help but think that this person/company would be positively horrible to work for. I find myself wondering what his goal was when publishing that, because it didn't read (to me) as positive or helpful.



Personally, I found it exceptionally well summarized. For me, the usefulness is in striving to not fall into one of these categories (as the conclusion hints, I certainly have the potential to end up that way from time to time). I could translate these anti-patterns to a list of advice (though I think it's better to read the original post):

Thinker: Design, but also don't hesitate to execute.

Talker: Discuss, but make sure the the discussion is fruitful, succinct and to the point.

The Entitled: Don't care too much about my title or titles of others - we are all working together to achieve some goal.

The Owner: Be open to suggestions and changes by others to ideas and code that originated with me.

The Recluse: No matter my specialization, I have to be able to pick up new technologies and processes, instead of blindly delegating every item I feel is not part of my expertise.


Me too. I wouldn't want to work for Eric. He is a management anti-pattern.


And one that hassn't heard of Belbin and his work on team roles.My top 3 where Plant, Resource Investiagtor and Chair


Ditto.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: