The key advantage of AI code assistants is they allow you to increase velocity. Velocity, of course, being the worst possible thing a software project can have, from the user's perspective. https://mastodon.online/@codechimp/117495289268759476
0 Boosts
0 Likes
@mcc God, remembering hearing the top leadership of the ex-workplace going on about how we have to adopt AI or we risk falling behind everyone else who does it, and.
Dude.
My guy.
Falling behind in FUCKING WHAT. What race are you imagining you are in.
As if not constantly changing your app means people would stop using it. That is the OPPOSITE of what people want.
@mcc
I would suggest it's only increasing speed, as it lacks direction.
@mcc really love that the github issue appears to just be people summarizing the same problem with their own llm agent over and over again. that should get everything fixed
@chrisw_b i tend to write very detailed bug reports which i try to infuse with both careful testing and an awareness of what types of information a developer needs. depending on how things shake out, this tends to very occasionally be a godsend to an engaged developer, or just be tremendously irritating to someone doing basic triage because they have to dig through excessive detail to get to the bits they care about. i try to fight this tendency but it can be hard, it's how i think. (1/2)
@mcc interested in some thoughts on how to improve things for triaging folks?
@dngrs You mean, with regard to my personal filing techniques?
Yes, I'm interested.
@mcc yup! personally I'd sequence it like
1. hey there - this report is 100% human-written
2. short description of bug, impact/security implications, affected subsystem(s)
3. all gory details below
@dngrs i feel like if i had to preface everything i said by clarifying i was a human, a part of me would die each time. i feel like they ought to be making the *fillertext-generator users* disclose they used a fillertext generator, and if i can't have that, i feel like i'd rather leave the open source community completely and find a community where inhuman contributors are simply banned to spend my time
@dngrs i've definitely been trying, for a long time actually to frame things more as "tldr" then "full details", but sometimes people react to the length regardless of the tldr. maybe i should just start querying if they want a more detailed report before submitting a more detailed report.
@chrisw_b a thing i've been considering how is that soon, the mere fact that my posts are long will be an "ignore" signal even for receptive devs, because verbiage is a sign of LLM.
@chrisw_b (I also use a lot of emdashes, but for reasons I *cannot* explain, I realized this year I have been using emdashes wrong since high school. There are two emdash standards, you write them—like this—or else, you write them — like this. I somehow got the habit splitting the difference— like this. Not sure if that makes me seem more or less human)
Kinetic energy is also proportional to the square of velocity, which is how much more it's going to hurt when the slop code comes back to bite you 
@mcc its not great from a developers perspective: At work i'm taking on functionality from Devs or LLM where I haven't read the code and don't really understand it until a week or two later.