This is a summary of the complement, did not write last week.
Around the fourth again, five weeks the knowledge learned:
the fourth week:
1. the three modifiers
abstract abstract class, an abstract method
static static members, the class loader
final final class, method, constant
2. Interface
What are the similarities and differences between interfaces, interface type, application, specification, constant output interface of the interface, the interface callbacks
3. Internal common classes and class
Inner class, Object class, Object class common method,
fifth week:
1. The internal common classes and class
Packaging, String class, BigDecemal class
2. Collections Framework
The concept collection, Collection architecture, List interface and implementation class, Set interface and implementation class, Map interfaces and implementation classes, generic set of tools.
summary:
1. knowledge learned last week, they are getting hard to part from the interface, although much of what the code level, but many levels of understanding. Have completed the fifth week now, look at the knowledge learned in the fourth week, there will be a deeper level of understanding.
2. The recent small problem: the
School teacher can not keep up the rhythm a bit. I think it might be before I did not learn this new knowledge, we must first listen and understand the effect will be reached with the impossible. We intend to optimize the self-learning system. Adhere to preview.
3. Prepare to each of the little things well, regularly re-set and see where they are not available, the leak filled.
4. Chun teacher in the class say the word remember, "We learn not only programming, we can also be used in programming thinking to life, the things in life is optimized."
In college we learned a lot of computer-related courses, many have mentioned object-oriented, but the teacher is basically a passing, tells us that "high cohesion and low coupling." But how to embody, and there is not much detail. In this lesson, we learn object-oriented chapters, as well as behind the interface, the collections framework. I have felt the presence of "high cohesion, low coupling". A few days ago to see a friend in the microblogging micro-Bo, said a research on agricultural industry consolidation, we found that "high cohesion, low coupling" thinking can also be used on top of research in this area. Allowing more flexibility combined with industry, industrial upgrading more convenient.
Although this "high cohesion, low coupling" the idea may seem simple, but if I were in practical operation code implementation aspects, may also need a longer time to precipitate.
5. Knowledge of the more interesting the more I learn, want to hold this warm, eat this bitter.
