Joel software-15th jolt awards books

Joel software-15th jolt awards books

Author: Zhang guiquan

When I was still pondering code reading -- the open soruce prespective, the 14th-sector jolt award-winning work, the book of the 15th jolt grand prize was expected by the audience. So Joel software has become a hot topic.

The tolt Book Award is comparable to the aoscar award in the film industry. To achieve this, we need to look at the fire of the author. I don't know the specific details, but I think the following parts are indispensable. If you still believe that a good book can affect a generation or an extremely large programmer ). Some factors are closely related to the author's background, but the vast majority are irrelevant. The eyes of the masses are bloody. If you say so. Idea is the soul of a book. If this is none of them, don't count on winning. The quality of a book depends on the author's way of thinking and ability to explain. It is also a key point to solve (interpret) profound problems through short language and vivid stories. Whether or not the readers can be correctly positioned is also an important factor. This will affect the popularity and sales of books. Only when there is a certain impact on the whole of the readers (globally) Can we have the opportunity to nominate. The award is another matter.

Joel on software is called Joel Spolsky. This is an influential book in this award. I am a book enthusiast, and my next goal is it. I have no choice. You can refer to the following introduction for information about books.

"
Book introduction:

You may never expect to become a manager. Like most software developers I know, if you can sit there and write code quietly, you will feel sincerely happy. However, as the best developer, after the unfortunate packaging rope and laptop accident happened to the group's old leader, Nigel, you seem to have become the leading role of the group.

In this way, you now have your own office (instead of sharing a bedroom with the summer wage earners staying in the room all day ), in addition, you must enter the performance evaluation form twice a year (instead of staring at CRT all day long ). That is to say, there is no need to waste time dealing with the strange requirements put forward by the female head programmer, the shoulder-hitting salesman, and the creative "User Interface Designer" (because of Pete, they are hired as graphic designers ). These designers want to highlight the bright "OK/cancel" button with reflected light. I want to know, what is the RGB Value of "reflected light? In addition, the Senior Vice President's empty question should be addressed, and all his knowledge about software comes from travel entertainment magazine articles on Delta flights. "Why should we use ORACLE instead of Java? I heard it looks more unified !"

Welcome to the management world! What have you guessed? Software Project Management and program design are totally irrelevant. If all you have done so far is to write code, you will see that humans are more unpredictable than the wide variety of Intel CPUs like weeds in the garden.

In any case, the old leader Nikel has never been very refined. "I don't want to be the manager who spends all his time on meaningless meetings !" He said in a confident tone. "I think we can still spend 85% of the time writing code, just a little bit of time on management ."

What Nikel really wants to say is: "I don't have any painstaking thoughts on how to manage this project, nor is it as hopeful as I used to write code wholeheartedly. To some extent, everything is automatically generated." Of course, things will not develop so smoothly. It is important to explain why the IBM ThinkPad powers up on that day, and there will be a long way to go.

......

As a result, many software projects fail in such a way, publicly or silently, because no one in the project team knows how a successful software project may work. As a result, too many groups will never be able to deliver their products, or the delivery time may be too long, or no one will be willing to use the delivered products. However, the most irritating part of me is that the project team is not optimistic. I complained about the complaint throughout the day. Life is so short, and there is no time to dislike your work.

A few years ago, I put forward the "Joel test" concept on my website, listing 12 indicators of a well-functioning software project team. For example, you need to maintain a database that tracks fault information and ask job seekers to write code on the spot (don't worry, I will give a more detailed description later ). Surprisingly, so many people emailed me that their project team had only two or three points in 12 tests.

Two or three points!

That's amazing-imagine how a carpenter who has never heard of the screw is trying to make furniture! They rely entirely on nails to work, and they use dance shoes for wooden nails, because no one told them they could use a pair of shoes.

Software project management requires a set of skills and methods that are completely different from coding. They are two completely different and irrelevant fields. The difference between code writing and software project management is much like brain surgery and French bread. There is no reason for a talented brain surgeon to go to a French bread factory due to time and space errors and be proficient in bread, even if he graduated from Harvard Medical School. However, it is inevitable that, without any adjustment, a top-notch coding staff can take management work.

Like the brain surgeon mentioned above, you and Nigel will suddenly feel like they are engaged in a new job, management, and need you and the -- God -- project team, instead of the compiler. If you think that the Java compiler has a lot of faults and is unpredictable, you should wait for the first head-girl programmer to have a problem. Managing a team of people makes the C ++ template seem trivial.

Successful management of software projects requires technology. The art of Management is developing far beyond the conditions of nails and shoes. We already have a cutting head, a screwdriver, and dual-sided saw available. The purpose of writing this book is to introduce some methods to you from all levels, from developing a schedule by the project team owner to proposing a competitive strategy by the software executive director, all of them are covered in the scope of this book.

In this book, you can learn:

How to hire and motivate the best employees-the only and most critical factor in software project success.

How to evaluate and schedule the job, and why.

How to design software functions and write specification documents that are really useful, not just the wrapping paper that is used to maintain the dormitory.

How to avoid falling into the common traps of software development, and why programmers are always wrong when they stick to the idea of "dropping it from scratch.

How to organize and motivate project teams, and why programmers need to close office doors and windows.

Even if you can download a usable software version from the Internet, when do you need to write code from scratch.

Why does software projects seem to be stuck after the first few months of fast running.

What does a good software strategy mean, And why BEOs is destined for a gray ending from the first day.

Other content.

The content in the book seems subjective. I can only do this. For the sake of conciseness, I have removed the phrase "in my opinion" at the beginning of each sentence, because in fact every sentence in the book is my opinion. Although this is incomplete, it may be a good start.

Well, you saw my website ......

Many of the contents of this book were originally published in the form of a series of articles on my website "Joel software" (www. joelonsoftware.com. That is the place that carries my thoughts for years. I hope that the book in your hand will be more "cohesive" than the website. I mean, "You can read it in the bathtub without worrying about electric shock ".

This book consists of three main parts. The first part is all about developing small-scale software: everything should be done by your own team to ensure that the software will not bring harm to people. The second part contains collections on programmer and development group management. Although the third part seems a little casual, it focuses on building a feasible software development business strategy. Here, you will understand why Big products always win the present, why Ben & Jerry companies are different from Amazon, and I will try to point out a situation where a complete set of software development models is usually a manifestation of a lack of competent employees.

Although I have mentioned a lot here, it is better to go deep into books and start reading them. "

Do not miss out on learning opportunities.