Boulevard to Jane: the idea of software engineering practitioners--sixth chapter impressions from programming to engineering

From programming to engineering

1. Language is just a tool

Language for an it -related industry programmer, technical staff, language is just a tool, in the it - related industry , to see clearly the big program is the beginning of all this is derived from the " Language is just a tool! " Ape to Human, "learn how to make and use tools" is the most important sign, so engaged in IT - related industries We are also known as the program Ape, of course, there is more pronunciation is a bit similar .  Therefore, I do not know that "language is only a tool" this sentence, whether the worship of language, or disregard. But from that moment on, I really knew about the project. What we've learned about eating,#c ++\ , and what we've learned about Java, maybe some people say it's a few technical courses, and it's not as if it's called a few languages, and after reading some time, we find these courses are just a few languages, These languages are the language we talk to the computer, so we have to learn these languages, on this understanding we need to learn Putonghua in the way to learn computer language, how we can learn professional knowledge. We can no longer focus on language, as the scholar wrote in the first chapter: it is good to talk about the language all day, or the language is bad, even sad.

2. Procedure

In the inner ring, it is "program = algorithm + Structure". This is the source definition of programming, and it is also the original state. Any work related to the code will eventually end up with such a rule, so the reason we learn this path to Jane is the whole, as all the English words are made up of the letters, so all the programs are made up of a simple "program = algorithm + Structure" So we have to be patient to see the program, to read the program.

1. Method

The development of the process forward is the emergence of "method" and "methodology". Long-term programming practice, natural return and summary, must be precipitated into some kind ( Software Development ) method, so "process" appeared, so "object" appeared, so the related methodology also appeared. You do not see the act of doing things, and you cannot understand the value of "patterns" as a method. So the gurus unanimous: patterns need some programming experience to understand. Understanding the process also requires programming experience, understanding the object also requires programming experience, so to master the method or need programming experience, this is what we often put on the lips of "practice makes perfect". So learn the code to do more hands-on.

4. Process

Boulevard to Jane: the idea of software engineering practitioners--sixth chapter impressions from programming to engineering