2016-03-02 22:28 by Jackchua
The confusion of "goal"
Sitting for one hours without knowing how to write this blog post. One is that the writing is always holding a conflict, practice very little, do not know how to use good words to describe it, the second is be in the "goal" two words. For "goal", if I say: I want to take the high score of this course, I want to learn knowledge, I want to know software engineering ... No, that's not enough, or for me that is just the basic needs of this course, I believe every student will have this demand, teachers have such needs, but to the "goal", that is not enough. My idea is: if we can build on the basic needs, can use this course of learning for us to bring anything, or want to use this course to learn the knowledge, we want to do something, want to do what. This is supposed to be the goal.
Initial knowledge of software engineering
This course is important, and my own specialty is software engineering. I know it is an engineering approach to managing the entire lifecycle of software, which is self-evident in the development of software and the importance of the industry as a whole. Perhaps I understand this subject is not deep enough, for it, I really still ignorant to poor. But I am still very gratified, our course not only has teacher Li, also has Xin Zou teacher and several other teachers to drive us to study together. Learn the damn (interesting) knowledge of software engineering with interesting learning methods and build up your understanding of software engineering.
Speaking of my confusion and preliminary knowledge of software engineering, it is time to talk about the focus of this blog post----My software engineering course goals. Here's one of my little suggestions, a lot of people will say: "Hey! Please quantify your goals and make specific points. " That's right! But I'd rather say, "Hey! Please make a plan for your goal. " I'm going to give my goal to the course and give a plan for achieving those goals.
Target:
1. Use the scientific method of software engineering, adhere to the team's software projects, and lead our team to the best in the class.
2. Learn to write, and persist in writing blogs, using words to refine and express their thoughts. (Because of the software engineering I know the blog, I saw Xin Zou teacher and link out some very good and very exciting articles, I should also learn, and try to express their ideas)
3. Learn to cooperate and communicate with others.
Plan:
Plan for Goal 1:1. Adhere to the scientific process of software engineering to implement our program. 2. Regularly meet, analyze, communicate and encourage everyone within the team. 3. Regularly feedback team status and project status with teachers.
Plan for Goal 2:1. Stick to browsing and reading other people's blogs. 2. Adhere to the publication of their own blog, whether it is the study, the feeling of life, or the knowledge of the subject, technology exchange. Insist on posting a weekly blog post.
Plan for Goal 3:1. The class answer should be positive and share your thoughts with others. 2. Communicate with the teacher after the weekly course. 3. Listen to other people's opinions and suggestions.
Conclusion:
I have written some of my own ideas, I am not sure whether people can fully understand what I say, but from another point of view I am writing this blog, describing my simple understanding of the course and goals, although some vague. But that's what I think, and that's the truth. Goals and plans are there, and the next step is to practice it. Come on!
Goal? I've got it all set! (The goal of my software engineering course)