Achievement fisherman
Bears
Taoist fish or people to fish? This is an old topic for IT education. Every educator wants to teach the "fishing of fishing" in the classroom, rather than a sputum small technology; every learner also wants to learn to learn from his own career Play an utility, making yourself not trapped in unexpected and oscillating. Achieve the fisherman, it is an educator and learner common interest. Make
For educational behavior, there is a vectors, from the top of the textbook, we can see the color of the educational thinking. Perhaps too emphasizing that "the people are fishing", and our computer professional textbook has almost no exceptionally the theoretical, ideological, long-term inspection theme, so that their readers are generally far from the needs of enterprises. In order to make up for this shortcomings, many emphasis on the effective training materials should be born, but they tend to come to another extreme - they are handed over to the readers, it is a strip to clean and even the code is good. " Fresh fish. If you have fun, you can also say that they provide "Applicability Education." Can it be destined to be dusty@ury? Do you have to give up the depth of your ideology? Software technology has a rapid development of unprecedented speed, and the huge tension brought about by the new day of the world has made educators feel awkward. The stone of the mountain can attack jade. When we may wish to turn your eyes to the other side of the ocean, maybe I can find some inspiration. In my hand, it is a CONTRIBUTING TO Eclipse in Kent Beck and Eric Gamma. If you look at the title, this is almost a book that is most focused on practical skills - but it is a specific aspect of a specific development tool (Eclipse). But this book has appeared on the number of Jolt Awards with "Technology Oscar". Even with a large number of Java people and two authors are famous, we still have to ask: What makes this "practical" book is so popular? Open the fourth part of this book "Mode Story", a wonderful appearance appears in front of us: Eclipse's huge architecture is scored by two authors, the runtime environment, work area platform, JDT core, UI performance layer ... All design ideas becomes a model to present to the reader. For Eclipse's extension, this hidden value of this treasure map is free; and for a learner for object-oriented thinking, this picture itself is not a priceless treasure? We still remember that Gamma and other three master "design patterns" for us, 23 models allowed readers to open their eyes, and let readers are confused: How to use these modes in actual development? And this CONTRIBUTING TO Eclipse has become a best mode application guide, plus Eclipse is the open source software, the tour map provided by the master, and swim in the Source of Eclipse, the only hinders you master the design model. Thought only has its own patience. This time, how is it "practical"? More intricate is the guidelines for "Rules" - Eclipse developed from time to time, with the most interesting as "Monkey SEE, Monkey DO). From the beginning, the two masters told readers without concealing: they won't pretend what they know, in fact, they can't remember the more detailed details in Eclipse as readers. This law tells the reader: Whenever you have a problem, the first thing you should do is to find a similar problem that has already been resolved, copy the ready-made solution of others, and then modify the change, I have your own problem. Is this a law not a seat of all excellent software developers? The programmer has an old saying: "Excellent code comes from the book, and the genius code is from plagiarism." In not mind, the two masters lifted weight to the reader, happened to be a "fishing of fishing".
Turning back to this book, the two authors talk about a fun little story here: some doctoral students must conduct a defense immediately, the theme is "fruit" (we don't ask this doctor), but he Buy only knowledge about cucumber. However, at least this student has at least the doctor's mind. He successfully pulled each problem to the topic of "cucumber", and played the things that he prepared. The two author modestly claimed that he only had JUnit and models these two "cucumber", so the topic of JUnit and mode from time to time. As a software developer who is often technically technically technically, isn't this a big teachings? - With its fate for Siivus, sleep, why not try all the problems What about your "cucumber"? With a very close to the actual theme, the two masters can write such a very ideological book - we can feel the long-term containers from the title, just a "controling", it is enough to make This book is in "in Action", "from the entry to the proficiency". Perhaps our IT educator - or said that technical writers have learned from this book. While giving your readers affordable "fish", while touches the fishing of fishing in the heart of the inconspicuous corner, the background, this is perhaps the best way to achieve a fisherman.
