Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#84

Open
wangwangwar opened this issue Dec 16, 2017 · 1 comment
Open

#84

wangwangwar opened this issue Dec 16, 2017 · 1 comment

Comments

@wangwangwar
Copy link
Owner

wangwangwar commented Dec 16, 2017

前几天老师提到一个观点,在软件开发过程中,在开发过程发现并解决问题,比以后客户反馈问题成本更低。更进一步,在需求分析阶段,排除一些不合理或过于复杂的需求,比起后面开发到一半甚至结束后才发现问题,又要节约大量成本。再进一步,在市场调研阶段,如果能合理调查分析,选择合适的市场和产品,再再进一步,,,在越上游做优化,得到的收益越大。你会发现,为什么牛逼的人都在谈宏观,方针,理论。

细看开发过程。比起在 JavaScript 里花式炫技,选择强类型的语言虽然写起来很老气但是更靠谱。更进一步,如果整个系统架构更灵活开放适于扩展和变化,业务代码可以保持足够简单清晰,选择什么语言其实关系不大了。再进一步,如果盈利模型更加简单快速,什么系统架构都无所谓了。比如XX连公司都不用开,忽悠你们来投资好了。

所以架构师就是要比码农值钱。老板知道架构靠谱了,可以支撑屎一样的业务代码。

@wangwangwar
Copy link
Owner Author

从大公司可以学到的东西通常都比较“大”,比如工作流程,架构,管理。学到了再到小公司可以复制。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant