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

I don't think this is the best analogy. Understanding a "full stack" isn't so you can manage specialists, it's necessary to _be_ a specialist so you can build something that you know doesn't have an obviously inherent pitfall. It's so you can prototype something without needing the time and attention of another specialist.

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