Found via HN, rephrased for future reminder:
- Do not repeat yourself, always refactor/reuse, avoid copy-paste
- Name your variables for what they are for, not its type of data
- Name your methods for what they are going to do
- Don’t use magic number or string literals, use constants or readonly variables
- Strive to make your method testable (unit test, dependency injection, mock object)
- Don’t be afraid to ask for help
- See a bug? Fix it while you’re there, then move on
- Share your knowledge, it will help the point no. 6
- Don’t interrupt colleagues who are ‘in the flow’, related to point no. 6
- Take criticism with open-mind, defensive stance might turn this into religious-wars
Original source: 10 golden rules for becoming a better programmer
GD Star Rating
loading...
Self-Reminder: 10 golden rules for becoming a better programmer, loading...
About Hardono
Howdy! I'm Hardono. I am working as a Software Developer. I am working mostly in Windows, dealing with .NET, conversing in C#. But I know a bit of Linux, mainly because I need to keep this blog operational. I've been working in Logistics/Transport industry for more than 11 years.
Incoming Search
career, team