Read "Rework" a year later

The first ebook that was bought in the Kindle was "rework", which was a rare one go to read, like the thrill of finding a bosom friend. A year later, when I once again on the Kindle on the mark to review the time, found that the book is very different from then, do not know whether it is called mature or will eventually become the kind of people they hate.

Forget the "real world."

"This is totally unworkable in the real world. "People always say that when you introduce a new idea to people.

This "real world" sounds so frustrating, as if all the new ideas, new proposals and foreign concepts will always hit the wall in the "real world". Here, the Invincible is the things that people are familiar with, even if these things are already flawed or stale inefficient.

A year ago, this paragraph felt special feeling, then always decided that their ideas are innovative, are subversive, others can not understand my world, it must be others are refusing to innovate, refused to subvert. Now, looking back, I find myself gradually becoming a person who is defending the "real world".

The project in the company is a HTML5 mixed application, no one has done before and I made out, feel this thing is very ahead, very innovative, not only apply the latest technology, but also very cost-saving, the boss is also very acceptable. In the next time, whenever someone put forward the original development of the opinion I have to reject the attitude, on the basis that the cost of native development is too high, and not easy to maintain two versions, for the pursuit of compression costs of the "real world" is simply not feasible. Ultimately, in a recent project, the customer statement demanded native development, and ultimately became one of the reasons our project team lost the opportunity to participate in the project.

I, really became the person who once made me feel like I hated to maintain the "real world".

Of course, HTML5 this form, itself is not wrong, in some scenarios is full of value. My problem is that I have been dying to embrace this program, unwilling to try to change, become overly conservative and lose the opportunity.

Start doing something.

What really makes sense in your life is what you do, not what you think, what you say or what you plan.

The so-called King loser, not only what you do, more important is what you made. The system made it, and the benefits? What about the market? What about the future? Can not see, it is still on the side to cool. Also plan to feedback the open source community, just think about it.

Making a decision is making progress

It doesn't matter how many plans you make, people always make mistakes. Do not mess things up because of excessive analysis and indecision beforehand. Too long a project will discourage morale. The longer the project development time, the less likely it is to succeed. As long as there is enough motivation and morale, it is necessary to strike the troops, make positive decisions, push ahead, and do things now.

I have been opposed to any annual plan. If I could have the foresight for a year, I think I must be immortal. So I am more inclined to the annual goal, the monthly plan. A year, there must be a goal, there is a direction, there is a look forward, the team in this direction, to this goal, is the so-called vision, but also similar to a spiritual sustenance. But to detail to the specific plan, time span should not be too long, one months belong to a more reliable range. You can see that many agile teams have an iterative cycle of about two weeks to one months.

But there are targets and no plans, and indeed the morale of the project team will be hit. We recently made a version of the iteration, developed for one months, tested for one months, online and tossing for half a month. After the toss over, as if they do not know how to go back.

Quality is King

This has nothing to do with product packaging, marketing or price. Here the quality is king.

Determining factors

Amateur photographers are always arguing over the use of film cameras or digital cameras, but no one is concerned about the decisive factor in making stunning photos.

Many amateur golfers are obsessed with joining expensive clubs. But what really matters is how to swing, not which club to join.
I used to see other people casually hanging a SLR, also want to spit groove: Not a SLR can take good pictures. But in fact, as a programmer, I often feel proud to use VIM, and I despise my colleagues in eclipse, and by using VIM, it doesn't mean that I will write better code. What should be the view of such pursuits and pride? The so-called 工欲善其事 its prerequisite, when you are in a professional field (even if you are only an amateur), in fact, you should first choose the best and most suitable tool, in order to help you achieve the best use effect. The quest for tools is also a strong hint of your inner self-improvement in this area of expertise, and the use of tall tools does not immediately make you ascend, but will make you stronger and faster on your way to Ascension.

Now it is often mentioned that a name is called Circle, and the club is a circle. In fact, the circle and the tool is the same, join the circle, not to represent you as the same level as the people in that circle, but by joining the circle to form a positive attitude towards good, and by learning from the good people, ultimately help you on the way to become more determined and faster.

Immediately on the line

When we launch Basecamp software, even the charging function is not finished! Because this product is charged on a monthly basis, we understand that there is a 30-day gap that can be used to complete this function, so we spend valuable time to solve the more urgent, on-line day to solve the problem. and 30 days later only need to use the function, can wait.

The illusion of approval

The business world is littered with useless documents that have no meaning but to waste people's time. No one read the report, no one saw the chart and could not complete the details. These things make a lot of effort, but people can forget about it as soon as they turn back.

If you must explain something, be practical. Don't describe what it looks like, draw it directly, and don't explain how it sounds, just hum it. Do everything possible to get rid of those abstractions.

Be willing to humble

Once you have made your career bigger, you will inevitably have to take a steady course. When you become a legend, you become more conservative and more difficult to take risks. This is the beginning of the rigid, the end of change.

At the moment this company, I was starting from scratch, so at first everyone despised or even ignored me. I remember the first month of work when I saw the manager next door, he was dismissive of my attitude. At that time, although I was weak, but no scruples, seize a chance to become bigger and faster. The change of attitude of others is very obvious. But the wind turbine circulation, the system of users more, cumbersome and worry more, a version of the upgrade out of the bug, in exchange for a pile of complaints; a careless production service failure, more people have been seized to attack you. Then all kinds of reports, various measures, the end result is you dare not do anything, rather than do things, better than do wrong. It's exactly the same as the book says.

General education is not worth mentioning

I never equate my own formal schooling with my educational level-Mark Twain

Everyone has to work.

In a small team, you need people who work, not supervisors. Everyone has to do things, and no one can stand by.

This means that you need to avoid the supervision-type characters in the recruitment, these people like to follow the guidance of others. For small teams, the overseer is a liability. They come up with all kinds of things for others to do, and when they leave their jobs to arrange others, they create more work-whether or not they need to.

In the past I hated supervisors, they didn't code, they commanded me to code. I think a company, such a person in addition to the boss, do not have one more.

As the team grew, and as the position progressed, I gradually realized that if I continued coding, the project would not go any further. We can not always like Google,facebook, recruit the best engineers, the composition of the team is mostly experienced young people, quality is difficult to protect. Some members, the technique is good, but likes to be lazy, arranges one thing to do even, will oneself to see other things, some members, understanding ability not, arranges one thing, does come out with the idea of the entrance too big, is not usable, some members, there is no sense of direction, it is easy not to know what to do, and then start confused ... So, when I've been writing a code for a day, I've found that other people are in bad shape. In a few days, the project has begun to fester. At this time, I had to be a supervisor. I need to track the work of the members every day, ANI; I need to verify that the code submitted by the member is consistent with the original design; I need to remind members to know what needs to be done every day and when to deliver something, and I need to do more, such as version planning, such as architecture design, such as intra-team communication, such as writing various documents. Really, there's no way to write code every day. The more helpless is, I gradually from write not good code, to write code.

Employees more than 13 years old

Let's talk about how much time and money you spend on monitoring your employees. How much does it cost to install the monitoring software? How much time does IT staff waste to monitor employees instead of doing more valuable utility projects? How much time did you waste to write nobody saw the rules? Looking at these costs, you will soon realize that the greatest expense is the distrust of employees.

Read "Rework" a year later