SECTION 08 / 14

Build and Fix: an early coding approach

1 min read
On this page 1 headings

Many learners have developed software without strictly following requirements → design → code → test. This exploratory programming style is called Build and Fix: programmers start writing the program immediately after forming an informal understanding of the requirements, and once the program is complete they fix anything that does not match the users' expectations. This is how programming was done in the 1950s and 60s. Good programmers knew principles that helped them write good programs — such as thinking about the big-picture view of the system (the design) before writing the program. Over time these good principles and practices, along with research innovations, were systematically organised into software engineering, which emphasises software development as a well-defined and ordered set of activities.

Build and Fix: begin coding, find problems, patch the code and repeat.
Build and Fix: begin coding, find problems, patch the code and repeat.
Open image ↗
Build and Fix: begin coding, find problems, patch the code and repeat.

Software lifecycle

The software lifecycle is the different stages, phases and activities over which a software evolves from the initial customer request to a fully developed software. These activities are commonly called the software life cycle model, the Software Development Life Cycle (SDLC), or the software development process model.

The software lifecycle and its three common names.
The software lifecycle and its three common names.
Open image ↗
The software lifecycle and its three common names.

REMEMBER Build and Fix → good principles + research innovations → software engineering (SDLC).

YOUR STUDY PROGRESS

Finished this section? Save your progress.

Back to top ↑