The things that you need to know to be a good programmer

Guide: programming is complex, but many of the factors that make a good programmer are the same as the ones we learned in school at the earliest.
1. Know how to share. use open source as much as possible, and make a contribution to it when you have the ability. Gathering the wisdom of the whole society trumps the myopia of some "big" companies.

2. Fair competition. Try other techniques, frameworks, methodologies, and viewpoints. Do not always think that only your choice is feasible. Other options may be much stronger than yours. Try to test others ' choices with an open mind.

3. Do not attack others. As the 2nd article says, don't attack them just because someone else happens to be using. Net, Java, or PHP (I have a lesson in this). Sometimes, they may be more effective than you think. As long as others are not worthless, you can learn a lot from them.

4. Self-improvement. Try to publish code that can be run. Don't expect QA to find out all the bugs in your program. Always test your code thoroughly and thoroughly.

5. Don't take things that don't belong to you. Use the software to comply with the license, do not steal and then pretend innocent.

6. Apologize for hurting others. Code review is a good but rarely used idea. Instruct programmers less experienced than you to help the whole team. Don't criticize others openly. Coaching is not about belittling others. Others sometimes accept, sometimes do not accept. In fact, sometimes you may learn a lot from the person you think is inferior to your level.

7. Prepare for a rainy day. Try to understand the problem you want to solve before you write the code. Be a prototype, look up an instance from the Internet, talk to someone else who is doing it, or just practice practicing. It's a bad habit to build something you've never done or used before. If you start with ideas, the results may be better.

8. Can afford to put down. Don't be afraid to replace, rewrite, refactor, or discard junk code. Sometimes, it is best to throw away the code if you can leave it. Never fall in love with your code.

9. Cookies and milk are good things. Yes, programmers should have a good working environment. If you want to make programming easier, a good chair, a quiet place, a highly equipped computer and a variety of tools are required. Managers should act as hard as possible to protect programmers and prevent trifles from interfering with them. As a programmer, don't accept a life of slavery. If the boss is bad for you, change a good club.

10. Balanced Life-Learn, think, paint, sing, dance, work, play, everything will be a little. I like the way Google is, where you have 20% of the time to think about anything you think is worth doing. The boss should provide a lounge, recreation room or some relaxing and sober environment.

Programming is a hard job; sometimes your brain does need a break. Refusing to routinely work 80 hours a week otherwise your quality will be greatly compromised, and the amount of time you spend on your work will be wasted. In addition, how to release work life pressure, can refer to Bole online this article: "3 steps to release work and life pressure."

11. Take a nap every afternoon. Working 24 hours a day won't make you more efficient. Rest, go home, and take a nap. Usually, a lot of problems are solved when I go home, and the solution usually comes to me when I'm driving or the next morning.

12. Don't go behind closed doors. Read blogs, learn new languages and frameworks, participate in discussions, and see what peers are doing. You can't be a better programmer if you don't hear the industry in two ears.

13. Keep your curiosity. Think of the seeds in the plastic cup: The roots are long, the foliage is long, no one knows why, but we all do. In general, in the programming and technical world, there are new things that happen every day. See. It's amazing. Study every day, so that you think a wider, skills update, the choice is more extensive. If you think programming is boring, then you should wrap it up.

14. Goldfish, hamsters, mice and small seeds in plastic cups--they all die, and so do we. The code is obsolete and dead. Sometimes what you need to do is bury them and redo them. Don't continue to maintain that awful code to save money.

15. Think of the book: "Male and female Thieves," the first word you learned-"see". If you don't try, you'll never learn anything. Everything I learn in programming comes from trying new things and practicing. Every morning I browse a lot of websites to see what's going on in the world of programming, and I've been doing it since the early 80 when I was at work (though it was a magazine). If you look back five years ago, you will find that programming is actually very simple.