5 years of experience in programming 14-blog-Bole Online

<title>5 years of experience in programming 14-blog-Bole Online</title>

Arrange in no particular order:

1. When performance is a problem, if it can be calculated and processed at the application level, then take it out of the database layer. Sorting and grouping is a typical example. Performance improvements at the application level are always much easier than at the database level. It's like being more manageable for mysql,sqlite.

2. For parallel computing, avoid as much as you can. If unavoidable, remember that the greater the capacity, the greater the responsibility. If possible, try to avoid direct manipulation of the thread. operate on a higher level of abstraction as much as possible. For example, in iOS, GCD, distribution, and queue operations are your good friends. The human brain is not designed to analyze those infinite temporary states--This is my painful lesson.

3. Simplify the state as much as possible, localized as much as possible. Apply first.

4. A short, composable approach is your best friend.

5. Code comments are dangerous because they are easy to update or misleading, but this cannot be a justification for not writing annotations. Don't comment on trivial things, but if necessary, in some special places, strategic lengthy annotations are needed. Your memory will betray you, maybe tomorrow morning, maybe after a cup of coffee.

6. If you think a use case scenario might be "no problem," it might be a place where you will suffer a painful failure in the product you publish after one months. Be a skeptic, test, validate.

7. When in doubt, communicate with all relevant people in the team.

8. Do the right thing-you will usually know what this means.

9. Your users are not stupid, they just don't have the patience to understand your shortcuts.

10. If a developer is not scheduled to maintain your system for the long term, keep him on guard. 80% of Blood, sweat, and tears flow in the time after the software is released-you will become a man-weary, but also a smarter "connoisseur".

11. The task list is your good friend.

12. Take the initiative to make your work more enjoyable and sometimes it takes a lot of effort.

13. A silent crash, I will still wake up from a nightmare. Monitoring, logging, alerting. Clear the various false alarms and the inevitable feeling of passivation. Keep your system sensitive to failures and timely alerts.

14. Complexity is a big enemy.

* Side Note: Mr. Rich Hickey's talk and Mr. Robert Martin's " Clean Code" book recently brought a very positive impact on my work.

From for notes (Wiz)

5 years of experience in programming 14-blog-Bole Online