识别代码改进
我们刚刚经历了一次相当大的系统重写，我被要求查找和识别已改进的代码区域。 以此向客户证明我们所付出的努力是值得的。 识别这些区域并不是真正困难的部分，但我正在努力解决如何最好地呈现这些信息。 任何对此的建议，或者如果有人过去做过类似的事情，将不胜感激。
We've just gone through a pretty major system rewrite and I have been asked to find and identify areas of the code that have been improved. as a way to justify to the customer that the effort we've spent was worthwhile. Identifying the areas isn't really the hard part but I'm struggling with how to best present this information. Any suggestions on this, or if anyone ahs done something similar in the past would be appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
实际上，这减少了您的技术债务。全部您通常从这种努力中获得的好处也适用于此。 一些影响将是前瞻性的。 例如：
然而，其中一些将是立竿见影的：
当然，这些好处的应用程度取决于您的项目及其代码库。
In effect, this is a reduction of your technical debt. All of the benefits you would normally receive from that sort of effort will also apply here. Some of the effects will be forward-looking. For example:
Some of them will be immediate, however:
The degree to which these sorts of benefits apply will, of course, be specific to your project and its code base.
这取决于客户：客户有技术头脑吗？ 它们是内部的还是外部的？ 他们想要多少细节？ 您是否被要求重写？如果是的话，由谁以及出于什么原因？
It depends on the customer: is the customer technically-minded? Are they internal or external? How much detail do they want? Were you asked to rewrite, and if so by whom and for what reason?
由于它是针对非技术人员，我建议使用条形图和饼图。 没有什么比彩色大图表更能帮助非技术人员掌握复杂的主题了。
Since it is for non technical people I would suggest Bar and Pie charts. Nothing helps non technical people grasp complex subjects like a big colorful chart.