It takes two weeks to watch agner's websites and articles intermittently. The content of program optimization is the most viewed, the most time spent, and the deepest feeling. Other programming ideas should be put down first. Just by the agner's investment in research and willingness to share the research results with others, it will be easy to think about.
During my work over the past two years after graduation, I often vaguely felt that programming is no longer the pride of a single game, the tacit understanding of teamwork, or the loss and happiness after the competition, or a course score. When programming becomes a job, what it brings most is compromise and frustration. What does it mean? The company focuses on clear division of labor and clear responsibilities. Under the rigid rules and regulations, most of them are the snow in front of the door, but less is the tacit understanding. Each person's boundary is different, and each person is a curled-up hedgehog. This makes me miss the enthusiasm and strength of the student age more or less.
I think, college students, teachers, and all kinds of fancy things will be forgotten sooner or later, but you may not remember the feeling at that time, but it is like the mud at the bottom of the river. When it rains, it will pop out of the bottom of the river and float on the water. For example, on the evening of half past six, you sat in the classroom, surrounded by twos and threes. You were very quiet and looked at the books placed under your arm. You can't remember what books you read at the time, but when you don't care, it will break into your heart. This kind of innocence hidden in the bottom of my heart may be the greatest wealth that the university brings to me.
Miscellaneous programming experience