Programmer self-cultivation

Recently read “programmer self-cultivation” this book, which programmers need to master the content of a comprehensive description of the content, is worth a look. Whether it’s front end, back end, app, you have to be a programmer first, then a specific role. Some of the content of the computer is a lot of general, only to master these general, invariable knowledge. To be able to handle the things that “change”!

Basic knowledge of

  • Semantic version
  • Naming conventions
  • Written document
  • Regular expression
  • The road to ordinary

Computer is a huge system, covering a lot of knowledge, we do not need to worry, straighten out the mentality, find their own way, straighten out the mentality, technology is to be polished. The more expert you are, the more calm and calm you will feel when dealing with them. They can analyze problems step by step like a teacher. To be able to face with thunder in your chest)

Data structures and algorithms

Don’t explain

Design patterns

In my case, in most cases, business code is fast and simple to write. Before writing code, we should pay more attention to the design of the code, the logic of the code, how to make your code coupling, extensibility, robustness, whether there is duplicate code, whether the logic is clear and so on. Actually writing code is a process of translation. Translating requirements into code is the same as translating a foreign language into Chinese. But the translation must be clear before the design scheme. If you translate something that others can’t understand then why do you have to translate it?

Code review

  1. How to quantify code

    Business people are focused on quantifying what they want to know from you about what you do and what value you bring, not how much you do. Professors can easily quantify their work, and sales people can calculate their revenues. Other fields can also count their contributions in several ways. But for people in software development and technology, quantifying work can be difficult. Quantifying this is not a job search, but a part of being a technician. Evaluate your performance, communicate effectively, and work effectively with non-technical people to ensure your value to the team or organization. What are the problems that technologists need to solve when looking at situations, actions, and results to describe work outcomes? What actions can be taken to solve and improve the problem?” What happens in the real world? You try to ask yourself some key questions: do you monitor and test when updating your code… That’s the goal of quantification. If you finish an app six weeks in advance of your schedule, you’ll want to brag about it. But have you thought about your company’s strategic goals? If not, please. . If you feel something different, it’s not just you. If the technical people had done the quantitative part, they might have gone into sales.

  2. A list of Code Review requirements for programmers

Regular item

  • Does the code work? Does it achieve the desired function, is the logic correct, etc.
  • Is all the code simple to understand?
  • Does the code conform to the programming specifications you follow? This usually includes brace positions, variable and function names, line lengths, indentation, formatting, and comments.
  • Is there redundant or duplicate code?
  • Is the code as modular as possible?
  • Are there global variables that can be replaced?
  • Is there any code commented out?
  • Is the loop set to length and correct termination conditions?
  • Is there any code that can be replaced by library functions?
  • Are there logs or debug code that can be deleted?

security

  • Are all data inputs checked (for correct type, length, format, and range) and encoded?
  • Where are third-party tools used, and are errors returned caught?
  • Are the output values checked and encoded?
  • Can invalid parameter values be handled?

The document

  • Are there comments that describe the intent of the code?
  • Are all functions commented?
  • Is there a description of unconventional behavior and boundary case handling?
  • Is the use of third party libraries and functions documented?
  • Are data structures and units of measurement explained?
  • Is there unfinished code? If so, should it be removed, or marked with appropriate markers such as’ TODO ‘?

test

  • Is the code testable? For example, don’t add too many or hidden dependencies, don’t initialize objects, test frameworks can use methods, and so on.
  • Are there tests and can they be understood? For example, get at least code coverage that you’re happy with.
  • Do unit tests really test whether the code does what it’s supposed to do?
  • Are arrays checked for “out of bounds” errors?
  • Is there any test code that can be replaced by an existing API?

Qualified PM

When writing code, you should think about why you need to do it, what the results are, and what you can bring to the user!

  • Define the product clearly
  • Establish good communication channels
  • Don’t tell the engineering team how to do it, tell them what to do
  • Believe in the engineering profession

The most troublesome product managers are those who know nothing about technology and have great ideas about it — hackers and painters

Pay attention to health

  • sleep
  • Exercise (The most important thing for most people is not prioritizing fitness, but getting started and sticking with it)

Everyone’s IQ is limited, some people are gifted, some people are ordinary. But we do not focus on here, although talent can not change but we have to let their mind always maintain the best thinking state, a healthy body can help us to do this.

The efficiency of

  • Learn to read
  • Learn to ask questions
  • Make good use of search (write a separate article later to collect information)
  • How to write
  • Time management

Hacker

How to Protect Privacy

work

Why you quit

Start by thinking about why you’re stuck in your current growth environment. Look for your own internal causes instead of complaining. Can not face up to their own shortcomings, sooner or later will be due to their own lack of ability and leave. Don’t talk to HR about your last company’s complaints, because the next company you interview with could be your last company.

The real reasons for leaving are:

  • Family: after buying a house and getting married, family expenses increase and personal pressure increases

  • Personal ability to grow below the industry average, often referred to as the ceiling.

  • And the lack of change and vitality of the company and team compared with the industry.

  • After two years in the same job, a person becomes competent and enters his or her comfort zone. At this point, it is common to move on or get a promotion to take on bigger challenges.

  • Value: A stop loss is a job change that does not provide value in the current environment for a period of time.

  • Salary: not explained.

Now of I

I think it’s important to know who you are when looking for a job. Otherwise too much thought their ability, often bring their own frustration.

As the saying goes, “Knowing yourself and knowing your enemy is the best way to win a hundred battles.” We not only need to understand ourselves, but also need to understand the external market. For example, we need to ask friends in other companies about the treatment of people with approximate working years and levels, which is also a way to price ourselves.

Going out to find a job also means that you have to give up the current working conditions and contacts, to grow in a new environment, our mentality is also very important. Being polite will pay dividends in the future.

What to pursue and how to plan

  • In the spare time, don’t forget to pursue their own technology, understand more and write some code
  • There is no IT company that does not work overtime. IT depends on whether you think this kind of overtime is worth IT

Quitting is not the way to solve the problem, what we should really do is to cultivate their general quality, excellent technology, every company has different points, with the same knowledge should be changed.

thinking

Front end, back end -> Programmer -> character (son, parent) -> human -> animal

Every day we are a process of life’s cultivation, exploring ourselves is also a kind of ability. We are not just a programmer, we are a normal person, we have more skills, interests. Improve yourself in life. What can you do one day when you are no longer in the business? Take a good attitude and feel life.

About writing

This is the first article. I don’t know how long I can do this, but like fitness, the most important thing is not to prioritize how well you do it, but to start doing it and stick to it.

Reference: www.kancloud.cn/kancloud/a-…