18
You have to beat the models at something (www.seangoedecke.com)
submitted 2 months ago by to c/programming@programming.dev
19 comments fedilink hide all child comments
 

I think it’s more useful to look at the tasks models haven’t gotten better at over time, and the tasks that are hard for them get better at in principle. The two best examples of these are:

  1. Deep familiarity with the codebase
  2. Technical communication
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 months ago (1 child)

What are you talking about? A study showing that code made with the "help" of slop machines is worse in quality and contains more issues is unrelated to capitalism.

If anything, people defending slop coding are the ones brainwashed by capitalism, with a cult of the "faster/more efficient" that makes them believe that code produced fast is good code no matter what.

Hallucinatory slop has no place in the making of software, or anything else.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 2 months ago* (last edited 2 months ago)

    Yeah, I didn't mean to say "engineers jobs will go away." I ADHDed mid-thought, posted, and walked away stoned. That was supposed to be about executives, and the comment is now edited appropriately.

    Does that change your thoughts?

    The growth-curve of these machines' utility is actually exponential, given rich enough data. That we've come this far says we might not have plateau-ed yet. However, this changes Engineers' work to be PAINFULLY tedious, and we've got an unprecedented burnout rate as a result. We need a new way forward that isn't this.

  • permalink
  • fedilink
  • source
  • parent