{"action":"opened","issue":{"url":"https://api.github.com/repos/amio/amio.github.com/issues/13","labels_url":"https://api.github.com/repos/amio/amio.github.com/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/amio/amio.github.com/issues/13/comments","events_url":"https://api.github.com/repos/amio/amio.github.com/issues/13/events","html_url":"https://github.com/amio/amio.github.com/issues/13","id":68010403,"number":13,"title":"关于分工和全栈","user":{"login":"amio","id":215282,"avatar_url":"https://avatars.githubusercontent.com/u/215282?v=3","gravatar_id":"","url":"https://api.github.com/users/amio","html_url":"https://github.com/amio","followers_url":"https://api.github.com/users/amio/followers","following_url":"https://api.github.com/users/amio/following{/other_user}","gists_url":"https://api.github.com/users/amio/gists{/gist_id}","starred_url":"https://api.github.com/users/amio/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amio/subscriptions","organizations_url":"https://api.github.com/users/amio/orgs","repos_url":"https://api.github.com/users/amio/repos","events_url":"https://api.github.com/users/amio/events{/privacy}","received_events_url":"https://api.github.com/users/amio/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-13T05:24:08Z","updated_at":"2015-04-13T05:24:08Z","closed_at":null,"body":"有一些还不确定的想法，记下来讨论。\r\n\r\n- __全栈是比分工更美好的形式__  \r\n  更好的整体协调，得到更趋近完美的产品结果，长起来看也是更高的效率。\r\n- __分工是为了提高效率__  \r\n  从最早的人类男打猎女哺乳的分工开始，就是为了提高效率，直到现代社会超级细节的分工方式，这一点依然没变。\r\n- __两个工具：专职 vs 全栈__\r\n  - 在水平较低的时候，专业化带来更大的效率提升；\r\n  - 所以可以不停细分，再细分，持续提高效率。\r\n  - （分工有一个潜在问题是引入了沟通成本）\r\n  - 通过细分专业把效率提升到一定阶段会有瓶颈，这个拐点是：沟通负担的提高压过了专业化效率提升的益处\r\n  - 这个拐点之后，向全栈发展会带来更好的成本收益比\r\n  - 全栈在提高质量方面的意义要高过提高效率\r\n\r\n基于碰到的具体个案现状而言：\r\n- 全栈需要建立在团队高水平专业化基础上，已经在专业分工提高效率方面达到了拐点\r\n- 全栈解决的问题是重要不紧急的"}}