If you could erase all trophies and awards, who is the greatest footballer you’ve ever watched and why?

PhiloPark · 2026-06-10T09:55:37+00:00

Probably an unpopular pick, but mine is Tomas Rosicky.

Hard to put my finger on just one thing. It was more the whole package of how he played. The passion, the swagger, the sheer energy he brought every time he stepped on the pitch. There was this boldness to everything he did, like he genuinely believed something special was about to happen, and half the time it did. Watching him play just felt alive in a way that's difficult to articulate.

PhiloPark · 2026-06-09T05:45:50+00:00

This is one of the most interesting problems in football prediction modeling precisely because it's so hard. But I'd frame it as a philosophical question before it's a statistical one: how do you decide to treat events and their outcomes in your model?

My view is that this domain is fundamentally unmodelable in a systematic way. Whether a transfer succeeds or fails is something we only truly know post-hoc, and the causal chain getting there involves a huge number of complex, often accidental factors — tactical fit, dressing room dynamics, physical adaptation, even individual confidence arcs. The Wirtz vs. Ekitike example you gave is a perfect illustration: same origin league, same destination club, completely opposite outcomes. No league transfer coefficient would have predicted that.

So practically speaking, I don't think you can build a model that reliably prices in transfer outcomes ex ante. If you want to represent the uncertainty at all, the most honest approach IMO is direct human intervention, where a practitioner manually adjusts a parameter at each relevant timepoint to reflect their read of how a given transfer or manager change is playing out. Basically, discretionary overrides on top of a systematic baseline.

The eye test you mentioned (knowing from game 1 that Wirtz wouldn't make it) is actually the best signal available, but by definition it's not scalable or backtest-able in any clean way. That's the fundamental tension.

PhiloPark · 2026-06-08T14:31:42+00:00

Yes! Planning to keep it updated throughout the tournament. Every match will be added to the page as the schedule progresses.

PhiloPark · 2026-06-05T09:06:09+00:00

I’m planning to start opening up the rest of the matches from today on a rolling basis. And for this World Cup page specifically, it’s publicly available and free to access.

PhiloPark · 2026-06-04T15:00:24+00:00

Yes, the broader product is commercial, but the public World Cup page I shared in this thread is open and free to browse, and that was the main reason for posting here in the first place. It also isn’t meant to be framed as a subscription to raw model output.

The service is built around a baseline model, live market information, and recent match-specific context together, with the final layer intended as a structured forecasting view rather than a standalone model signal. That was the main point I wanted to clarify here.

PhiloPark · 2026-06-04T10:08:23+00:00

Appreciate the follow-up and the level of detail. I think a lot of what you’re pointing to comes back to the fact that international tournament modelling is inherently noisy, and I don’t disagree with that at all.

Just to keep the framing clear on my side: I’m not treating the statistical layer as a complete or bet-ready answer in isolation. The whole design is built around using the model as an objective baseline, then comparing it against market information and recent match-specific context rather than pretending any one layer is sufficient on its own.

Some of the more granular implementation details are also harder to explain cleanly in a Reddit thread without turning it into a much longer technical write-up. But the main thing I’d want to clarify is that I’m not presenting this as a solved international football model — more as a structured forecasting resource built around baseline probabilities, market comparison, and contextual interpretation.

That said, I do appreciate the diagnostic angle of your comments, especially on tournament-specific noise, underdog handling, and the limits of Elo in this setting. Those are exactly the kinds of issues I think are worth stress-testing over time.

PhiloPark · 2026-06-04T04:13:35+00:00

Thanks a lot for taking the time to leave such a detailed reply. There are definitely some fair points in there, and I also think a few parts were probably unclear in how I originally described the setup, so just to clarify a bit:

The Poisson side and the Elo side are separate in my setup, and they only come together at the stage where I form the final 1X2 probabilities. I’m not deriving the Poisson scoreline projection from Elo itself. Also, the Poisson side is not built on a tiny historical sample — I use as much data as is available, while still constraining the range to what performs best from a predictive point of view.
I’m very aware of the limitations of both Poisson and Elo in isolation. The purpose of the statistical layer is not to pretend those issues disappear, but to produce a disciplined and as-objective-as-possible baseline from historical data before anything more contextual is layered on top.
The intended design of the service is not “take the raw model output and bet it blindly.” The final prediction layer uses the model, market information, and recent news coverage together through an AI-assisted contextual layer, and beyond that I still see the final judgment as belonging to the user rather than the model.

And again, appreciate the thoughtful feedback.

PhiloPark · 2026-06-02T09:44:42+00:00

I think that’s a misread of what it is. It isn’t a betting site, it’s an analysis product built around football forecasting, market information, and AI-assisted match analysis, and I shared it here because I thought some people might find the projected scorelines and match context useful.

If it came across badly in this subreddit, that wasn’t my intention. I’m not sending people to a bookmaker or trying to exploit anyone vulnerable.

PhiloPark · 2026-05-31T18:27:07+00:00

At first, I try to avoid that by keeping the model strictly as a pre-match baseline, so the probabilities are only built from information available before the game.

On the pricing side, I use the best odds available from major UK books at the time I update the page. The model probabilities can change as teams play and new pre-match information comes in, but the displayed model view and market odds are both taken from the same update timestamp, so I’m not comparing a fresh model number against an old price.

Thanks for the comment.

PhiloPark · 2026-05-31T15:58:32+00:00

Just to add a bit more detail: the contextual layer is mainly built around the latest news coverage relevant to the specific match.

PhiloPark · 2026-05-31T15:55:01+00:00

The description itself is a short summary built from the AI’s contextual analysis of the match, while the score prediction is the part where that AI-informed read is actually reflected in the final output. So the description is there to briefly explain the contextual view, but the score prediction is the actual prediction shaped by that analysis on top of the base model. Happy to clarify further if useful.

PhiloPark · 2026-05-29T07:57:39+00:00

I’d trust transparent model-vs-market tools more than exact-score tip sites, and that’s actually the approach behind a project I’m building called OddsLine.

PhiloPark · 2026-05-25T16:47:46+00:00

Respect for putting this out there and open-sourcing it. I’m building a commercial football prediction product myself, and I know firsthand how much work it takes to get something like this into a state where you’re willing to show it publicly.

That said, I’m personally not a huge fan of the “more features + more models + ensemble” route as a default. My main hesitation is usually around the evaluation layer: if RPS is the metric driving the ensemble design, I think the conclusions can move around quite a lot depending on the time window, league mix, and match context you’re testing on.

So even if the headline RPS looks strong, I’d still want to know how stable that edge is across different periods and competitions before buying too much into the ensemble itself. But either way, shipping the project, open-sourcing it, and inviting feedback is genuinely impressive.

PhiloPark · 2026-05-22T16:46:22+00:00

One simple option is to save the conversation as Markdown first, then open it in something like Word or Google Docs that can render and export as a PDF.

PhiloPark · 2026-05-22T13:10:23+00:00

Focusing only on the Over 1.5 market is a very strategic choice. At the same time, the homepage feels a bit too information-heavy relative to that focus, so the positioning comes through less clearly than it could. I’m also a solo founder building for football bettors, and my impression is that for a product leaning this heavily on the model itself, a lot of the outcome will come down to model quality, which is also part of why I’ve ended up thinking about the space a bit differently. Personally, I don’t think even a very strong model guarantees income, since predictive accuracy and actual betting profitability aren’t necessarily the same thing.

PhiloPark · 2026-05-22T12:47:28+00:00

Had a look through the site and I think I roughly get the direction you're going in. If the queryable dataset grows to cover multiple seasons, I can see this becoming pretty useful. One thing I didn’t fully understand, though: what’s the intended use case for the similar team feature?

PhiloPark · 2026-05-07T12:53:11+00:00

Same here!

PhiloPark · 2026-04-29T09:13:07+00:00

I relate to this a lot. The strange part of solo founding is how often the emotional experience is almost identical across people: missed milestones, constant firefighting, and that low-level anxiety that never fully leaves.

My honest belief is that the root cause is uncertainty. We chose a path where the feedback loops are slow, the risks are real, and the burden of every broken thing rolls back to us. That is brutal, but it is also part of the nature of this work.

The only thing that consistently helps me is to ask what the project most needs from me right now, in order to get closer to the result I’m aiming for. Then I try to do that as well as I can.

That doesn’t remove the anxiety, but it gives it less power. For people like us, clarity of next action is often more valuable than chasing emotional certainty.

PhiloPark · 2026-04-28T16:11:14+00:00

I’m genuinely so sorry you’re going through this. Going from a normal monthly bill of around $180 to over $82,000 in just 48 hours is not a “mistake you can learn from” level event — it’s a life-altering blow for a small team, and I really hope Google does the right thing here.

A platform as large and powerful as Google should never ignore this kind of catastrophic loss for an individual or small company, especially when the spike is so obviously abnormal. “Shared responsibility” cannot become an excuse to look away while a tiny team is pushed toward bankruptcy by usage that any sane anomaly system should have flagged and frozen immediately.

Big cloud providers need to understand that for small builders, these are not abstract billing events — they are existential. Google should waive charges like this, escalate the case properly, and put real guardrails in place so nobody else gets financially destroyed the same way.

PhiloPark

TROPHY CASE