1,944 karma · joined May 4, 2012
@santiagobasulto on Twitter.
Want to try DataWars? app.datawars.io/register
Want to reach out? santiago [dot] basulto [at] gmail
meet.hn/city/45.0677551,7.6824892/Turin
Socials: - github.com/santiagobasulto - x.com/santiagobasulto
---
PS: Are you in Italy?
But YC is so prevalent in the hacker community that is kinda associated with Open Source, is like we feel entitled to ask for explanations when in reality it’s just a private business. It’s an interesting phenomenon.
I think it’d be great if you could keep transparency in order to keep encouraging founders to apply to YC, but we have to learn that’s just an option.
RAPTOR for example is a technique that groups and clusters documents together, summarizes them, and creates embeddings defining a sort of a Tree. Paper: https://arxiv.org/html/2401.18059v1
Agentic RAG is creating an agent that can decide to augment "conversations" (or other LLM tools) with RAG searches and analyze its relevance. Pretty useful, but hard to implement right.
You can google the others, they're all more or less these "techniques" to improve an old-fashioned RAG search.
It has happened that a dev in our team was populating an endpoint that used inheritance and when looking at the number of queries we were over 100.
But the solution in those cases is just OUTER JOINs and CASE. Especially since we use Postgres in the backend and it works so well.
So yes, there are some pitfalls, but they're greatly overshadowed by the advantages of the ORM.
First, it let's you get started quickly and prototype. You can write unit tests, make sure everything is working as expected, then count queries and make sure you're being efficient with your SQL engine.
Second, and even more importantly, it's crucial in the definition of the app and the Schema. Thinking in high level "classes and objects" helps with the abstraction and the design of the apps. Even if you then default to raw SQU queries, thinking and building your model with class abstractions is huge.
Finally, there are some "tiny details" (but in my eyes, very important) that everybody oversees:
* Migrations: the way Django has designed migrations is just marvelous. We've migrated tons of data and changed the structure of our DB multiple times without any issues.
* Troubleshooting and "reporting": the ability to fire a quick shell, load a few models in Django's REPL, and do a few `.filters()` is for me key. On top of that, we add a Jupyter server connected to our read replica and we can do all sorts of reporting VERY QUICKLY. Not everybody needs a Data Lake :)
PS: We've ran Django sites accessed by millions of people per month. And we never had an issue with the ORM. Yes, sometimes I have to tell more junior devs that the gymnastics they're doing with `select_related` and `prefetch_related` can be more easily and effectively resolved with a query. But that's it. I'd say less than 1% of all the queries in our codebase have to be migrated to raw SQL.
Can I ask you what are the reasons you decide to stay?
And by the way, counterintuitively, languages have NOT evolved to be better understood, but on the contrary, to "separate" or create cohesion in smaller groups.
Any centralized institution that is in charge of overseeing a large and diverse number of countries that have evolved spanish over the past ~400 years is, in my eyes, set to fail.
Now, I do use RAE all the time to check definitions, but I see it as a "descriptive" body, in charge of creating some definitions. But even some of those definitions have to be "scrutinized" and can't be literally and blindly trusted. For example, check the definition of "gitano", which has a clear pejorative connotation. That is not wrong, is just the reality of how the "spanish speaking world" expresses itself. But should you take that definition by heart? I don't think so.
This is a clear example of "The Cathedral vs the Bazaar", as in Open Source vs privative software. I'm a hacker, I prefer a bazaar to a single institution dictating how we should talk..
And what I love the most about these guys (Marc, PG, even Sam Altman) is that they ARE hackers. They speak in our terms, they have our awkwardness.
Thanks for sharing this.
While I was watching that i said: “DUDE! I remember that quote (and that illustration)”. Went to my text book and there it was. In Tanenbaum’s networking textbook.
Aside from the anecdote, this guy has had a huge influence in the whole industry (not even mentioning the Kernel debates).