neprotivo

3 ms·

1.
by neprotivo 2mo ago
Improving code understanding is the main focus of my work and thinking right now. If we want to make advances I believe that we should rely more heavily on one key quality of the program code: It is meant to be executed. Here are some ideas
2.
by neprotivo 2mo ago
I am using Go right now for personal projects. One such project is to collect per-test-case coverage data and use it to study the structure of the underlying codebase. I'm hoping to develop a new knowledge base for agents to do feature
3.
by neprotivo 3mo ago
If you are using Jujutsu you can achieve a basic way to maintain a public repo from a private monorepo with very little code and without Copybara. I wrote up how to do it here: https://vihren.dev/blog/20260625-jj-public
4.
Projection: A JJ Workflow for splitting public and private files(vihren.dev)
3 points by neprotivo 3mo ago|2 comments
5.
by neprotivo 3mo ago
Hi HN, 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, an
6.
by neprotivo 1y ago
This approach of solving a problem by building a low-perplexity path towards the solution reminds me of Grothendieck's approach towards solving complex mathematical problems - you gradually build a theory which eventually makes the pr
7.
by neprotivo 1y ago
TLDR: * 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 issu
8.
What constitutes debugging? Empirical findings from live-coding streams(tzanko.substack.com)
3 points by neprotivo 1y ago|1 comments
9.
by neprotivo 4y ago
It looks like the new Blockchain is quite centralized. 45% of blocks are mined by just two addresses: https://twitter.com/santimentfeed/status/1570339602346684416...