3 ms·

I found the best way for me to write backend applications is with an ORM. Because SQL is super slow to write. The exception is sqlx in Rust when I want someth

by winrid 3y ago

I found the best way for me to write backend applications is with an ORM. Because SQL is super slow to write. The exception is sqlx in Rust when I want something super correct.

andrewstuart 3y ago
>> Because SQL is super slow to write. ChatGPT writes SQL incredibly well - presumably because there is so much training material out there. Seriously, ChatGPT is the single best reason to change your architecture away from ORM to plain SQL.
- winrid 3y ago
  That's interesting. But no. I can write queries so fast with the Django ORM it's silly. Especially dealing when dealing with relationships... Pycharm will auto complete like 4 levels of joins in two seconds. That's faster than you tabbing to chatGPT let alone writing the prompt.
- Lukas_Skywalker 3y ago
  Writing the code is only part of the equation though - especially if you are not very fluent in SQL. I imagine it gets annoying quite quickly if you need to ask ChatGPT what different fragments of SQL do 6 months after you have generated them.
- PrimeMcFly 3y ago
  Ah. So you're not writing the SQL, ChatGPT is. Yeah, no thanks. I'll stick with Django.
  - andrewstuart 3y ago
    Sounds like you still see ChatGPT as a bad thing in some way. I can almost hear the subtext "AHA GOTCHA! you don't understand the code being written!" ChatGPT is a programming assistant - it is an advantage that assists in your programming. You still have to understand the code, and more often than not you need to debug it and refactor it to make it work or make it work nicely. If you are not using ChatGPT as a programming assistant then you're wasting time and doing yourself a disservice.
    - PrimeMcFly 3y ago
      > Sounds like you still see ChatGPT as a bad thing in some way. Not really, it can be a useful tool, I'm not ready to just delegate all my code writing to it and no professional developer should either. You're talking about using raw SQL because it's "closer to the metal" (it isn't really), but then really you're just using ChatGPT to write your code so in a way, you're much further removed from the metal than framework developers. If I had to choose between an OS written in C++ by skilled humans vs an OS written in ASM (because it's 'closer to the metal') by someone who had ChatGPT write most of the code and "checked" it, I know which I'd choose.

by winrid 3y ago

I found the best way for me to write backend applications is with an ORM. Because SQL is super slow to write. The exception is sqlx in Rust when I want something super correct.

andrewstuart 3y ago

>> Because SQL is super slow to write. ChatGPT writes SQL incredibly well - presumably because there is so much training material out there. Seriously, ChatGPT is the single best reason to change your architecture away from ORM to plain SQL.

winrid 3y ago
That's interesting. But no. I can write queries so fast with the Django ORM it's silly. Especially dealing when dealing with relationships... Pycharm will auto complete like 4 levels of joins in two seconds. That's faster than you tabbing to chatGPT let alone writing the prompt.
Lukas_Skywalker 3y ago
Writing the code is only part of the equation though - especially if you are not very fluent in SQL. I imagine it gets annoying quite quickly if you need to ask ChatGPT what different fragments of SQL do 6 months after you have generated them.
PrimeMcFly 3y ago
Ah. So you're not writing the SQL, ChatGPT is. Yeah, no thanks. I'll stick with Django.
- andrewstuart 3y ago
  Sounds like you still see ChatGPT as a bad thing in some way. I can almost hear the subtext "AHA GOTCHA! you don't understand the code being written!" ChatGPT is a programming assistant - it is an advantage that assists in your programming. You still have to understand the code, and more often than not you need to debug it and refactor it to make it work or make it work nicely. If you are not using ChatGPT as a programming assistant then you're wasting time and doing yourself a disservice.
  - PrimeMcFly 3y ago
    > Sounds like you still see ChatGPT as a bad thing in some way. Not really, it can be a useful tool, I'm not ready to just delegate all my code writing to it and no professional developer should either. You're talking about using raw SQL because it's "closer to the metal" (it isn't really), but then really you're just using ChatGPT to write your code so in a way, you're much further removed from the metal than framework developers. If I had to choose between an OS written in C++ by skilled humans vs an OS written in ASM (because it's 'closer to the metal') by someone who had ChatGPT write most of the code and "checked" it, I know which I'd choose.