__eddie__

Apologies for not rewarding your trust ;)

Would be very interested to read an article on the literal interpretation of my title.

Also just wanted to say thank you for this comment - made my day :)

Sorry, where are you seeing this? In one of the code samples?

> Sup Eddie, the actual motivating example is we finally nixed Pandas from Data Ingestion, now reading excel files takes 2 seconds instead of 2 minutes. However unfortunately your

I shall pass this information along to my sleep paralysis demons. They'll be glad to hear it.

> > TODO: rewrite this entire service

Part of me enjoys the historical significance of this. However, I feel like keeping it would violate my own princples: https://eddie.codes/posts/source-code-comments/

Yes, this was something I emphasised more in the slides / my actual talk. But it's just significantly easier to reason about the APIs for both DuckDB and Polars

Sorry, fixed it now!

Published two posts at the same time and total PEBCAK

Yep, fixed now. Sorry!

Fixed!

Yep sorry, fixing now. It's what you get for being bitten by the bug to write twice in the same day

True, but also if Polars and DuckDB offer a similar experience with the ability to scale beyond that range, why not use them (for new projects)?

This isn't a call to arms to rewrite everything in the new shiny, just consider the new shiny for new shiny things

This bot has reported my repo of University lab exercises as being potentially copyright infringing.

I emailed the lecturer who taught me this course and they did not request or support this action. On the contrary they were supportive of me making my solutions public on the web.

It is worth noting that these exercises were not assessed and were purely for the purposes of learning and understanding the course content. In addition, there is no proprietary code anywhere in this repo.