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

Ahh, a team of generalists where nobody is spectacular at anything in particular. Throw in a Kanban board, and you've really got a recipe for success.



I've seen teams of "specialists" be about as doomed before. I knew a few "Rubyists" who would not touch any other language than Ruby. No JS, No HTML, No SQL. Only pure Ruby.

Get in a bind and need a full court press to get some unit tests out, QA automation, or some queries tuned? Too bad. Everyone is in their silo and heading home at the steam whistle at 5pm.

On my teams of devs that all knew a lot of areas, we could pivot to get whatever had to be done complete at the end of the release rather than being marooned on our daises.


That's one extreme. Middle ground would be to recognize and capitalize on strengths, while taking advantage of anyone's ability and willingness to fill in a role until the better qualified individual comes off his urgent assignment or personal issue.


This shouldn't be the case. You can be spectacular at X and still very good at Y and Z. Even more likely, that broader view and experience would help to be specacular at something.




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

Search: