Oops my new favourite typo: gut status

Do I feel great that I chose Cherki for this blog. Yes, yes, I do 😆

I'm thinking liking this new way of coding is correlated to whether your results orientated. If you liked the process of writing the code more than the results, you probably don't like the new way.

One quarter down.. some reflections

a) the new models are so good and fast, even for analysis.
b) meetings have gone from context switch problems, to oh fuck I could have done so much in that half an hour/hour
c) it's hard to turn off the PC at the end of the day, you can get loads done in 15 mins

Oaky

Claude Opus loves to say "good instinct" and then completely burn your idea to the ground 🔥🔥🔥

codex init

Good catch.

I use the plan mode more like research mode. E.g. I am building a ML repo and a little background. I don't really like cookie cutter, I think meta have some interesting ideas, twitter once released the algorthim, research some ideas.

Sounds amazing. I remember reading that ball tree was written by jakevdp and found his blog:

jakevdp.github.io/blog/2013/04...

How far back in time can you understand English? An experiment in language change

"As his post goes on, his language gets older. 100 years older with each jump. The spelling changes. The grammar changes. Words you know are replaced by unfamiliar words" Fascinating. So how far back in time can YOU go?

More please 🤩. I just finished my first t-shirt yesterday (first time sewing). I always wanted a longer body section than you can get in the shops.

The good thing with LLMs is you get fast feedback about whether your docs actually work.

I think it will work if we:
a) build polished models with standardised naming
b) put docs against the columns and data
c) have a good bank of example queries
d) start documenting that knowledge living inside our heads

I found them useful for doing boring stuff like picking thresholds for capping averages. They can iterate through five different versions quickly. I am experimenting quite a bit with text-to-sql. I tried indexed memories for the LLMs to pick up the kind of knowledge your talking about.

Thanks, I guess I need to add some claude instructions to the repo then.

One underated feature that I don't see mentioned in the old blog is zooming in on the box area, rather than showing half of the pitch.

Ha 🤣. I don't have a personal claude account yet. There is a million side projects that I am itching to finish with its power.

I am wondering what claude's default library would be if you didn't prompt it to use mplsoccer.

If you are using claude out of interest, did it use mplsoccer?

It appears Bournemouth like to recruit from my thread 🤣

Soler / Rayan

bsky.app/profile/numb...

Well at the least the way I have it structured is around domains:

loyalty
bookings
inventory
...

The agent also suggested having a common one around joins/ data quality.

Each domain has it's own MDs. I imagine you could structure files so it could progressively disclose table schema in a domain.

I am building text-to-sql at the moment for my own use. I decided to use skills, as then you can progressively disclose the datasets available to match the query.

Ooh I also have been thinking about this. My aim is to have a database of SQL examples agents could pull from as the models understand everything apart from our data structure.

Yay you're back! I have learnt so much off you and fastai 🚀

The first comment is "Since you clearly need someone to hold your hand through the basics of software engineering, here is a list of tasks you need to complete before this 'library' is even remotely fit for human consumption. Try to pay attention this time"

The last comment on the TODO list is "Get to work. And try not to break anything else while you're at it." 🤣

I tested something similar, asked the other agent to add a TODO list and it named it "TODO_FOR_SLOPPY_AGENT.md" 🤣

2025 NFL Rulebook | NFL Football Operations Explore the official 2025 NFL rulebook.

There is more details on the NFL pitch dimensions here:

operations.nfl.com/the-rules/nf...

I actually want to make a vertical pitch (see picture) where all the numbers (50, 40, 30, 20, 10) are aligned.

In theory, each digit (5, 0 etc.) should fit exactly in a box of a certain size. This is tricky in matplotlib as the text is defined in points. It also needs to work for different figsize.

I am also trying to add NFL to the existing library.

Something that I have been struggling to in matplotlib is to align text placed at a 90 degree angle so that if you place text at x = 30, y = 10 and new text at x = 30, y = 20 the text is aligned with a baseline: matplotlib.org/stable/galle...