Only because I thought, “Why not?”, I’ve grabbed some screenshots to show what the DuFFLe looks like under the hood.
The DuFFLe’s engine is a relational database. The schema looks like this:
The remaining screenshots are of the database interface. The Overview shows the current fixture and our list of DuFFLe players, the team name and home ground.
When you submit a team, I enter your selections into the database by clicking on the appropriate player position (ruck/back/mid/fwd/int). If I make a mistake in data entry here, it is usually a click on the wrong player. To avoid errors due to Byes, unavailable players are highlighted. If you don’t put a team in, I have some handy tables on this screen which shows stats for the players in your squad - i.e. best ruckman etc.
At the conclusion of the AFL round, I scrape the player statistics from the FinalSiren.com website and then import this data into the database.
After the player stats have been imported, I have a sequence of coding scripts that is executed that works out the results, if-only and various ladders/tables.
The data that I copy/paste into Dockerland is placed here ready for me to create the various posts:
I manage the various trade requests via this screen. Nothing special to see here except your squad, available players and a log of all your squad transactions. That’s how I keep a watch to see you don’t use more Trades than you are allowed.
The Draft Night’s shenanigans are also managed similarly. The only difference is that I have a list of good ruckman, backs, midfielders, forwards and utilities who I can choose for you if there is a need.
My Statistics tab shows some useful stats which are sorted according to the radio button selected. For example, sort the tables by the backs with the largest aggregate DuFFle points score, or sort them by the average score as a forward.
So, that’s the DuFFLe engine in brief. I enjoy the scripting associated with the database, hence the recent addition of the Trade Bait posts. Perhaps you can give me a challenge that is related to this database.