65
using GitHub CoPilot leads to the obvious consequence (archive.is)
submitted 6 months ago by dgerard@awful.systems to c/techtakes@awful.systems
66 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[-] Architeuthis@awful.systems 26 points 6 months ago* (last edited 6 months ago)

Honestly, the evident plethora of poor programming practices is the least notable thing about all this; using roided autocomplete to cut corners was never going to be a well calculated decision, it's always the cherry on top of a shit-cake.

[-] ebu@awful.systems 22 points 6 months ago

the upside: we can now watch "disruptive startups" go through the aquire funding -> slapdash development -> catastrophic failure -> postmortem cycle at breakneck speeds

[-] swlabr@awful.systems 12 points 6 months ago

roided autocomplete

My autocomplete:

  • written in an hour on a whiteboard for a job interview
  • uses only the finest words, hand-selected by unix
  • speed and size efficient

Roided autocomplete:

  • years of development, billions of dollars of investment
  • hallucinates constantly
  • projected to use all computing capacity at current rates
this post was submitted on 13 Jun 2024
65 points (100.0% liked)

TechTakes

1489 readers
31 users here now

Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.

This is not debate club. Unless it’s amusing debate.

For actually-good tech, you want our NotAwfulTech community

founded 2 years ago
MODERATORS
dgerard@awful.systems