Turn: Fire, move-Great God Joel is also impetuous

Http://www.ituring.com.cn/article/18728

Sunday, January 1, January 6, 2002

Sometimes I just can't calm down and work.

Yes, I went into the office, but I was just wandering around. I checked my email every 10 seconds, watched the webpage, and even did nothing to do with my mind. For example, I paid the American Express bill. But I cannot concentrate on writing.Code.

In the face of this fruitless state, my struggle usually lasts for one or two days. However, in my development career, I couldn't write a line of code several times for weeks. As they said, I am not in the status, I am confused, and I am stuck all day.

Everyone has a low mood; some people are relatively shallow, while others may be deep, or even deep, until they cannot take care of themselves. This loss period does seem to be somewhat related to the pessimistic disappointment.

This reminds me of the experts and scholars who said that people basically cannot control what they eat, so the so-called diet can only last for a while, then their weights will return to their natural state. As a software developer, I may not be able to control when I am more efficient. I can only accept low-speed periods that appear during high-speed travel, I hope that the average number of lines of code I have written will satisfy the boss.

What I can't stand is that, on average, I have two or three hours to write some code, which I realized when I was doing my first development job. My summer internship at Microsoft told me that he only worked between and every day. It takes four hours to get rid of lunch, but his team still liked him because he did a lot more than the average. I also found this situation. I feel a bit embarrassed when I see that everyone works so hard, but even if I only have two or three hours of work a day, I can still become one of the most productive members in the team. This may beParts(Peopleware) andAgile programming(XP) insist on Eliminating Overtime and strictly controlling the weekly work time to 40 hours. They are very clear that this will not affect the team's output.

But not those days when I "only" work for two or three hours are bothering me, but those days when I can't do anything.

I think a lot about this. I try to remember the most productive period of my career. Probably at the time of Microsoft, I should have just moved into the magnificent new office, a big glass window, a stone courtyard in full bloom outside the window, picturesque! Everything is so beautiful! For a few months, I almost gave the Excel basic detailed design instruction in one go, but it was a pile of paper as high as a hill, it is filled with incredible details, so I can clearly explain a huge object model and programming environment. When I had to go to the first Macworld conference in Boston, I also brought my laptop and wrote window documents on the nice balcony of Harvard 1.

1 Harvard Business School

Once it enters the status, it is not difficult to maintain it. I often spend my day like this: (1) Working (2) checking emails, reading webpages, and so on. (3) I decided to use lunch (4) for meal return (5) I checked my email, read the webpage, and so on (6) I decided to start working (7) check the email, read the webpage, and so on (8) Again, make up my mind that I must really start working. (9) Open the damn editor, and (10) Keep writing code, I looked up and found that it was already half past seven.

There seems to be a bug between Step 8 and Step 9, because sometimes I cannot get over this. For me, the only difficulty is to start. An object in idle State tends to stay idle. I have some unbearable pressure in my mind, so I can't lift the speed, but once it passes, the status of full speed is almost no effort to keep up. It's like you are waiting for a ride to make a self-help long-distance trip. Before you step down, it's hard to imagine how much effort you have to make them turn, but once you get it done, it feels as easy as anything else.

Maybe this is the key to productivity: Just keep going. The reason for Pair programming is that after you have made an appointment with your friends, you have to urge each other to go.

When I was still serving as an umbrella guard in Israel, a general once came along to explain our strategy. He said there was only one strategy for infantry to fight:Fire and move. Fire while moving towards the enemy. Hold him down with fire, so that he cannot look up, and he cannot open fire on you. (This is what soldiers call "Cover me". "Look at this, open fire at the enemy and hold him down, in this way, when I ran across the street, he could not beat me. "This method works ). Mobile can occupy more territory, be closer to the enemy, and be more likely to hit the target. If you don't move, the enemy will have the right to decide. That's not a good thing. If you don't open fire, the enemy will open fire at you and hold you down.

I still remember this. I have noticed that almost every military strategy, whether it's air combat or large-scale naval performancesFire, moveThe idea has evolved. It took another 15 years for me to realize that,Fire, moveThe principle is to guide us to deal with things in our daily lives. Without a long journey or even a thousand miles. The key is that it must be upgraded every day. It doesn't matter if the code is full of loopholes. It doesn't matter if no one wants the code. If you stick to moving forward, coding, and fixing bugs, the time will bring success to you. Be careful when your competitors open fire on you. Do they want to force you to cope, So that you cannot make progress?

Think about the development history of data access policies developed by Microsoft. ODBC, rdo, Dao, ADO, and oledb are all new tricks! Are these technologies really necessary? Is Data Access Technology re-invented every year because of the incompetence of the design team? (Actually possible ). However, the final result is the formation of fire protection. Competitors have no choice but to transplant and follow-up, which consumes all their time and does not allow them to take the time to implement new features. Take a closer look at the software landscape. Companies that do well have low dependence on big companies, so they don't have to spend all their time following up, implementing and modifying bugs, in addition, the work on Windows XP only works on XP, and the new version of Windows has to go on. Companies struggling to survive online spend too much time reading tea root divination 2 Microsoft's future direction. People began to worry about. NET and decided to rewrite the entire architecture for. Net because they felt they had to do so. Microsoft is shooting at you, and it is only a protection of firepower, so that they can suppress you and run in front of themselves, because the game is playing like this. Are you going to support hailstorm? Soap? RDF? Do you support it because the customer needs it or because someone fires on you, do you feel you have to respond? The sales team of a large company is well versed in the fire shield. They visited the customer and said to the customer, "OK, you don't have to buy from us. Buy from our best agent. But you must ensure that they provide you with Product Support (XML, SOAP, CDE, and J2EE). Otherwise, you will lose the freedom of choice ." When small companies want to sell things to them, all they hear is the confusing CTO's parrot: "Do you have J2EE ?" So small companies have to waste all their time on J2EE. Even if they do this, they cannot bring them a list. They have no chance to make themselves stand out. This is a multi-choice box feature. You do it because you need it to prove that you have it, but no one will use it or need it. It's just the fire protection.

2. a traditional family divination game that uses the shape in which others drink the remaining tea leaves in the cup.

Opening fire and moving has two meanings for small companies like ours. You must let time stand on your side, and you must go up every day. You will win sooner or later. I tried to improve the color scheme of fogbugz a little all day yesterday. Time is worth it. It is always getting better and better. Our software is getting better and better every day, and there are more and more customers. These are the most important. Before our company is as big as Oracle, we don't have to consider any big strategy. What we need to do is to start the editor every morning.

Original article: Fire and Motion
Author: Niu Ren, see the background of Joel Spolsky, founder of Stack Overflow
Who knows Joel Spolsky?

This article is only used for learning and communication purposes and does not represent Turing. Community Opinion. For non-commercial reprinting, please indicate the translator and source, and keep the original chain of this Article