It also made good engineering easier.

AI is an amplifier of existing behavior.

> Your intent is 'Getting more users by lowering barriers to sign up', a business goal.

Important point.

But it says more about OP’s perspective on product-driven development than this “contextual commits”.

The idea that OP does not follow up on is whether these codified commit messages with a very shallow summary of the LLM context improve anything compared to the normal commit messages that Claude will generate.

I suspect they’re equally insufficient since even a compacted context seems less diffusing and it’s still a lot bigger than these.

> I wish our profession would stop trying to reinvent issue tracking in git every week.

I would love to have good git-powered issue tracking. I haven’t seen it yet.

It’s not that you are wrong.

Just that the message does not contribute to the conversation.

Neither does this one.

I think you have a fair point, but you bothered to give feedback for how this article could be more congruent as if a non-assisted writing process would not warrant similar feedback.

The number of blog sentences that end abruptly halfway through have drastically fallen since I applied AI to my writing process.

There is nuance beyond the feeling that you know the author because he either uses the em dash a lot, the word “comprehensive” a lot, uses bullet points with bold text a lot, or writes detailed summaries reiterating what was just said. I read a lot from that author and I could use a break.

The ~foo as backup convention is not part of any standard.

Using hidden files is a stronger convention, e.g. .foo.swp or .foo~.

But nginx's sites-enabled also doesn't filter those.

It's a very simple mechanism that assumes what you put in that directory is a website configuration.

Adding backup files here and there is considered spam, no matter how old it is.

It's the second thing I fix in either Vim or Emacs: Put backup files in a central location. (The first is proper indentation/spacing rules.)