编码规范是技术上的遮羞布（Encoding specification is technically a fig leaf）.docVIP

下载本文档

7
0
约5.48千字
约 5页
2017-09-02 发布于河南
举报
版权申诉

编码规范是技术上的遮羞布（Encoding specification is technically a fig leaf）.doc

1、有哪些信誉好的足球投注网站（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

编码规范是技术上的遮羞布（Encoding specification is technically a fig leaf）

编码规范是技术上的遮羞布（Encoding specification is technically a fig leaf） As every programmer knows, you need a rigorous coding specification in a software company. Every programmer also knows that every programmer is struggling to make this set of rules according to his programming habits. Just entering a new company, every programmer would be desperate and afraid of the set of coding rules that some powerful architects arbitrarily specify. Throw out the coding specifications and let the programmer play free, and youll get more benefits. From the point of view of strengthening code unity, victory can not solve the problem at all. The technical specification is encoding a fig leaf. At nearForm, I never thought of making such a rule because I wanted everyone to program just the way they liked. The world is too noisy. The revival of JavaScript bears full responsibility for this. In particular, there is a feature: an optional semicolon. Numerous claims, conjectures, and objections poured in. Stop, actually write some code, OK?. You know who Im talking about?. The intention is good, the release of various JavaScript encoding programmers Daisen norms and style guide. Youre all wrong. Please stop the act of saving the world. Where do coding specifications come from? The process is this: when you start coding, what do you do with what you dont know?. Its fun, its a game, until youre blind to one eye. Once youve been injured too many times by your own garbage code, you begin to know youre a newbie. So you start on the road to the Programming Guru, and you chew the code, the programmer, and, of course, Joel. After that, things began to happen. On the way to a pilgrimage, you understand the scriptures. Your skills make you a star of programming. Your efficiency has doubled. Now, you want to spread to the world. The knowledge that you have today will also save others. You win, you preach, haunt you. You coach your boss to adopt the best practices, practices, and development standards. An