outcome-driven coding

noun phrase
UK /ˈaʊt.kʌm ˈdrɪv.ən ˈkəʊ.dɪŋ/
US /ˈaʊt.kʌm ˈdrɪv.ən ˈkoʊ.dɪŋ/

Writing computer code by first thinking about the result you want and then making the code to get it.

With outcome-driven coding, she planned the game's win screen before writing any code.


OTHER MEANINGS

2. A coding style where success is judged by whether the program solves the user's problem, not by how clever the code looks.

The team switched to outcome-driven coding and started asking users what they actually needed.

3. An approach in which developers define clear success measures before starting a project.

Outcome-driven coding helped them agree on what 'done' meant before writing a single line.

4. A teaching method that gives learners a target result to reach, then lets them figure out the code.

The teacher used outcome-driven coding by asking students to make a working calculator first.