Wake up everyone on Monday, maybe you can do more things this week, such as watching one more episode of Twelve Hours...
The story goes like this, I was there with the client from Monday to Saturday last week, every day from 6 am to 11 pm and 12 pm. Isn't it hard work? Do you think I'm working so hard?
wrong! Big mistake! Readers who know me know that I sometimes like to tell you about chicken soup and the truth of hard work, but today I have to change my mind.
Because after such a week, I was not moved by my hard work, but rather worried. There are a few things I will tell you one by one.
0、
The background is that I am now starting a business, working as a data center, responsible for pre-sales, after-sales, solution architecture, technical support, and doing everything except not writing business code. Every day is not in the customer site support, is writing films, documents.
Our product is in the growth stage, and we spend a lot of time working on functions. The development brothers work very hard every day and work overtime every day, and take a lunch break on weekends. But even so, it's still too late to function. So that the quality of the product is not good, various performance problems, bugs.
At the beginning of July, our client's client came to accept it once, but it failed. Let our customers be severely reprimanded, because this is related to some sensitive things I won't say more. In short, the customer was notified by the top because the quality of our products was not up to standard. Therefore, our product line stopped throughout July, and we were responsible for improving the product and fixing bugs.
<br>
1、
Then this past week is for the final assault, to ensure that the second inspection will not go wrong, and it is also our guarantee to customers.
Over the past week, there have been more than a dozen or twenty bugs appearing every day, and some performance and experience problems have been taken out. 20 were repaired on Monday, 20 were tested again on Tuesday, 10 were new, and 10 were old and not repaired.
At this time, a scene that everyone likes to see will happen:
In addition to bugs, many experience problems are even more thought-provoking. The user operation process we envision is ABCD, what about users? AD. What do users think BC is for? So troublesome. Then I'm going to explain why I want BC. But I can explain one or two. Everyone says so, shouldn't it be time to reflect?
So in this kind of problem, we have modified a lot, added a lot of tips, and optimized a lot of process problems.
This is the first place I worry about. We are lucky. We meet a good-tempered customer and dare to use our products with so many problems. But from our own perspective, we can also understand that the team is still growing, and the product is even more so. Many problems do exist objectively.
But this is not the reason, we need to do everything well so that we will have customer word of mouth.
This is a worry.
2、
This time, the client's architecture is relatively large, with a total of 20 machines, 64C + 256GB + SAS 1.5T * 12. This architecture is difficult to encounter, so I want to take this opportunity to make a performance test report.
However, due to insufficient preparation, the test cases were repeatedly modified, which took 2 days. Of course, other things were carried out simultaneously during the period. Then I spent another day debugging the code, because I wanted to collect all the logs as much as possible, including system-level logs, application-level logs, process logs, database logs, and reports on the status of each service, although my final drawing may only be Individual indicators are used, but the collection of these logs will help troubleshoot problems later.
Since the customer site is disconnected and isolated, it can only be tested on the intranet. When the test was carried out on the same day, other leaders of the customer were inspected, and the operation could not be done in the morning.
This series of problems caused me to leave on Friday, so I could only continue on Saturday, and when I wanted to do more later on Friday, because the client was going home, I persuaded me to do it tomorrow... I can't either. Staying there isn't...
At a superficial level, it means that I was not fully prepared, but when I look deeper, it is actually because I personally did not make a plan in time when faced with too many things, but did it directly.
Although the action group is very good, if you have a good plan and then take action, you will get twice the result with half the effort. This is why architecture comes first. Early planning, mid-term adjustment, and final finalization, each step is so important.
This is the second worry.
3、
When I started my business, I told myself, don't do it or ring the bell. I know that I have deficiencies in pre-sales and solutions, so I will make up for it. However, customers have one case after another. Sometimes they have 4-5 cases in hand, and they are doing it at the same time. This is normal. .
This led to less time for study. Until the boss asked me to make a film this week, I still had a lot of work in my hands, so I just hurriedly did it. The next day my boss saw it and came to me. Point out my problem and say it all on point.
I think I am very similar to the boss in some aspects. If there is a problem, I will talk about it, discuss it, and never target people. Even if you and I are very good, I will point out the problem. When others say me, as long as I am right, I can ignore the tone, tone, and situation, because this really helps me.
When I first started working, I met the noble man I have been talking about. He is the kind of person who is very strict. When he taught me to write code, he scolded me every day, "What kind of garbage code did I write?" write", "roll"...too many, but I filter them all...because it's really for my good.
In the workplace now, there are not many people who are willing to spend their rest time every day to teach you real things for free, not to mention no, but there are not many. Besides, they teach me 2 hours a day, and one teaching is 2 months.
So I know where my problems are. These problems will affect the lofty goals I want to achieve. When the company needs me, I can't help. This is a kind of self-blame, helplessness, and guilt.
These are the three worries.
4、
The above three worries are my own analysis, and I share them with you as a reference without reservation. I hope everyone can take this as a warning, and at the same time drinking chicken soup, choose more and see more.
At work, I think attitude is one aspect, but the way of doing things is also very important. This is true of everything. If you can design a course of action in advance and determine a strategic plan, then the next step is to move towards the goal and solve the problem on the way. This is the problem of surgery.
I hope today's content can give you some inspiration.
More interesting and fun content can be found in the public account " Python Column "