每个程序员都应该知道的一些最基本的事情是什么？

2022-03-29 本文已影响0人 Always_July

看了一些高分评论，看完发觉自己在工作没有认真的遵守这些原则，工作中只忙着完成需求，几个版本以后，发现自己的设计和编码都很有问题，年底的时候回想一年也发觉自己的代码没有对业务产生真正的价值。

下面是摘录的一些高分评论

Always know how your business makes money, that determines who gets paid what.
始终了解您的企业如何赚钱，这决定了谁得到什么报酬。
Your success will depend more on your soft-skills and how you articulate the problems and solutions to them, than your technical ability。
你的成功将更多地取决于你的软技能以及你如何表达问题和解决问题的方法，而不是你的技术能力。
You will spend more time thinking than coding.
相比编码，你应该花更多的时间去思考。
If you want to feel important as a software developer, work at a tech company.
如果您想成为一名软件开发人员，请在科技公司工作。
There is no such thing as a 5 minute job. It'll always take at least half a day.
没有5分钟的工作。总是至少需要半天时间。
Project management will always want you to do twice as much in half the time.
项目管理总是希望你在一半的时间内完成两倍的工作。

Love your job, but not your company, you never know when your company might stop loving you
爱你的工作，而不是你的公司，你永远不知道你的公司什么时候会停止爱你

Bad architecture causes more problems than bad code.
坏的架构比坏的代码造成更多的问题。
A bad design will haunt you as soon as the requirement changes even slightly
只要需求稍有变化，糟糕的设计就会困扰您
It is a good idea to discuss your solution with another programmer before starting to implement it, you might learn more
在开始实施之前与其他程序员讨论您的解决方案是个好主意，您可能会了解更多信息

If it’s not tested, it doesn’t work.
如果没有经过测试，它就不起作用。
Code reviews by your peers will make all of you better.
同行的代码审查将使你们所有人变得更好。
A code review is not a criticism.
代码审查不是批评。
Code that’s hard to understand is hard to maintain.
难以理解的代码很难维护。
Code that’s hard to maintain is next to useless.
难以维护的代码几乎是无用的。
The true cost of poorly written code is in the maintenance.
写得不好的代码的真正成本在于维护。
The neater your code layout, the easier it is to read. The easier it is to read, the easier it is to understand and maintain.
你的代码布局越整洁，就越容易阅读。越容易阅读，就越容易理解和维护。
It's not the quantity of code that matters, it's the quality. Any idiot can bang out 40kloc but that doesn't make it fit for purpose.
重要的不是代码的数量，而是质量。任何白痴都可以打出 40kloc，但这并不适合目的。

Learn to read between the lines from the business requirements and try to convert them into technical requirements
始终将代码记录好，它将在将来帮助其他人（包括您自己）
Don’t reinvent the wheel, library code is there to help.
不要重新发明轮子，库代码可以提供帮助。
Fewer features for better code is always the right answer in the end.
减少功能以获得更好的代码始终是最终的正确答案。
there will always be someone somewhere, you’d write a better code
总会有人在某个地方，你要写出更好的代码.
Always test your code, for both, usual cases and edge cases
始终针对通常情况和边缘情况测试您的代码
Just because you wrote it doesn't mean you own it — don't be offended if someone else on your team has to change your code.
仅仅因为您编写了它并不意味着您拥有它——如果您团队中的其他人不得不更改您的代码，请不要生气。