Results-Oriented Programming

📰 Dev.to · JaviMaligno

Learn about results-oriented programming and how it shifts the focus from verifying code implementation to verifying its output and results

intermediate Published 24 Jun 2026
Action Steps
  1. Understand the concept of results-oriented programming and its difference from traditional programming approaches
  2. Apply results-oriented programming to your current project by focusing on verifying the output and results of your code
  3. Use testing frameworks and tools to validate the results of your code
  4. Collaborate with your team to implement results-oriented programming and ensure everyone is on the same page
  5. Refactor your code to prioritize results over implementation details
Who Needs to Know This

Software engineers and developers can benefit from this approach as it changes the way they test and validate their code, focusing on the outcome rather than the process

Key Insight

💡 Results-oriented programming is about verifying the output and results of your code, rather than its implementation details

Share This
💡 Results-Oriented Programming: Focus on verifying WHAT your code produces, not HOW it's implemented #softwareengineering #testing

Key Takeaways

Learn about results-oriented programming and how it shifts the focus from verifying code implementation to verifying its output and results

Full Article

Title: Results-Oriented Programming

URL Source: https://dev.to/javieraguilarai/results-oriented-programming-2n35

Published Time: 2026-06-24T16:47:14Z

Markdown Content:
[Skip to content](https://dev.to/javieraguilarai/results-oriented-programming-2n35#main-content)

[![Image 1: DEV Community](https://media2.dev.to/dynamic/image/quality=100/https://dev-to-uploads.s3.amazonaws.com/uploads/logos/resized_logo_UQww2soKuUsjaOGNB38o.png)](https://dev.to/)

[Powered by Algolia](https://www.algolia.com/developers/?utm_source=devto&utm_medium=referral)

[Log in](https://dev.to/enter?signup_subforem=1)[Create account](https://dev.to/enter?signup_subforem=1&state=new-user)

## DEV Community

![Image 2](https://assets.dev.to/assets/heart-plus-active-9ea3b22f2bc311281db911d416166c5f430636e76b15cd5df6b3b841d830eefa.svg)0 Add reaction

![Image 3](https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg)0 Like ![Image 4](https://assets.dev.to/assets/multi-unicorn-b44d6f8c23cdd00964192bedc38af3e82463978aa611b4365bd33a0f1f4f3e97.svg)0 Unicorn ![Image 5](https://assets.dev.to/assets/exploding-head-daceb38d627e6ae9b730f36a1e390fca556a4289d5a41abb2c35068ad3e2c4b5.svg)0 Exploding Head ![Image 6](https://assets.dev.to/assets/raised-hands-74b2099fd66a39f2d7eed9305ee0f4553df0eb7b4f11b01b6b1b499973048fe5.svg)0 Raised Hands ![Image 7](https://assets.dev.to/assets/fire-f60e7a582391810302117f987b22a8ef04a2fe0df7e3258a5f49332df1cec71e.svg)0 Fire

0 Jump to Comments 0 Save Boost

Copy link

Copied to Clipboard

[Share to X](https://twitter.com/intent/tweet?text=%22Results-Oriented%20Programming%22%20by%20JaviMaligno%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fjavieraguilarai%2Fresults-oriented-programming-2n35)[Share to LinkedIn](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fjavieraguilarai%2Fresults-oriented-programming-2n35&title=Results-Oriented%20Programming&summary=Reviewing%20used%20to%20mean%20reading%20the%20implementation.%20Increasingly%20I%20verify%20what%20the%20model%20produced%2C%20not%20the%20path%20it%20took%20%E2%80%94%20and%20what%20%27verify%20the%20result%27%20means%20changes%20wildly%20depending%20on%20whether%20the%20result%20is%20a%20number%20or%20a%20behavior.&source=DEV%20Community)[Share to Facebook](https://www.facebook.com/sharer.php?u=https%3A%2F%2Fdev.to%2Fjavieraguilarai%2Fresults-oriented-programming-2n35)[Share to Mastodon](https://s2f.kytta.dev/?text=https%3A%2F%2Fdev.to%2Fjavieraguilarai%2Fresults-oriented-programming-2n35)

[Share Post via...](https://dev.to/javieraguilarai/results-oriented-programming-2n35#)[Report Abuse](https://dev.to/report-abuse)

[![Image 8: Cover image for Results-Oriented Programming](https://media2.dev.to/dynamic/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fwww.javieraguilar.ai%2Fblog%2Fresults-oriented-programming.png)](https://media2.dev.to/dynamic/image/width=1000,height=420,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fwww.javieraguilar.ai%2Fblog%2Fresults-oriented-programming.png)

[![Image 9: JaviMaligno](https://media2.dev.to/dynamic/image/width=50,height=50,fit=cover,gravity=auto,format=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3701121%2F3d85b744-a4d6-4104-a1ae-db83b08dcc88.png)](https://dev.to/javieraguilarai)

[JaviMaligno](https://dev.to/javieraguilarai)
Posted on Jun 24 • Originally published at [javieraguilar.ai](https://www.javieraguilar.ai/en/blog/results-oriented-programming)

# Results-Oriented Programming

[#ai](https://dev.to/t/ai)[#software](https://dev.to/t/software)[#engineering](https://dev.to/t/engineering)[#testing](https://dev.to/t/testing)

There's a line I dropped almost in passing in [a recent piece](https://www.javieraguilar.ai/en/blog/how-much-should-you-still-know), and it's been nagging at me ever since: programming keeps drifting from verifying _how_ the code works to verifying _what_ it p
Read full article → ← Back to Reads