How can Fish Li help you?

Unconsciously, I have been writing blogs in the blog Park for two years.
After two years of accumulation, the popularity has increased a lot. For this reason, some friends may have asked questions in the past year.
Some of the questions have been asked many times, and some of them have no results.

Fish Li also regrets the lack of results.
Taking advantage of the special day of March 12, I also want to talk about another question: How can I help you with Fish Li?

Next, I will reply to some questions with no results. Although there may still be no answers today, I want to tell you why there is no answer.

How to ask?

Whether it's online or other colleagues around me, I found that some people like to say only two words when giving feedback to an error: An error!

To be honest, you are too unprofessional!

Can you find the cause of the Error Based on the word "error?
Some may send abnormal messages or screenshots, but some of them are vague.
Can you provide more clues?

I believe that you have encountered a program exception, but I don't know what kind of exception you have encountered, especially under what circumstances.
If you refuse to spend more time describing exceptions or provide more clues, no one may be able to help you.
Especially if some exceptions do not occur normally, you need to tell people how to reproduce them.
If exceptions cannot be reproduced by others, how can you help others solve them?

There are also some code problems. I have not encountered any exception when calling the same method, but you have encountered it.
In this case, if the clues you provide make me unable to solve the problem,I suggest you create a new project and copy the code to the new project,
Ensure they can reproduce the problemFinally, send the new project to me for analysis.

So when you ask me a question, I hope you can spend more time to describe the question,
Don't be too lazy to solve the problem.
To be honest: You don't want to spend time or time.

When you encounter some complicated problems, inefficient feedback may lead to several emails going back and forth, and there is no answer at last,
At this time, I will ask the same question: What is your QQ number?

I don't need QQ!

Every time I was asked a QQ number, I don't know if you believe my answer: I don't need QQ!

New eggs make me develop a good habit: no chat tools are needed.
As I am used to it, I still don't need any chat tools, including QQ.

Another reason why I don't need QQ is that I don't have the free time to use QQ.
Fish Li is indeed busy with work, and does not have time to chat with QQ, so I have to use QQ.

Some people like to use QQ communication technology, but I think it is too inefficient to use QQ communication technology?
I don't like typing very much. It's too slow. Therefore, I will not choose this communication method.
If you want to talk to me about technology, you can come to guanggu Software Park to find me.

On the contrary, mail is an offline communication method. I can reply to all kinds of questions when I am idle,
Therefore, you are welcome to contact me via email:Liqifeng0503@163.com

Some may think that QQ interaction is faster than email. If you cannot tell the problem clearly, you can add a description immediately.
If you can clarify the problem at one time, I only need to reply once.

Finally, I want to advise some people who like to chat about QQ during working hours:
When you still haven't finished your work, don't open QQ. Your progress may affect the entire team!

How to Learn

Many people have asked me how you learned it? No good learning method? Can I recommend some books?

Every time I see such questions, I feel very difficult to answer: it is very difficult to give you a satisfactory answer.

I have analyzed these questions. There are two groups:
1. New students who are about to graduate or who are about to graduate soon.
2. Some people who have done Technology for many years but find that their abilities have not improved significantly.

Since they are two different groups, I think the answer should be different.

For newcomers, he may also think that the technical field is too large, and hopes to find someone to give directions.
In fact, I can understand this idea very well. However, have you ever thought: there is no shortcut to learning, and you don't have to invest in it?
Today, you can write a lot of things that you don't understand or haven't seen, but have you ever thought about:
How long does it take me and Fish Li to write these things?

I am not engaged in teaching research and have never thought about the learning method. Therefore, I can only give you some suggestions:
1.Select the technical fields you are interested in.
Since the technology field is too large, you should select a field of your interest. It doesn't matter if you select. net, C ++, and java.
Of course,. net is too big, and you need to continue subdivision and select a part of the. net field.
Do you see the sentence in the upper left corner of my blog page?I was born with no knowledge. If there is a region with no region, the region already exists.
Your life's energy is limited, and there are not only a lot of technical fields, but you are still making continuous progress. It is just a waste of effort. If you really want to write on your resume:
Proficient in. net, proficient in C ++, proficient in java, proficient in JavaScript, proficient in HTML, proficient in CSS, proficient in SQL SERVER, proficient in El, proficient in..., you will surely be exhausted!

2.Have a persistent heart.This is actually a kind of mentality: Don't expect quick success.
At present, it seems that I have not heard of any successful fast-paced things except for quick success.
Many technologies do not only have several commands, functions, or conclusions,
Therefore, your overall skills can be improved only by constantly learning and understanding each technical point.
Therefore, it is doomed that technology learning is a long-term process. In this process, interest and mentality are two key factors that can determine whether you can stick to them.
For this reason, I suggest that you select a technology field that you are interested in first,
In this long phase, interest may always give you motivation. When you encounter difficulties, interest will also inspire you to overcome them.

3.Summary is also important.
New users and Veterans can differentiate them with a chat. Why?
The reason is: from the conversation of veterans, we can feel that they have a lot of technical accumulation.
These technologies come from their summary.
Of course, the form of summarization is diversified: you can write a blog like me and write some technical features into a DEMO or lab,
You can also draw a picture of what you understand.
The form is not an aim. It aims to help you sort out some chaotic or unclear things,
Some omissions can also be exposed during the carding process, which reminds you of what you need to learn.
There are also two advantages: Enhanced memory, which can be referenced in the future.

How Should developers who have been working on technology for many years learn?

Be a Technical Engineer

I often hear people complain: The company's code is too bad! The company's technology is too old to learn anything!

Here, I want to ask you: what are you doing in your spare time? Are you playing games, chatting with QQ, or other things unrelated to technology?

In fact, IT men are still relatively home-based, and most people like to stay at home for leisure, but they don't think of technology.
Therefore, when faced with bad code, they can only complain!
But does complaints work? Of course, you can leave your job, change your job, and face a new code.
However, the situation may be the same.
According to the situations I have seen and my colleagues around me, it is almost certain that the code of software companies in China [mostly] is very bad.
Therefore, even if you change your company, you still have to deal with such bad code. Why is that? I don't want to analyze it here, because it doesn't make sense. We can't change it. This is a reality!

I also want to ask these people: Have you ever thought about how to improve the bad code?
Note: I don't want you to change them all. I know that is unrealistic. I only want to ask if you have thought about it?
If you have never thought about these problems, you cannot make progress!

There are two possible causes for a lot of bad code:
1. Because the Code has many duplicates, It is very laborious to change.
2. The code structure is confused after many coupling, and I don't know where to change it.

If the reason I assume is correct, your problem is:
1. How can I solve a large number of code duplication problems?
2. How to keep the code in a better structure?

Let me tell you the answer:
1. Reflection and delegation can be used to solve code duplication. encapsulation is also a method.
2. The design pattern can solve the problem of code structure confusion. The book refactoring is worth learning.

The complaint "cannot learn new technologies" is estimated to come from many companies that make products or projects that require continuous improvement.
Think about it: Even if you have to redo the project today and use the latest technology, will you complain about it in a few years?
I admit that new technologies or new frameworks can indeed improve development efficiency, but it is not enough to introduce them.
Have you ever thought about improving people's technology? Do you need to improve the code you write?
Or do you pay attention to the quality of your code? For example, security, maintainability, scalability, and performance.

People's technology (CODE) has been improving. Why don't you think about how to improve your code?

Many people not only think about how to improve their code, but also like copying and pasting.
Have you ever wondered why the new framework can reduce the amount of code developed?
That's because people make encapsulation.
What if you often consider encapsulation? Are you creating your own technology?
During your continuous encapsulation process, I am sure you will take the initiative to learn some new technologies, because encapsulation also requires technology.

Therefore, for developers who have been working for many years, don't ask me how to learn or learn anything. Think about your technical pursuit.

If you believe that reading this blog has some benefits, click 【Recommendation] Button.
If you want to discover my new blog more easily, click 【Follow Fish Li].
Because my enthusiasm for writing is inseparable from your support.

Thank you for reading this article. If you are interested in the content of my blog, please continue to follow up on my blog. I am Fish Li.