1. It'd save a lot of time if one could just click a Markdown PR description and start editing it, without entering edit mode first.
2. Thanks to the following prompt, I barely write PR descriptions these days.
> Run `gh pr view` then `gh pr edit` to fill out the PR description. Use my words verbatim as much as possible. Be brief. Use tasteful markdown formatting.
Very glad you're working on this! Here is my wish list as a code reviewer:
1. Allow me to step through the code execution paths that have been modified in the pull request, based on the tests that have been modified.
2. Allow me to see the data being handled in variables as I look through the code.
3. Allow me to see code coverage of each part of the code.
4. Show me the full file as I am navigating through the program execution so that I can feel the level of abstraction and notice nearby repetition or code that would benefit from being cleaned up.
> 1. Allow me to step through the code execution paths that have been modified in the pull request, based on the tests that have been modified.
Not sure if I fully grasp this! We tried to kind of do this in previous iterations (show call graphs all at once) and it gets messy very fast. Could you elaborate on this point in particular?
Sure - imagine my PR adds one new test which test one new function.
Starting from the test, allow me to step through the program execution, just like a debugger, to observe variables, surrounding code, and the complete file.
If you read only the covered lines of code in a linear way, you'd miss the refactoring opportunities because you aren't looking at the rest of the file.
We need some goats to eat all the fuel while it's still growing. Herbivores will also trample dead plants to the ground so grass can grow. Apparently there's too much work for the herders, based on articles published after the last round of fires.
Stillbourne, you seem to have a lot of trust in science funded by chemical companies. Remember how tobacco companies lied about the health impact of cigarettes?
I know right, it almost like there are no studies conducted by the NIH, the EPA, the FDA, all major Universities including Yale, Harvard, Stanford or any other independent group such as NIEHS. NOPE, ALL pesticide and herbicide research on toxicological properties of chemicals is only ever conducted by BIGAG. You know, just like all of those vaccine studies that show efficacy and safety are only ever conducted by BIGPHARMA. Nope, if you support science, skeptical inquiry and chemicals other than those that occur in nature you must be a shill.
It is cheaper to raise them this way because you don’t need to buy corn feed.
The cows digest grass well. They do not digest corn well, which means corn fed cows produce methane and get sick, and don’t build the soil (sequestering carbon).
Definitely worth watching some YouTube videos and reading about it, it’s pretty fun and interesting.
The problem with mob grazing (and really any kind of similar system) is that you cannot support nearly as many animals per sq ft. in comparison to more industrialized farming.
Salatin's solution is to shift a major portion of the work force/economy into making sustainable food. It sounds amazing from a utopian standpoint but is a total fantasy.
Mob grazing does not need more work, and it reportedly needs no fertilizer and less land, and it was noticed years ago - this is how it is clearly fantasy at this stage. The strategy would have transformed existing beef and dairy economics within years of discovery.
1. It'd save a lot of time if one could just click a Markdown PR description and start editing it, without entering edit mode first.
2. Thanks to the following prompt, I barely write PR descriptions these days.
> Run `gh pr view` then `gh pr edit` to fill out the PR description. Use my words verbatim as much as possible. Be brief. Use tasteful markdown formatting.