4 ms·
Ah. So you're not writing the SQL, ChatGPT is. Yeah, no thanks. I'll stick with Django.
by PrimeMcFly 3y ago
Ah. So you're not writing the SQL, ChatGPT is.
Yeah, no thanks. I'll stick with Django.
- andrewstuart 3y agoSounds 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.