blocks|key|3926895|text|你可能不得不更仔细地看看你的店铺做错了什么，他们做对了什么。您实际上可以在那里更改什么？您可以对您自己的实践进行哪些更改，以提高您或您团队的技能？在一个根深蒂固的商店里实现改变是困难的。尝试提出代码审查(首先对你的代码)，这可能会导致讨论。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3926896|对于有形物品，我会看看Scott+Meyers的Effective+C%2B%2B等。发展你的技能集，你要么帮助周围的人提高水平，要么转移到愿意的商店。另外，看看四人帮的Design+Patterns一书。|offset|length|3926897|entityMap|0|LINK|mutability|MUTABLE|url|http://www.aristeia.com/|1|https://rads.stackoverflow.com/amzn/click/com/0201633612^0|0|B|C|0|29|F|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]|$D|U|E|V|1|W]]|A|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]|N|$5|I|J|K|A|$L|O]]]]

You probably have to look more closely at what it is your shop does wrong and what they do right. What can you actually change there? What can you change about your own practices that will improve your skills or that of your team? It can be difficult to realize change in an entrenched shop. Try proposing code reviews (on your code first), which could lead to discussion.

For tangible items, I'd look at <a href="http://www.aristeia.com/" rel="nofollow noreferrer">Scott Meyers</a>' Effective C++, etc. Develop your skillset and you will either help improve others around you or move on to a shop that will. Also, look at the Gang of Four's <a href="https://rads.stackoverflow.com/amzn/click/com/0201633612" rel="nofollow noreferrer" rel="nofollow noreferrer">Design Patterns</a> book.

blocks|key|793494|text|代码审查是我发现的提高整体代码质量的最好方法。审查来自不同个人的相互帮助的代码可以提高对不同技术的总体认识，并有助于传播最佳实践。雇佣一个比你更有经验的人也是一个很好的工具，但实施起来有点单调乏味。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|793495|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Code reviews are the best way I found to improve code quality overall. Reviewing code from different individuals helping each other increases general awareness of different techniques and help propagate best practices. Hire a person more experienced than you are is also a good tool but it is a bit more tedious to implement.

blocks|key|3927652|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3927653|阅读好的编程书籍|unordered-list-item|3927654|从别人的代码中学习-开源项目是开始|3927655|的最好地方，定期阅读好的博客和论坛-+Sutter+mill，Coding+Horror，Martin+fowler等|3927656|代码评论|3927657|<+code+>H19单元测试|3927658|使用Boost、STL等好的库。也了解他们的implementation|3927659|3927660|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|Q|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|R|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|S|7|@]|8|@]|9|$]]|$1|F|3|G|4|C|6|T|7|@]|8|@]|9|$]]|$1|H|3|I|4|C|6|U|7|@]|8|@]|9|$]]|$1|J|3|K|4|5|6|V|7|@]|8|@]|9|$]]|$1|L|3|M|4|C|6|W|7|@]|8|@]|9|$]]|$1|N|3|-4|4|5|6|X|7|@]|8|@]|9|$]]|$1|O|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]]|P|$]]

<ul>
<li>Reading good programming books</li>
<li>Learning from other's code - Open source projects are the best place to start</li>
<li>Read good blogs and forums regularly - Sutter mill, Coding Horror, Martin fowler etc</li>
<li>Code reviews</li>
<li>Unit tests</li>
<li>Using good libraries like Boost, STL. Also understanding their implementation</li>
</ul>

blocks|key|3926779|text|以身作则总是一件好事，尽管让别人相信你的例子比他们目前所做的要好，但这并不容易。通过代码审查的建设性批评可能是您温和地建议您的同事如何工作的替代方法的最佳选择。关键的一点是要让别人相信，你提出的建议确实更好，让他们能够欣赏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3926780|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Leading by example is always a good thing, though convincing others that your example is better than however they're currently doing it is not so easy. Constructive criticism through code review is probably your best bet for gently suggesting alternative approaches to how your colleagues work. The key point is to convince others that what you're proposing really is better in a tangible way that they can appreciate.

blocks|key|3081096|text|有时人们不得不看到你的方式比他们的方式工作得更好。通常很难让人们改变。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3081097|如果你还没有写单元测试，你有没有考虑过？我发现它真的改进了我的生产代码，让我更有信心相信我正在写的就是我应该写的。|3081098|我喜欢Jason关于代码评审的想法。它们可以是有用的，也可以是争论的地方--这真的取决于你如何定下基调。|3081099|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Sometimes folks have to see that your way is working better than their way. It is often difficult to make people change.

Have you considered unit test writing if you don't do that already? I've found it to really improve my production code and give me more confidence that what I'm writing is what I'm supposed to be writing.

I like Jason's idea about code reviews. They can be helpful or they can be a place for arguing - really depends on how you set the tone.

blocks|key|5336850|text|设计和设计好项目，这样开发人员就不会采取不同的方法来破坏质量。如果你设置了一个好的设计，人们只需要遵循路线，他们就会自动学习|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5336851|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Architect and design the project well so that none of the developers will be able to take a different route to violate the quality. If you set a great design, people will just follow the route and they will automatically learn

blocks|key|797555|text|可以尝试的其他方法是添加unit+tests和documentation。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|797556|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/googletest/|1|http://www.boost.org/doc/libs/1_36_0/libs/test/index.html|2|http://www.doxygen.org/^0|C|4|0|H|5|1|N|D|2|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]]]

Other things to try is to add <a href="http://code.google.com/p/googletest/" rel="nofollow noreferrer">unit</a> <a href="http://www.boost.org/doc/libs/1_36_0/libs/test/index.html" rel="nofollow noreferrer">tests</a> and <a href="http://www.doxygen.org/" rel="nofollow noreferrer">documentation</a>.

blocks|key|5336979|text|尽管这可能不是一个直接的答案，但我建议您选择Code+Complete这本书。我发现它是学习如何成为一名更好的程序员的最好资源。如果你通读了整本书，并理解了它所讨论的内容，你就会真正地学习如何改进自己和代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5336980|entityMap|0|LINK|mutability|MUTABLE|url|http://www.cc2e.com/^0|M|D|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Although this probably isn't as direct of an answer, I recommend you pick up the book <a href="http://www.cc2e.com/" rel="nofollow noreferrer">Code Complete</a>. I find it to be the best resource for learning how to be a better programmer. If you read through the whole book and understand what it talks about, you'll really learn how to better yourself, and your code.

blocks|key|3927547|text|我发现编写单元测试对代码质量有很大帮助--这意味着你必须考虑你的代码将如何与测试和代码的其他部分进行交互。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3927548|同行代码审查:检查代码的质量也会让程序员考虑如何编写代码。|3927549|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I find writing unit tests helps code quality a lot - it means you have to think about how your code will interact with the tests and other parts of the code.

Peer code-review: Checking quality of code will also make the programmers think about how they write the code.

blocks|key|3927592|text|你意识到还有改进的空间，并渴望尝试实施一些改变，这是很棒的。我建议阅读James+Shore的19-week+diary，他在其中记录了他在公司实施敏捷开发的步骤。这是一场艰苦的战斗，但他的经验表明，你可以有所作为。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3927593|entityMap|0|LINK|mutability|MUTABLE|url|http://jamesshore.com/Change-Diary/^0|1B|D|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

It's great that you recognize that there's room for improvement and have the desire to try to enact some change. I suggest reading James Shore's <a href="http://jamesshore.com/Change-Diary/" rel="nofollow noreferrer">19-week diary</a> where he documents the steps that he went through to enact agile development at his company. It's a hard fight, but his experience shows that you can make a difference.

blocks|key|3081723|text|仅仅问这个问题就是一个很好的开始。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3081724|具体地说，您可以：|3081725|3081726|承认你的代码很烂，开始请其他人(最好是有更多经验的人)审查你的代码|unordered-list-item|3081727|实现一个持续构建的服务器-你必须是第一个使用这个|3081728|的人有勇气，因为这可能是困难的|3081729|<代码>H19谦虚<代码>H210<代码>H111阅读代码完整<代码>H212<代码>H113使用鼓励团队合作的软件开发方法。一些敏捷方法非常擅长这个|3081730|阅读开发博客|3081731|Get+in+a+user+group|3081732|3081733|改变是困难的，你必须成为第一个改变的人。|3081734|如果你在一个别人都很开心的环境中工作，那么你的工作将会很艰难。坚持不懈地想要提高代码质量。|3081735|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|11|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|13|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|O|5|G|7|15|8|@]|9|@]|A|$]]|$1|P|3|Q|5|G|7|16|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

Just asking the question is a good start. 

Specifically you can:

<ul>
<li>Admit that your code sucks</li>
<li>Start asking others, preferably others with more experience, to review your code</li>
<li>Implement a continuous build server - you have to be the one who uses this first</li>
<li>Have courage because this can be difficult</li>
<li>Be humble</li>
<li>Read Code Complete</li>
<li>Use a software development methodology that encourages team work. Some of the agile methodologies are really good at this</li>
<li>Read development blogs</li>
<li>Get involved in a user group</li>
</ul>

Change is hard and you have to be the one who changes first.

If you are working in an environment where others are happy the way it is you are going to have rough going. Be persistent about wanting to improve code quality.

blocks|key|5337335|text|我是有偏见的(由于我的工作)，但根据您的预算(如果存在)静态分析是一个可能的选择。有许多不同类型的工具，其中一些还包括编码标准强制检查。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5337336|如果您使用g%2B%2B，您可能能够从-Weffc%2B%2B选项获得基本的帮助。|5337337|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I am biased (as a result of my work), but depending on your budget (if it exists) static analysis is a possible option. There are lots of different types of tools, some of which also include coding standard enforcement checking..

If you use g++, you might be able to get a basic amount of help from the -Weffc++ option.

So, in reading this site, it seems that the shop in which I work does a lot of things wrong and some things right. How can I improve the code that I work with from my colleagues? The only thing I can think of is to lead by example - start using Boost, etc. Any other thoughts?

Improving the quality of code?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

所以，在阅读这个网站时，我工作的商店似乎做了很多错误的事情，也做了一些正确的事情。我如何改进我从同事那里使用的代码？我唯一能想到的就是以身作则--开始使用Boost，等等。还有其他想法吗？

问提高代码质量？
EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问提高代码质量？EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问提高代码质量？
EN