maxdemarzi
Joined 17 years ago
Karma
883
Submissions
408
Member since
Oct 13
Checkout my blog about Graphs http://maxdemarzi.com
View on Hacker NewsRecent submissions
Comment · 5 months ago
Wouldn’t it be nice if your database could help you fine tune your model for better faster and cheaper text to sql? That’s what we’re exploring on this post.
Comment · 5 months ago
I'm happy enough to use LLMs for code, but I think it's nuts people are using it for their PERSONAL blogs. It's supposed to be me talking to my super niche audience. Never gonna happen.
Comment · 6 months ago
I can't shake the feeling that something is off about “context graphs”. This is my attempt at trying to explain why I feel this way.
Comment · 1 year ago
The current benchmark for real world text to sql is https://spider2-sql.github.io/ and the SOTA is at 64%
Anyone selling you 99% accuracy can prove it there first.
Comment · 1 year ago
I’ve had tattoos removed and currently removing two more. They are all 20 years old, very faded, blurry they honestly just didn’t look good any more.
The first removal 5 years ago would leave me bleeding and require bandage changes for a week.
The new tattoo removal lasers leave you feeling like a sun burn for two days. No blood, no bandages.
It will become way more common.
Comment · 2 years ago
Tell me more…
Comment · 2 years ago
It’s $275 a month plus $99 every 6 months at SlimDownRX. The compounded pharmacies are helping.
Comment · 3 years ago
The 14th way is “multi way joins” also called “worst case optimal joins” which is a terrible name.
It means instead of joining tables two at a time and dealing with the temporary results along the way (eating memory), you join 3 or more tables together without the temporary results.
There is a blog post and short video of this on https://relational.ai/blog/dovetail-join and the original paper is on https://dl.acm.org/doi/pdf/10.1145/3180143
I work for RelationalAI, we and about 4 other new database companies are bringing these new join algorithms to market after ten years in academia.
Comment · 3 years ago
Quite the opposite. The idea is to move as much of the business logic into the database. “Rel” definitions are meant to be written once and reused everywhere. Instead of letting the client decide different business logic every time, you capture and control it in one place.