Urgent.News

What's breaking now, across thousands of outlets.

Tech

A good prediction doesn't always make a good decision

I started building an FPL tool because I kept coming back to one question: what's the point of predicting the best player if signing him isn't actually the best move? It gets complicated pretty quickly. You have a budget, transfer limits, players you already own, upcoming fixtures, and the occasional terrible decision you made three gameweeks ago. So I started building FPL Decision Engine. The…

I started developing an FPL tool because I kept returning to a single question: what is the purpose of predicting the best player if signing them does not ultimately result in the best decision? The complexity soon increased. You have a budget, transfer limits, players you currently possess, upcoming fixtures, and the occasional disastrous decision made several gameweeks prior.

To address this, I began creating the FPL Decision Engine. The objective was to merge football data, AI reasoning, and rule-based checks to evaluate real-world decisions instead of merely ranking players. One aspect that particularly captivated me was distinguishing between what the AI suggests and what the system permits. An AI model may recommend an outstanding player, but if the transfer surpasses the budget or violates the three-players-per-club rule, the suggestion must be rejected.

Confidence alone does not validate an invalid decision. I also began investigating another aspect: what transpires when my judgment diverges from the AI's? Does it genuinely enhance my decisions, or simply heighten my confidence in them? This research is still in progress, and I have not yet determined if the engine improves FPL performance.

There is still much testing to be done. The publicly accessible repository includes a refined version of the code, architecture, and a practical example. While the project began as a football endeavor, it has piqued my interest in decision systems in general. Predictions are valuable. However, determining what to do with them proves to be the more challenging aspect.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

From One Prompt to 39 Finished Products: What Actually Broke

Last March I ran a batch of 40 uploads to Adobe Stock overnight. I woke up to a rejection screen and a bad feeling. The art was fine. The CSV was not.

  • Single prompt generated 39 finished products
  • Metadata mismatch caused initial 40 uploads rejection
  • Scripts automate metadata and upload tracking

The License Layer — Or, Who Can Rewrite the Terms Underneath You?

Twelve essays into this series, the line has never moved: the layer you don't own is the layer that owns you. I've named distribution (#45), the model (#46), identity (#47), access (#48), the harness…

  • License Layer controls software use, modification, distribution
  • Bitwarden switched to dual-license model, sparking debate
  • Nvidia acquisition, Apple removal highlight license control risks

The Silent Alert Bug: When Your Instant Push Exists but Never Fires

Your alert formatter is probably fine. The problem is that nobody calls it. The Symptom A user reports that instant push notifications stopped working. The daily report arrives on schedule.

  • formatinstantalert function built push messages, but never invoked
  • Four code paths for opening positions each contained copy-pasted push logic
  • Dead code persisted due to lack of enforcement mechanism

More from Monday 12 October →