I am not a sports analyst. I don’t have insider knowledge of team sheet dynamics, injury recovery timelines, or the subtle psychological impact of playing a Thursday night game in Canberra in July. What I do have is Claude, a Python environment, and a dangerous amount of free time. The result is nrl-predictor.ohare.id.au — an AI-powered NRL match predictor that publishes its picks every week and, crucially, publishes its accuracy record even when it’s wrong.

I recently worked through a tutorial using Google’s Agent Development Kit (ADK), a Python framework for building multi-agent AI workflows. The tutorial used a fun premise: an AI pipeline that researches historical figures and generates full movie pitches, complete with plot outlines, box office projections, and casting suggestions. What is Google ADK? The ADK lets you compose multiple AI agents into pipelines using three core building blocks: SequentialAgent — runs sub-agents one after another, passing state between them LoopAgent — repeatedly runs sub-agents until a termination condition is met (using exit_loop) ParallelAgent — runs sub-agents concurrently and merges their outputs Agents communicate through a shared state dictionary, which tools can read and write via a ToolContext object.

Python Instance and Class Variables Call me late to the game, but TIL about Python Instance and Class variables the hard way. Setting up mulplie classes using composition and was struck wondering why when storing data in a list of class instances, the data was stored across all instances. As specified 9.3.5. Class and Instance Variables class Dog: kind = 'canine' # class variable shared by all instances def __init__(self, name): self.