upvote
This has been a thing for long while, on codex too.

You ask it to do something, then tell it to do something in a different way, then it assumes it needs to do the refactor in a backward compatible way, or creates migrations for it etc.

reply
Omg the "backwards compatible fix" in a one-off script, I feel my ptsd coming on ...
reply
This is why I started adding a PROJECT.md file to all my projects and a hook for claude to read it.

It contains (Among other things) stuff like "this is a single user personal project, I'm the only user, this will never be open to the public internet" etc.

It kinda-sorta tones down the proclivity to worry about backwards compatibility and slight edge cases where if someone has edited some template and the new code doesn't support it.

reply
Oh good I thought I was doing something wrong! Using ChatGPT web for planning, ask for a prompt then notice something weird in the prompt and whether I:

1) use the edit in-place functionality; or

2) ask it to rewrite to remove something

It'll write the prompt as if the agent (codex) knew about the conversation and add "don't do X" etc. At first that bothered but I realized it doesn't really change the output so I stopped caring.

Still, no experience is unique I guess.

reply
I remember when I was updating some formats for my apps data files and it ended up writing v2 and laying it on top of the old one. Ended up just telling it to delete the entire feature and start again. I do think claude.md instructions help though.
reply
Oh no, you said "landed"! It's dug into our brains!
reply
I hate that I have to change the way I write to avoid AI-isms. I loved using "load bearing" to describe weird code that you think you can delete but is actually holding everything together.

Now people think I'm just parroting what Claude said. It sucks. I want my catch phrases back, I guess this is how em dash users felt

reply
As a former em-dash enjoyer, I indeed feel your pain.
reply
I'm with you an that one. RIP em-dash.
reply
Same here for em-dashes
reply
I feel like a lot of these have been LinkedIn-isms or PR-isms long before they have been AI-isms so not much is lost.
reply
I used to use em-dashes for explanatory clauses--like this one, for example--when using commas would make the sentence difficult to parse due to other nearby commas.

They're only a LinkedIn-ism when used to create an unduly dramatic juxtaposition for an otherwise mundane idea. But now they set off people's AI radar when used for any reason at all.

reply
Perhaps I am biased because I find the use of em-dashes without spaces (as is common in English typesetting) to be inherently ugly so I'm not too unhappy to see their use discouraged.
reply
You could say it landed cleanly.
reply
Good instinct. Fair challenge. This corrects my framing. It makes your point sharp. This is a significant finding. Positively confirmed. That settles it, and it flips the picture. Honest verdict - this is not small. Let me wire it in.
reply
There's got to be a Weird Al song like this coming soon.
reply
Bless the lord that it's not been presented to us yet, because you just know that it exists already.
reply
[flagged]
reply
Oh. Oh no.
reply
There needs to be a pithy name for this. I have been calling it context leak.
reply