• 0 Posts
  • 7 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle
  • As someone whose employer is strongly pushing them to use AI assistants in coding: no. At best, it’s like being tied to a shitty intern that copies code off stack overflow and then blows me up on slack when it magically doesn’t work. I still don’t understand why everyone is so excited about them. The only tasks they can handle competently are tasks I can easily do on my own (and with a lot less re-typing.)

    Sure, they’ll grow over the years, but Altman et al are complaining that they’re running out of training data. And even with an unlimited body of training data for future models, we’ll still end up with something about as intelligent as a kid that’s been locked in a windowless room with books their whole life and can either parrot opinions they’ve read or make shit up and hope you believe it. I’ll think we’ll get a series of incompetent products with increasing ability to make wrong shit up on the fly until C-suite moves on to the next shiny bullshit.

    That’s not to say we’re not capable of creating a generally-intelligent system on par with or exceeding human intelligence, but I really don’t think LLMs will allow for that.

    tl;dr: a lot of woo in the tech community that the linux community isn’t as on board with







  • I do most things on the command-line and for me, the trick is not having a lot of scripts laying around. If it’s a common action I do a lot (like running the local test bed), I rely on shell history. Beyond that I just start chaining stuff together on the fly. It forces me to keep knowledge of the utilities fresh, and also keeps me from having a ~/bin folder full of outdated crap that almost does what I want.