I wrote up a Jujutsu workflow that I came up with recently. I wanted to work on a public open-source repository while also versioning the private context files that influenced each public commit: specs, product notes, experiments, and agent instructions.

I use coding agents heavily, which means the specs are often as important as the final code. I wanted a proper way to manage them without making them reachable from public history.

Jujutsu’s features give us a compact solution based on filesets, revsets, and `git.private commits`. With a small amount of code, this achieves a public/private split without much heavier tools like Copybara.

This is advanced material. It assumes intermediate jj knowledge, especially around revsets. Let me know what you think.

Comments URL: https://news.ycombinator.com/item?id=48720489

Points: 3

# Comments: 2

https://ncatlab.org/nlab/show/The+Rising+Sea

* Debugging takes 35%-50% of a developer's time

* In the study 79% of the time was spent on the top 26% of the bugs

* Fresh bugs appearing during ongoing work take 3 minutes to fix on average. Committed bugs appearing in the issue tracker take 29 minutes on average

* When running/testing during debugging sessions devs run the code manually (84%) rather than relying on automated tests

* When inspecting program state devs rely on looking at logs and print statements 70% of the cases and in only 30% use a debugger

Comments URL: https://news.ycombinator.com/item?id=44798206

Points: 3

# Comments: 1