Three steps to take to solve problems in programming

There is no doubt that engineers who write good programming code are excellent, but while they need the skills to write code in the field of software development, that alone is not enough. In order to solve problems with programming, engineers at software platform LoB explain the process that requires writing code and building a system, as well as the principle of making the world programmable.

Understand, Design, Build: A Framework for Problem-Solving-Lob Blog

Rafael Lee , an engineer at LoB, is introducing LoB's “three steps that will enable you to solve problems in a good shape”. By following this framework, projects are less likely to be regressed and interrupted, and less labor and operation burden, making them more likely to be successful.

Lee states that the first step is to 'understand', and it is important to fully understand what you want as a business outcome and what is blocking the outcome now. Is preaching. In addition to frequent interruptions and interruptions in work to confirm information, it is often the case that completion is not complete and problems are not solved if the prior understanding is not fully understood. There is also a possibility that

The second step is to 'design'. Before actually starting programming, drawing a blueprint for the completion of what kind of approach is possible and the advantages, risks and their mitigation measures of each means enriches the programming technology from pure implementation Lee says it's the key to turning it into a creative job. There are usually several ways to go about the solution, and the first thing you can think of is not always the best. Therefore, it is important to design a plan in advance and to consider means.

Once you understand the problem you are having and design what kind of measures to take, you will actually begin the 'build' phase. While it is tempting to think that this step is the most laborious, Lee said: “If you have already made difficult design decisions, writing code will be the easiest part, and it will be speedy and educational. Yes, it's also fun. '

This three-step framework seems to be useful when teaching introductory engineers, when dealing with problems for which you don't know the solution, and when considering why the project doesn't work. At first glance, it is a process that does not say anything special, but it emphasizes that common understanding and decision-making can be made smooth by sharing the framework with the whole team and keeping it in mind. It has been.

in Note, Posted by log1e_dh