Reviewing agents PR in a vibe coding era still feels a bit heavy. Skim allows you to "vibe review" your PRs, focusing on changes to concepts and logic rather than individual lines
Separately we also found that git lfs is not very optimised for large repositories, notably its locking feature which list every file tracked by git for every checkout and commit command.
To clarify here, "generated" and "autogenerated" were bad choices of words. They're translations created by humans and is dependent on the strings in code.
The translations are dependent on the original strings that is in code. For example if we change "design anything" to "design everything", the translations also needs to be updated to reflect that and by keeping it within vcs, we have an atomic change including both code, copy and translation. Moving it to a database would make updates easier but would now be a separate process to "sync" between copy change in code and translation changes in the database
Author here, the phrase "generated" was the wrong choice of word here. These translations are manually translated by humans in another systems and consolidated into these .xlf files so they're dependent on what the original strings are in code at a specific commit. They cannot be generated on the fly
Hi Hacker News, Tidbits is a project that I had been working on to filter through clickbait news articles, sensational headlines and low impact articles. With large language models gaining popularity, this project outsource the filtering process and send notification for articles that are newsworthy. There had been a few similar posts in recent days and it's great to see this issue being solved by others as well. I had been a big fan of Sip by Product Hunt before it was shutdown and wanted to recreate a similar experience!
author here, xlf files are translations that are coupled with the texts we set in the code so they're not really generated I admit that was misleading. What I wanted to get across is they're not touched directly by engineers but they're still created through our translation pipeline where real humans translate them
Author here, not everyone on the team works on git and git performance. Our team work on a variety of things that touch "code" in general like our ownership system and tooling, access control, bots and automation, etc...
Sorry, there is a quote from the article:
"Kudos to other members of the Source Control team — Alex Sadleir, Wesley Li, Adam Murray, Matthew Chhoeu — who work on improving git performance at Canva"
So I assume 5 people working specifically on Git performance ;-P
Sorry I've been a bit misleading. These xlf files aren't generated, they're just not interacted with by engineers but they're still created and edited by humans as translations. We want to keep track of them so that if we deploy a different commit, the texts and translations in other languages will match
reply