Flutterby™! : Github issues showing fighting with CoPilot

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Github issues showing fighting with CoPilot

2025-05-22 17:26:58.323496+02 by Dan Lyke 0 comments

Dusty Burwell @dustyburwell@twit.social

Oh my god. I just had the terrible realization that AI coding agents take the Mythical Man Month and make it last forever. They're new to the project and they'll never learn anything, so they're always new to the project.

in response to Reddit /r/ExperiencedDevs: My new hobby: watching AI slowly drive Microsoft employees insane

Jokes aside, GitHub/Microsoft recently announced the public preview for their GitHub Copilot agent.

The agent has recently been deployed to open PRs on the .NET runtime repo and it’s…not great. It’s not my best trait, but I can't help enjoying some good schadenfreude. Here are some examples:

I actually feel bad for the employees being assigned to review these PRs. But, if this is the future of our field, I think I want off the ride.

The hilarity of people trying to fix bad code with English is...

As an Emacs user, one of the things I often wonder is how people get along in editors that don't have a lot of the capabilities that I've become used to. Block operations, keyboard playback, it's amazing how many times I've sat down at IDEs or modern editors over the years and the system just didn't have what I think of as core operations.

This brave new world of "describe in English what your edits should be, and then get something non-deterministic and wrong, and then describe again" seems like the even further stupidification of code editing.

[ related topics: Religion Interactive Drama Humor Microsoft Invention and Design Software Engineering moron Work, productivity and environment Artificial Intelligence hubris ]

comments in ascending chronological order (reverse):

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)




Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.