souperdeluxe's comments

Without pre-commit you should squash on merge. That way main is atomic. But squashing loses granularity. A single merge commit might both refactor a function and implement a feature. You could split it into two pull requests, but maybe the feature depends on the refactor. Now your feature branch needs to cherry pick from the refactor branch. What if the refactor branch makes further changes prior to being merged? Now your feature branch has conflicts.

With pre-commit you can disable squashing on merge. You'll have a refactor commit and a feature commit. Changes to the refactor can be --fixup followed by rebase. I find this much easier than juggling two pull requests.

I accept that this is only viable with buy-in from everyone on the team, and I wouldn't advise it for teams over 10 people. But for small teams, I love pre-commit and trunk-based development.

We're doing something similar at our company. We're fine tuning small LLMs and using them as isolated components of a larger deterministic system. When we tried using LLMs for larger components of the system we ended up writing a lot of pseudo-code into the prompt. That was better off as just code. Now we can quickly find tune our business logic based on client preferences, without having to dig into the prompt. This also means we build trust in our prompts over time, because they change less often.

Wife changing technology. Amazing work guys.

Solution: https://www.reddit.com/r/MacOSBeta/comments/15ha2r8/comment/...

Same. I have 10 CGPDFService processes running for over 24 hours. Two CPU's are at 100%, and together they're using 15GB of RAM. I can SIGKILL but they come back after 5 minutes. Some people believe they're related to the slow-mo screensaver, which I disabled in my settings. It's only happening on my Mac Studio (which isn't logged in), and not on my Macbook Air (which I'm currently using).