Introduction: The current software structure has just commenced week, and I am of knowledge which is still in the preliminary stage of exploration, this blog is mainly about my record changes in perception of the discipline and the software itself before and after the commencement of the course.
Perception of the curriculum
Sophomore year, let's access to the computer system in this course, then you know the next semester there is an equally large classes 5 credits, called software configuration, said Tuesday the two former schoolmates often heard the course is "very difficult nut to crack, "and told to use the java programming language, I thought the main objective of this course must also be on the java programming.
But when I finished the first week of class, my thoughts had changed, and I think this course some differences.
The first week of classes mentioned in a lot of software quality goals, many goals are quality I am very familiar and yet little noticed at the time of programming. A few examples, such as intelligibility: since freshman year I wrote the code has always been what? Think of yourself an algorithm, finished only interested in fast unhappy right, run, as long as the work is not required to write a comment almost never written comments, write your own code after some time it wanted no idea, and this is definitely a very poor habit.
Then I found the back of the course is to set goals around these quality, I think this happened to change the course of the:
before learning course includes the knowledge base, programming basics, let us understand the process, be able to write programs;
then the software structure of this course is to allow us to learn what method - with the guidance of a good knowledge of the method, write a good program. Like the description the same.
Actually, before the course but also to allow us to write a "good" program, but here's the "good" is not the same. Before writing program may be more concerned about how to write out the program, focusing on design ideas, algorithms, program implementation, mainly in terms of accuracy and efficiency;
and this course could work closer to our future: not only focus on efficiency, but also to all aspects of a software concern, consider how to make a software on the market, "live longer", for example in order to safeguard the future of the software, your code might therefore become redundant at the expense of efficiency, but sometimes it yet essential. It's all I had never considered before.
After a week of learning it, my greatest achievement is that these and insights, summed up: design of certain software from various angles to measure it, judge it.
Wang Ling-feng from the side, people often say more perspective Perhaps the answer is not the same problem, in fact, is true of software. I want to now more software as a real person, people are not perfect, there will be some or even many shortcomings, but why some people may be attracted to you alienate some people reckon you want to do? A man wants attractive, design software, is it not so? Various aspects may not achieve the best, but to meet the needs of users, users have a strong attraction for software that is we want to pursue. I hope in the future to participate in the design of software can have a "charm" of it!
These are only for their own personal understanding of this course, please understand if wrong, and I also welcome you to explore!
