您始终努力实现哪一个软件质量方面？
是性能、可扩展性、可维护性、可用性还是什么？在创建优秀的软件或应用程序时，您始终努力实现的目标是什么？为什么？
我总是更喜欢可维护性。如果它没有优化或者有很好的用户界面也没关系——它必须是可维护的。我相信我们每个人都会有一些非常重要的事情要在这里说。整个想法是收集尽可能多的软件开发改进观点。
Is it performance, scalabilty, maintainability, usability or what ? What is it that you always strive to achieve while creating a good software or application and why ?
I always prefer maintainability above anything. It's ok if its not otimized or has great user interface - it has to be maintainable. I'm sure each one of us would have something very important to say here. Whole idea is to gather as many as perspectives for improvement in software development.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
这里有一个错误的前提：您只想优化一个方面。
您需要取得平衡，即使这意味着没有一个方面得到完美优化。
例如，如果可用性受到严重影响以至于没有人愿意使用您的产品，那么您努力提高可维护性的建议是徒劳的。
（这甚至可以被解释为有点自私，将您的优先事项放在更轻松的生活之上，而不是客户。）
同样，当我看到人们努力从组件中获得尽可能快的性能时，当客户很少时-需要......当它们影响可维护性或错过提高安全性的机会时令人沮丧。
There's a false premise here: that you want to optimize only one single aspect.
You need to strike a balance, even if that means none of the aspects is perfectly optimised.
For example, your suggestion of striving for maintainability is futile if the usability suffers so much that no-one wants to use your product.
(It could even be interpreted as a little bit selfish, putting your priorities for an easier life over those of the customer.)
Similarly, when I see people striving to get the fastest possible performance out of a component, when there is little customer-need for that... frustrating when they are impacting maintainability, or missing the opportunity to improve security.
它必须做客户想要它做的事情。
如果一个软件不能做客户想要的事情，那么它对他们来说就没用。
It has to do what the customer wants it to do
It doesn't matter how fast, how efficient, how maintainable or how testable a piece of software is if it doesn't do what the customer wants then it's no use to them
对于最终用户来说具有良好的可用性，对于可能必须在同一项目上工作的其他开发人员来说，代码具有一定的优雅性。
A good usability for the end user and some elegance in the code for the fellow developers that might have to work on the same project.
可读性。
如果代码可读，就更容易理解！如果需要，在分析代码后，可以稍后进行性能优化之类的事情。
我认为您提到的所有其他“目标”都可以建立在提供可读（因此可以理解）代码库的基础上
Readability.
If code is readable it's easier to understand! Things like performance optimizations can come later if required after profiling your code.
I think all the other 'goals' you mention can be built on providing you have a readable -and therefore understandable - codebase