HNHacker News
TopNewBestAskShowJobs

djeiejejejej

6 karma · joined August 31, 2024

submissionscomments
djeiejejejej··on Taming the beast that is the Django ORM – An introduction
Yes I agree. That’s a valid argument, but there are other ways as well like SQLKata and other query builders.

Depending on the complexity of the product I think writing standard SQL92 will get you far as well.

I don’t get how an ORM will handle Postgres’ CTEs and windowing functions. Those are pretty basic and extremely useful features to me, but those require dropping to raw SQL. Each vendor has those useful particularities that you immediately lose by going ORM.

So in practice you are already required to make your queries as bland as possible where GROUP BY and JOIN is about as complex as it will get. I’d say just do SQL92 work around the limitations - which is something you’ll have to do anyway, but now more directly - and all major vendors will work OOB.

djeiejejejej··on Taming the beast that is the Django ORM – An introduction
Same here, but IMO it is related to skill and experience.

Once you get sufficiently familiar with some paradigm the training wheels can come off.

“Raw” SQL is already an abstraction. Over time all the implicit magic will get on your nerves. Trying to shoehorn two completely different worlds into one abstraction is not worth it: you get to learn today’s untransferable funky ORM syntax and idiosyncrasies while losing sight of the actual skill that matters long term which is SQL itself.

I concede however that handling of SQL, the field names, the relations, is annoying. But it’s core to the problem you are probably solving (some form of CRUD). Plumbing is annoying but as a plumber I’d say get used to it instead of wishing to be dancer.

I notice this in other aspects of my work as well. When I switched away trom desktop environment to terminal I had the same feeling. It’s easier, less hassle, less wonky abstractions, more direct. Completely counter to what popular culture is telling me.

djeiejejejej··on Artifacts are now generally available
This does not take a couple of hours. I can assure you of that.

The app description sounds like it was more work to come up with than the app code itself.

Also, this is an extremely common, bland and simplistic example. You’ll see it flail and falter on slightly less generic boilerplate-heavy “apps” and there is no known tech/theory that’ll get us there. We just hope more “scale” will magically solve all its issues, but IMO that’s not going to happen. The paradigm just doesn’t allow it. Time will tell who is right of course.

I don’t want to downplay the recent LLM achievements because they are amazing, but this is not taking any (programming) jobs.

I’m actually not too worried about the current wave of AI. Copilot is an annoyance and GPT4 is lying so much it’s getting old. LLMs have deep issues that I’m not seeing much improvement on. The next wave of AI however.. I’m not sure. It’s a matter of time.