-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
精读《可维护性思考》 #359
Comments
然而确定边界是一个十分难的问题. |
和leader的能力息息相关 |
|
而且,复杂度也不是一劳永逸的,随着功能的迭代,会一点点累积,就像家里不想洗的衣服,一件两件一直堆到一筐,最后就洗不动了 |
|
从另一个角度看,如果整体设计就不合理,基本上是没什么希望推倒重来了,必须来一次彻底重构。 |
随着业务的发展,团队的扩增,哪怕之前被认为是“完美”的架构和代码,也可能变得不适用,以及形成"shit mountain",所以需要持续的做好一件事情的能力。 |
是的,所以也有话说,架构是长出来的,而不是高屋建瓴提前规划出来的。 |
本周又是一个原创文章,谈谈怎么样算好的代码可维护性。
精读《可维护性思考》
The text was updated successfully, but these errors were encountered: