如何成为一个高效的程序员(How to become an efficient programmer).docVIP

如何成为一个高效的程序员(How to become an efficient programmer).doc

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

如何成为一个高效的程序员(How to become an efficient programmer) 1., active learning, new technology and non-technical two aspects of knowledge, poor programmers only when it really can not begin to learn knowledge. Good programmers take the initiative in learning new skills. Programmers will not only to learn new skills and knowledge, but also learn non technical knowledge, have an open mind on a variety of knowledge sources, and some people do not like to rest on its laurels. Specifically, not only a good programmer in begin to learn XAM by WPF project; good programmers a year ago to learn the XAM, because he felt it very interesting; but great programmers also read the design guidelines, the availability of WPF applications (usability) or what similar theory the course of study, so he can make exceptional UI. 2., pragmatism without dogma and adherence to unwritten programming rules is often a luxury, and not many developers can afford it. If your specifications are not written by the top developers, nor are they written by the top developers, I can assure you that you may not be able to afford them. I have often been able to meet some programmers who cannot or refuse to do a task just because they are not accepted for best practice. Which business needs are seldom on the demand of the technology adopted; no one would say, that we should not put the needs of written specifications, because to achieve this demand, the programmer had to write a very smelly code. At the end of the day, the programmers task is to generate a valid application, and not to demand perfection in terms of technology. Im not defending junk code. What Im trying to say is that there are always times when you write some code that youll never show as an example of the right way to do things. If there is only one type of writing, then the code is not a bad code - but make sure you have exhausted all other possible scenarios. 3. know how to find the answer through the research through the research can not only

您可能关注的文档

文档评论(0)

f8r9t5c + 关注
实名认证
文档贡献者

该用户很懒,什么也没介绍

版权声明书
用户编号:8000054077000003

1亿VIP精品文档

相关文档