• 5 Posts
  • 421 Comments
Joined 1 year ago
cake
Cake day: January 3rd, 2024

help-circle












  • Fair enough.

    Here’s what I remember: invoking SQL containing inserts from bash has resulted in lost data, when fairly unsurprising database things happened, since bash didn’t really expect to be in charge of logging the details of the attempted change. For the error, it wasn’t something surprising - maybe it was “max connections reached”, stuff that will just happen sometimes.

    The data loss was probably solveable in bash, but the scripter didn’t think to (and probably would have needed more effort in a full development tool).




  • You’re oversimplifying things here there are a lot

    I think… we’re agreeing?

    My point is that what is currently possible with AI doesn’t solve any of that.

    People in this thread keep discussing growth in programmer productivity as if programmer typing speed and number of languages known are the limiting factors of programmer productivity. They are not. It’s all the other bullshit that makes (the vast majority of) programming projects fail.

    My source: I know so many programming languages and I type insanely fast. My team is also productive beyond all reason. These two tidbits are only related in that I tried and failed with the first before succeeding with the second.



  • but how do people have the patience to deal with all of that in the beginning?

    Whenever I was frustrated with a stupid undecipherable error message, I would just tweak my vim config a bit.

    Within a few minutes, my rage at the error would be completely replaced with rage toward vimscript.

    Then I would revert my vim config change, and return to the undecipherable error message with a fresh perspective. mainly relief that at least it’s not vimscript.

    Joking aside, I really did learn vim mostly during coffee breaks or while waiting on some long running build process.