There is a very popular project on Github, 996. Icu, which was published in less than an hour, has 9W +star as of 14:33:02 on March 29, 2019. My colleagues and I often joke about this, but the joke is the joke, my true thoughts, I want to write here.
The present situation of the I
My current company 966 rigid rules, I think it is ok, the workload is not very big, the welfare is also good, especially food and accommodation package, solve a lot of trouble, the leadership is nice. Most of the time, as long as I get my part done, I don’t care.
What do you think of 996?
There are two cases
Firm rules
First of all, the reason why the company is doing this is understandable if you’re in the early stages; Second, look at the treatment, time salary do not use monthly salary, do not believe options and other pie, every month to get the money is the most real (if as a partner, you consider.) . If both are ok, you can decide whether to join or not. If I have more time and energy or want to exercise myself, I will probably go.
Otherwise everything else is bullshit, usually companies are not 996, companies that want 996 for no reason whatsoever are garbage, companies that want 996 and don’t give money are garbage + disgusting.
The company has no hard and fast rules
Well, all I can say is, dude, you have a big problem, and you need to think about whether you’re being a little inefficient, or you’re taking on too many tasks. In most cases, your ability is tied to your salary, and you have to think about what the problem is.
Task too much
Every development task has time evaluation, if you think the time is wrong, you should bring it up, and when you find the problem when you do it, you have to take the blame, work overtime, because you don’t have the concept of time, learn from a fall into a pit, learn how to estimate time next time.
Low efficiency
You’re not one of those programmers who codes for five minutes and chats for two hours. If you don’t work overtime, who will? How to become a master of Effective Learning? Is explained in detail. If I don’t have time to read the whole project, I’ll write about how I made sure I didn’t work overtime and get the work done.
How to ensure that the task is completed and not 996?
In two words, efficiency, of course, can also be classified as ability. But it’s too broad a statement to know how to implement. So I say my specific practice, only for your reference. I plan to write an article on how to work effectively as a team in the later stage. Blog, I believe it is also very helpful to you.
The mission
When estimating the time, the need to use the technology, framework and so on in the mind has a spectrum. Estimate, not the first time to bury your head in writing code, but to estimate when those things are generally implemented, think about every detail point, library table design, and then from the deep to shallow plan. Such as when the framework is built and when the library tables are designed. If the demand is too large, it can be divided into several phases and the function points of each phase are formulated.
The end of the day is the deadline
What does that mean? Just don’t think that you can’t finish working overtime now, once you have this idea, your efficiency is about 0. Focus on your work while you’re at the office. Zero chatter, zero distractions. Don’t create the compulsion to leave on time.
Personal thoughts and suggestions
If you’ve been in 996, it’s most likely your fault. Don’t laugh and complain all day long. Take a good look at yourself, find more reasons in yourself, so as to improve.
I look down on companies that are 996 for no reason, as well as programmers who are always 996. The former is corporate garbage, and the latter is ability garbage. As the elder brother said, “I’m not targeting any one, I’m talking about the above, they are all garbage.”
But if you’re new out there and you don’t know anything, I suggest you work overtime. But is not always engaged in work, your focus is not even salary, but learning, the ability to focus on the promotion, really very very important, the iron needs their own hard; On the other hand, working overtime can make a good impression on your boss, at least to show that you are a hard worker.
When I first arrived at Qunar.com, I didn’t know anything about the company’s technology. So in the early days, there are almost no days before 10 o ‘clock, even on the weekend are in the company. But notice, I don’t do work all the time. In my off hours, I learn about company components, company processes, etc. Until now, I think that period of time was the time when I improved my skills the most. I have to thank my two leaders — Yang Shenjia and Li Wenfang. This kind of opportunity is rare.
conclusion
To sum up, 996 is often the programmer’s own problem.
When I said something like this before, there was a lot of confusion as to what I meant by this: it’s all programmer’s fault. So I wrote these extra tables to show my attitude.
Strength, or strength, try to improve themselves, study hard. What’s the use of complaining? You think the treatment is not good, the system is disgusting, the product is rubbish, it is better to hold back this tone, spell once, to oneself hard point, learn the technology home, and then job-hopping. It’s better than complaining and standing still.
I’m not going to make you feel good, I’m going to make you feel bad, but I hope you can change something.
Welcome to follow the wechat public account, to provide ideas and technical original articles. Search for Xiaobing Zhang Jian on wechat or scan the qr code below.
