2014-03-29 18:07:20 Today, I'm 33 years old. It's a little big.
I chatted with a friend a few days ago and said that my brain is much slower than when I went to college. My friend was surprised: Do you think it now? I thought so for a few years. Well, I am actually...
I have also discussed this topic with some colleagues:
Some people say: this is because it is now mature and the problem is considered more comprehensive and careful. It is not as reckless as it was before.
Some people say: It's because it's not as passionate as it was before.
It makes sense, but I still like the direct communication method with my friends: Mom, it's just slow!
Slow down what should I do? Compared with some new students, they are young, intelligent, diligent, and code writing is fast. do you compare them with them? I don't think so. At this time, you should never give yourself a wrong position. What you need to do is to put aside your persistence in code when you were young, and never envy the speed and passion of People's code, instead, we need to think about how to cultivate and use it better.
When talking to several senior colleagues in the company, I asked, Do you still write code?
A: Do I write code now? Isn't it disturbing people?
A: I don't want to write code. I am interested in solving the problem. Just write the code and find some young people to write it. I have more important things to do.
So where are your values? I have summarized the following:
1. Project Management
Including progress and priority
2. Software Architecture and business logic design
The code writer needs to know which module is implemented and what it looks like.
At the same time, some code may not be written by you, but you know how it works, because if conditions permit, any line of code goes through your review.
3. Risk management
It is mainly about quality assurance.
And in case of outage, your remedy-this is usually hard to detect, but very important!
4. Customer communication
First, we started to develop our customers.
How to obtain and filter customer feedback and requirements, solve customer problems, and manage expectation when the customer is ready.
There is another value here: the relationship you have established with customers for a long time.
Therefore, your focus should be changed or improved: You are most concerned with "making this project"-choosing the right technology and assigning the right people to do the right thing, their success is your success, and your value is reflected in the final success of the project.
