Some of the highlights for the chapter:
1. Every good work of software starts by scratching a developer’s personal itch.
2. Good programmers know what to write. Great ones know what to rewrite (and reuse).
3. “Plan to throw one away; you will, anyhow.” (Fred Brooks, The Mythical Man-Month, Chapter 11)
4. If you have the right attitude, interesting problems will find you.
5. When you lose interest in a program, your last duty to it is to hand it off to a competent successor.
6. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.
7. Release early. Release often. And listen to your customers.
8. Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone.
9. Smart data structures and dumb code works a lot better than the other way around.
10. If you treat your beta-testers as if they’re your most valuable resource, they will respond by becoming your most valuable resource.
11. The next best thing to having good ideas is recognizing good ideas from your users. Sometimes the latter is better.
12. Often, the most striking and innovative solutions come from realizing that your concept of the problem was wrong.
13. “Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.”
14. Any tool should be useful in the expected way, but a truly great tool lends itself to uses you never expected.
15. When writing gateway software of any kind, take pains to disturb the data stream as little as possible—and never throw away information unless the recipient forces you to!
16. When your language is nowhere near Turing-complete, syntactic sugar can be your friend.
17. A security system is only as secure as its secret. Beware of pseudo-secrets.
18. To solve an interesting problem, start by finding a problem that is interesting to you.
19: Provided the development coordinator has a communications medium at least as good as the Internet, and knows how to lead without coercion, many heads are inevitably better than one.
As I continue reading the book, I was struck by the insights of the author (as mentioned above) on how his personal experience may taught him all. For my favorite quote is number 18 which explains all about the problem a hacker at some point has to encounter. The career transition for the hackers were not simple enough to be solved instantly. Each problem (actually, the term should also be “challenge” for each of them) should be done in examination of the whole progam. Furthermore, the efforts of the hackers were not always a win for them at the battlefield, in fact failures are much prone for them to happen considering for their first try to implement the project. As for my experience as a student, I must say that yes indeed that I am up for the challenges to become one of the contributors in the IT industry someday. Hacking is an interesting topic for me that is why its learning curves and problems that may come my way so to speak, are as well a good thing for me to learn.
Finally to sum it all up, I beleive in the statement that: experience is the best teacher of all time, because first hand experiences are much fulfilling to happen compared with any other experiences as one should have to encounter.