Upon reflection, I've come to believe that quality software is not about how many features something has or how quickly it is built but rather how cared for it is by the designers, developers, and product people who work on it. There's an ineffable aspect to my favorite pieces of software where I don't think of it is as feature matrix but rather as an interface made by a human for humans that's a joy to use. And when you build software with AI, it leads to worse software. Sure, it's faster to build initially, but I think to the detriment of the quality of the code and the user interface and the user experience.

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 day ago (1 child)

Learning programming, maybe, maybe not. But I have had success being like "assume I already know Ruby, Python, JavaScript, and Haskell. What are the quick pointers and cheat sheets for using R, especially the ggplot2 library"

I could read an R tutorial, but I don't need to learn about variables and what comments are or how to call a function. I just want to know the differences between what I'm already used to.

And I'll admit it was useful to already have that context to throw follow-up questions into when they came up, like "what's the difference between = and <-" which are famously hard questions to Google

  • source
  • parent
  • hideshow 2 child comments
  • [–] 12 points 1 day ago

    It seems like most responsible use cases of AI involve users who have a substantial knowledge base with which to sniff test AI's output, which is at odds with the dream of AI which is to have illiterate morons do all the work for slave wages.

  • source
  • parent