pgxbackup: Continuity Support for pgBackRest

(thebuild.com)

26 points by Wingy2 days ago

2 comments

moontear43 minutes ago
Is the co-authoring by Claude good practice or is it better to not have that reference in each commit?<p>I kind of feel all the commits by Claude everywhere are a marketing gig. In terms of transparency of course state somewhere that you are using AI, but personally it doesn’t help me seeing this on every commit. Ultimately you don’t know anyways which part of the commit was AI-inspired, AI-written or human-written, but the co-authored by Claude makes it seem that everything was done by AI and maybe diminishing its credibility.
- bakugo30 minutes ago
  > but the co-authored by Claude makes it seem that everything was done by AI<p>Likely because, in 99% of cases, it was. I doubt anyone would willingly leave the co-author advertisement (because that's what it is, an advertisement) on display in all their commits unless they've gone all-in on the fad and are actively proud of the fact that they're not writing any code themselves.<p>That said, I don't think this is a bad thing. It helps signal which projects should be avoided if you care about quality at all.
wg01 hour ago
Why not hire the original author?
- lfittl1 hour ago
  The original author of pgBackRest posted on LinkedIn today that he will very likely revive the project, given the interest and new sponsorship opportunities: <a href="https://www.linkedin.com/feed/update/urn:li:activity:7457070556736028672/" rel="nofollow">https://www.linkedin.com/feed/update/urn:li:activity:7457070...</a><p>That said, this post predates that LinkedIn post, so I don't think it was intended to compete with the original author's own efforts, but rather to provide continuity for PGX's customers.