this post was submitted on 01 Sep 2026
23 points (92.6% liked)

Programming

28384 readers
269 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
23
You have to beat the models at something (www.seangoedecke.com)
submitted 5 days ago by codeinabox@programming.dev 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
[–] ATS1312@lemmy.dbzer0.com 1 points 3 days ago* (last edited 3 days 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.