Finally, a reading of the notes, the contents of each chapter Total about it:
1. dead: talking about the time, we are always very optimistic estimate our arrangements, but our code, does not always give us the opportunity to let us work on time. And exchanges, "a pregnant woman, no matter how many women participate in all the same" project and our people will not be reduced.
Soul 2.Agenda of: talking Kapoor, talking about the drive ideal. What drives us is kept under his hand, I think the hearts of every programmer should have an answer.
3. prototype with Python: to speak the language, how we make choices, how do we find the options, how do we prevent more choices brought us trouble. Another point about the contents of the elevator speech.
4. Lego kingdom, our desire is to be assembled code base, we want the code to be more simple, but, just like me in contact with only one year of white also look out. We can not let the code really like building blocks to easily ride to ride. The modular and component-based software personnel of a dream, but the reality is ruthless. We always want to get the part of the code in, but never no way directly. But at the same time, part of this innovation, it is also our value lies.
5. bundle Geek and dogs: a word, do not do a dog, do not do geek.
Both good, fast, cheaper, and more satisfying it is unlikely to happen.
6. fixed up design: To quote
Do not bigger project. Start small, but do not ever expect it to become larger. If you think so (refer to do large-scale software), it will do over-design, imagine the line is too important. Even worse, you might be intimidated by the hard work of his own imagining. So to start at an early age, efforts to consider the details. Do not think about the big picture and good design. If the project did not address some of the needs, most of that is over-designed.
Do not expect great achievements in a short time, I am committed to Linux for 13 years, I had to take some time to think back. If a long delusion to be a big thing, it might now not hands-on . ----------李纳斯托瓦茨
7. Details view: attention to the needs, attention to detail. Go the opposite way, only let us farther and farther away from our goal, even farther than we do not move.
8. sticky notes on a whiteboard: Agile Development in the mission of this practice is called Kanban. Indecisive, and I think for programmers, is necessary. Many times the lower limit is dependent on a piece of software, we can see how far.
9. The method
These two words gave me great inspiration, IBM is required to plan
1) plan is mandatory
2) plan must conform to the reality ---- "bottom-up", according to those responsible for the programmer to program implementation experience and knowledge from, rather than "from the top down to the" racking our brains or by the manager of the market expectations from.
10 engineers and artists: the artist is not necessarily the engineer, but the engineer must be artists.
11. The road leading to the dog version, others have behaved not impose on others, want users to fall into a pit, we have to jump