Read "Road to Jane - software engineering practitioners thought" felt

"Road to Jane" book length is shorter, over one hundred pages, not the kind of programming as a large book reads very cumbersome. Overall, it is rather easy to understand, explain their point of view at the same time cites many examples of ancient and clarifies the author of the book detailed view of software engineering as well as some insights, the book also has a lot of jargon I do not see to understand, but the idea that I can learn, especially as my students this school of software engineering is worth learning. Road to Jane probably is the big deal is actually a very simple truth, a very simple truth, he is very simple, so simple that one or two words can be said clearly.

This book is a total of eight chapters, each chapter tells a truth of an idea, first Foolish Old Man, this fable written by a fundamental programming sequence, branching, looping, also wrote the book in addition to congenital and acquired mental retardation lazy people can learn why we will not learn, not to mention we are to learn software engineering, should redouble our efforts, and certainly not just blindly hard on the line, like a foolish old man diligent room every day but did not think, this does not work, just like the book very busy boring Bing, he came up with a way to "burn the accumulated salary", with the only time to think, will have a good idea, so we, too, need to think about after then act. It created a lazy method, a new method of software engineering should be on the road to keep in mind-set is, the use of fixed type, forget-set, create-set, we need to continue to explore and create their own methods!

Unconsciously freshman has ended, for a year of programming, however, during the year, every time I encountered programming problems, has always been a problem began to read made up, never seriously thought, often writing written with no idea of ​​the efficiency is very low, sometimes even a simple programming problems take a long time, after reading this book I also found his big flaw in this, we must first ponder this question at large frame, then started to move not too late.

Failure of the process is the process, which describes the waterfall model and some of its deformation, said: do not do the engineering process is not the purpose of the essence, but also get theatrical program and project comparison, going through the motions put forward words like, tells purpose programming --achieve. Achieve, is the goal. Just a way to project implementation, but also to those of us novice engineering students a warning: engineering and engineering who are lost in the project. Those of us who learn software engineering, should know that.

There are many books about teamwork, language tools, communicate with customers, as well as insights and ideas of thinking, people are able to learn a lot of things. But read the book, I feel most of the wisdom or lazy, endless repeats often, although there are mountains and flat, but the time spent can be imagined, only hard on the body is not enough to be busy while working to stop and think, choose better solution to the problem, look for a closer way. Road to SR, any heavy work, just to explore, will find the optimal solution.

 

Guess you like

Origin www.cnblogs.com/022414ls/p/11220897.html