"Road to Jane" reading Feedback
Let me talk first about his past is what to do.
When the teacher learned that the arrangement of their own when the program before they saw the job or code of the program you want to do, first appeared reaction is, well, I want to start programming, read the title to write code to enter this step. Cause a lot of errors in the programming process. We can not carry on unimpeded. Often they think they play an afternoon code, if finally came to feel not written the last will of their own waste an afternoon there is no progress. Always deny their failure, and become dejected. When I have written a program encounters an error, the only problem in the tangled, tangled Why can not run their own satisfactory results, and never escape codes for analysis of the whole. Without the correct method tangled in their failure, they do not know how to stand "outside" observation. In everyday learning is always in their own efforts, there is no choice and we work together, work together. No greater development and progress.
He said the following about the right to face the code of practice Road to Jane as mentioned.
When learning to program code, do not worry be written in the code, first thing to do is to understand the idea of a project, how is this project need to do, how it can be done. Road to Jane the most attention is the idea only when they understand by what steps and methods to solve the problem, this way can make a computer understand what you want to do. Learned during programming regardless of the failure are growing is progress. Those who know say that the achievements in terms of saying little success last fight of the code, they have losers, but they continue to adhere to, to take a defeat in a row after the final victory.
Learning in software engineering is likely to become a developer, as a developer and want to learn computer to communicate. Understand UML source of importance, it is the development of customer demand, leaving history to do the project, like the same history of our country, so easy to check for errors themselves, but also help people understand your code later. Theories are coming from practice, when first learning to master the software development experts concluded these results, rather than search for the origin. Understand the truth, to know the policy work. To understand the project is very simple to understand, the knowledge we think of it too complicated. In addition to congenital mental retardation know the lazy or the day after, all can write the program. Yourself writing program is the first to know to understand how they should do so before they agree to allow computers to understand what you want to do. As a project manager should be committed to reducing the role of communication and team development and other sectors. Should stand between developers sectoral appear to interact. It is to become of people outside ant hole. Such programming should not trap heat in the code can not get away, or turn into an infinite loop, we must learn from the whole issue. Road to Jane, said in a failure of the process is the process , do not make the essence of the process of the project , first of all learn how to do things. In which spoke of " bullshit map " tools, methods and processes is also known as the three elements of software engineering , in which the method is particularly important .
" Process " issue, on both the process of implementation tools, also related to the process approach theory. " Process " issue, on both the process of implementation tools, also related to the process approach theory. When he was involved in a project to clarify their position. The basic dynamic software engineering because an object that implements the method comprising the process tool. Recognizing the JAVA as a platform-neutral language features. Software Engineering = process + method + tool. "Also understand the importance of the team, and how to make good use of the team.
For their proposed requirements, and how to do it.
Their former practices to make themselves become narrower and narrower on the road code, you can not get good results, can not achieve their goals. Own learning in the future to fully understand their own drawbacks, but also understand that they have a lot of things to learn, myself not included in the program are always entangled in the wrong place, to know how to analyze a whole, when work began to engage in the code, one must master the method, you have to understand how we can solve the problem of implementation. This way can make let the computer know what to do in accordance with your thoughts. Remind yourself focus on software engineering tools, methods , processes and achieve the object, or through the efforts of each failure but still did not achieve success, to encourage correct understanding of their own to make their failure. To keep in touch with the team in the daily learning, their learning of energy is limited, and the strength of the team is unlimited. I keep reminding myself into the team. Know how to use the power of the team.