Confucius said, “If you take from it, you get from it; Take from it, get under it; If you take it, you get nothing.”
For reading knowledge, this old adage teaches us to read good books, preferably the best of the best — classic books!
❝
Good reading makes good friends
❞
“The Way of Programmer Training“
This is a book worth reading again and again.
Since I began to work, I have found that the people around me who read books are like water chestnuts. Many people have lost interest in reading the moment they step out of school. Think reading is useless, but if you ask what is the use of reading? That may indeed be useless! Reading won’t bring you short-term gains or material improvements.
But life is so strange, the more useless things are, the more useful they are.
The world is moving too fast, and the Internet is leading the way! With a small body rushed forward, but do not forget to look back to eliminate a batch of elderly. To stand in this turbulent times, you need to have the courage to ride the wind and waves and indomitable soul. Courage can be tested, but the soul can only be practiced. And reading is a kind of cultivation.
“The Way of Programmer Training” is known as the Bible of Internet practitioners. A book can be so highly appraised in the industry, it shows its value. I can only share the tip of the iceberg here to show my respect!
- Don’t put up with broken Windows
- Don’t leave “broken Windows” (poor design, bad decisions, bad code) unfixed. Fix as many as you find
- Once the window starts to break, it deteriorates fairly quickly and becomes difficult to control
❝
The “broken window theory” : A broken window, left unrepaired for any length of time, gives residents a sense of abandonment — a sense that authorities don’t care about the building. Then another window broke. People started littering, there was graffiti, there was serious structural damage. In a relatively short period of time, the building has been damaged beyond the owner’s willingness to repair, and the sense of abandonment has become a reality!
❞
- Collaborative results – everyone wins in the end
- It’s easier to participate in the successes that are happening, and by giving them a glimpse of the future, they will rally around you
- “A catalyst for change“
- Most software disasters start with little things, and most project delays are day-to-day
- It’s often the little things that add up that destroy morale and the team
- Pay attention to the big picture (boiling the frog) and constantly observe what’s going on around you, not just what you’re doing
- To be successful, all systems must meet the needs of their users
- If you give users something and let them use it early, their feedback will often lead you to a better final solution
- “Invest regularly in your intellectual assets“
- Critically analyze what you read and hear
- “What you say is just as important as how you say it“
- Design self-contained components: independent, with a single, well-defined purpose, and cohesion
- The code remains decoupled
- Avoid writing similar functions
- Get in the habit of constantly criticizing your own code. Look for any opportunities to reorganize to improve its structure and orthogonality. This process is called refactoring
- Orthogonally designed and implemented systems are easier to test because the components of the system are interactive and limited, facilitating testing at the level of a single module
- Unit (module) testing is easier to conduct and operate than integration testing
❝
What is orthogonality?
“Orthogonal” is the concept of linear algebra, is the extension of the intuitive concept of vertical. As an adjective, it only makes sense in a definite inner product space. Two vectors in an inner product space are said to be “orthogonal” if their inner product is 0. — Wikipedia
Then switch to the field of software systems, orthogonality is not dependent on each other, decoupling, that is, each subsystem, module is independent of each other, do not affect each other, or minimize the coupling
❞
- There are always changes to be made, features to be added, and it’s a gradual process
- The limit of language is the limit of one’s world — Wittgenstein
- Estimate! To avoid accidents
- To do a good job, he must sharpen his tools.
- Use an editor. Make it your right-hand man
- Qin people have no time to mourn, and posterity mourn. Posterity of sorrow and not mirror, also complex posterity of sorrow.
- “Fix the problem, not point fingers“
- The easiest person to deceive is yourself
- “Code is for people to see“
- There is no such thing as perfect software. Embrace it, embrace it, celebrate it. Just like there are no perfectly normal people in this world
- Dealing with computers is difficult, but dealing with people is even harder
- Finish what you start
- The only constant in the world is that it is always changing
- Write loose, flexible code to adapt to this era of rapid iteration and change
- Minimize coupling between modules
- Configure, not integrate
- Species that can’t adapt to the real world die out
- Divide and rule. Each module has its own responsibilities
- Coding is not a mechanical translation of design into execution statements.
- Early refactoring, frequent refactoring
- Test your software, or your users will
- Think like a user
❝
Goldie, king of Phrygia, once tied a knot that no one could untie. It is said that whoever can untie this knot will rule all of Asia. Alexander the Great came and split the knot with his sword. Just a slightly different interpretation of the requirements, that’s all… He did go on to rule most of Asia
❞
- Think of the Trojan Horse
- Don’t repeat yourself
- Test your test with sabotage
- A bad pen is better than a good memory
- Write clear and clear notes, convenient for you and me
- When you learn a new language, you can learn all of them