The word is like the face, I am Brother Jun.
Let me ask you a few questions first.
Are you doing 996 every day, but your technical skills still haven’t improved?
Are you working hard but making slow progress?
Have you worked for the same company for three years and feel like you have three years of work experience?
Do you know what you want, but you just don’t dare to take action? Do you take action, but still make the same mistake?
As a veteran of the IT industry for 18 years, today's article will start from the four points of " rapid positive feedback, boundary breakthrough, closed-loop thinking, and systematic approach ".
— 1 —
Fast positive feedback
Generally speaking, after we enter the workplace, we have the following methods to quickly learn new things:
1. Take the initiative to learn in the work environment.
2. Find external excellent people for advice and learning.
3. Read good books, think about them and apply them practically.
4. Fragmented time learning and other methods.
But I think the first thing you need to do to improve quickly is quick feedback.
How to say?
At work, we go from not being good at writing code to becoming architects, from watching others make products to being able to design a product ourselves, and we learn to copy other people's experiences. I think the first point is to be shameless and ask if you don’t understand. If the colleague doesn’t answer or has no patience, I’ll ask another question. We seek feedback from others, and then practice it quickly before asking questions (continue feedback).
For some issues that people around me are not professional in, I will think about finding outstanding people outside the company to learn from. I often read Liu Run’s official account, and when I see articles or opinions that interest me, I will leave a message to express my thoughts. , I will even go to his planet to ask questions and put forward my own opinions, and then I can quickly get his feedback, and in this way I can quickly improve.
In addition, reading has always been a good habit of mine, but there is a bug in reading, that is, no one will give you feedback on whether you understand it correctly. What did I do at this time?
I set up a WeChat reading group with more than 100 people who love reading. I sorted out the content in the book that I didn’t understand well and posted it in the group to see other people’s suggestions and give myself feedback through external input. Of course, there are also situations where friends in the group don’t understand. For example, I was reading Teacher Huang Youcan’s "The Light of Operations" and I asked a question about the details of operations. Almost no one in the circle of friends understood it, so I asked him personally. In order to find out He thought of various ways and finally found him and asked him for advice.
This is my first way to quickly improve myself - quick "positive" feedback, the only martial arts in the world that can't be broken is fast.
This is a single-point breakthrough thinking that quickly improves oneself.
— 2—
push boundaries
Let me make a point first.
In most cases, if you are a developer, you will consider more implementation, more related to stability, that is, think about HOW (how to do it).
You are a tester. What you think about is the impact of the change requirements on the original functions. You won’t create another online bug. Bugs are written by developers. I don’t care whether users are happy or not. Wow! .
If you are an operation and maintenance person, what you think more about is that the hardware and network are normal. I don't care what is running on the machine, as long as there are no important alarms, otherwise I will oncall you developers to death.
If you are a product manager, do you think about whether this demand or product is what users need? What pain points does it solve for users? What are the benefits and disadvantages of adding this new product feature? You think about WHY questions.
Everyone limits their thinking because of their own responsibilities, but if you want to grow quickly, you must break through boundary awareness.
When I am developing, I will ask the product what this function does? What are the prerequisites for this function? If he doesn't think clearly or avoids the topic, there is a high probability that this need is his own.
I also often ask my subordinate product managers (P6 or below), why does this simple requirement development take 2 weeks? You agreed. There are still two weeks of demand. Have you asked what problems the business needs to solve and what business goals it needs to achieve? We have to lower our heads to work, but also have to raise our heads to look at the sky.
The above discussion is about breaking through the boundaries of our responsibilities and connecting one point to another to form a straight line or multiple straight lines.
— 3—
closed loop thinking
Do you often encounter this situation, you ask someone to do a favor, and if he doesn’t reply to you after a few days, just forget it.
Someone comes to ask you about something, but you see it but pretend not to see it, or pretend to answer it, but there is no follow-up.
Or maybe your boss assigned you a task at work, but after a while the boss didn’t ask about it, and you didn’t mention it either.
There is even the matter of borrowing money. You borrow money from others and promise to pay it back when the time comes. When the time comes, you don’t have the money to pay back, but you don’t tell them in advance and wait for them to come to you. In this way, you will basically never be able to borrow from them again. Come in money.
These seem to be small things, but these small things will bring us bad habits, that is, things have a beginning but not an end - that is, there is no "closed-loop thinking" .
Let me give you an example of daily work. For example, we write code and find colleagues to do code reviews. After the review is completed, we will update our code to form a closed loop. It is bound to happen that you make a change once, find a colleague to review it again, and find new problems, but it doesn’t matter and continue to make changes. If things continue like this, it goes without saying that you will soon become a programming master.
On the contrary, when our colleagues gave us some good suggestions, we just agreed with them on the spot and left them alone. If we can't do anything in a closed loop, I believe the results are self-evident.
Let me summarize, I have moved from linear thinking to surface thinking.
— 4 —
Systematic approach
In addition to the above discussion, I think these three points are very important.
Is there a systematic approach?
I provide a model: first find the goal, then find the key issues to achieve this goal, then formulate a plan, execute it, collect data feedback and continue to find new key issues, and so on.
As an example:
I want to complete my goal of reading 4 books in a month. Of course, I read the books that are most meaningful to me at the moment, such as economics and product operations. I bought 4 related books from a certain website in one week. The pace of one book is that after a while, I found that it was quite difficult to read one book a week, and some of the economics books I bought were incomprehensible.
what to do?
I quickly adjusted my plan and used "Fan Deng Reading" to solve the books I couldn't understand. Then I read the paper book again after listening to it. I found that the effect was much better. This is how I found new solutions through a month of feedback, but is it enough?
It was not enough, so I continued to read the book for a month. I found that I only read the book, and the effect was not good.
what to do?
output. I can use it in various scenarios. For example, I output some product articles or opinions on the public account or video account, chat with friends about the application of economic knowledge, etc.
Going back to the "model" I gave above, this is an infinite loop, and it is also what we commonly call "lean " method.
The above systematic method is a systematic method for rapid personal growth - three-dimensional thinking.
Today's article mainly focuses on rapid "positive" feedback, boundary breakthroughs, closed-loop thinking and systematic methods. This is the "point, line, surface, body" thinking model that I have summarized from many years of practice and the rapid growth of technical people .
Finally, readers often ask me backstage why I am growing so fast, whether in the workplace or on my own! Any tips? ! To be honest, there are still secrets and methods in this. I am going to come to the system to share it at 21:15 tomorrow night. It is full of heart-felt information. Please click below to make an appointment. See you there~
-------
Recommended popular articles from the past:
How to manage upward? From a real case!
Why does Byte use GO instead of Java?
For more excitement, follow my official account to learn and grow together
