Why I'm Building Decision Systems Instead of Prediction Systems
Adrian Sterling Blackwell discusses the shift from prediction systems to decision systems in software development. He emphasizes the importance of making decisions explainable, auditable, and repeatable. Current projects include an Event-Driven Decision Logging System aimed at improving decision-making processes in organizations.
- ▪Most software projects focus on producing outputs, while AI projects focus on predictions.
- ▪Organizations operate on decisions that have consequences, risks, and resource consumption.
- ▪Blackwell is exploring concepts like event-driven architectures and decision logging to enhance decision-making.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3936793) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Adrian Sterling Blackwell Posted on May 29 Why I'm Building Decision Systems Instead of Prediction Systems #systemdesign #backend #fintech #softwareengineering Most software projects focus on producing outputs. Most AI projects focus on producing predictions. But real organizations don't operate on outputs or predictions alone. They operate on decisions. A decision has consequences. A decision creates risk. A decision consumes resources.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
