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.
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.
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.
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?
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.
You're having trouble creating/contributing back because you're not sure what other people need from you (when you find them, it'll be like someone opened your faucet for creativity). Try doing a sales safari※ for an audience you want to help and see what happens.
Find people with expensive problems† and help them solve those problems with your words, a software product, or consulting.
Super interesting article. With a system like this you can also get great metrics for product health / tech debt. If you were also looking at key growth metrics for the apps, you'd be able to see which releases improved them, and give credit (in the cases where it makes sense).
Awesome–it's fast and I like the autocomplete and the auto-npm package download.
I might be hooking graphql/apollo up to some strange data sources like CSVs to help import my data in the right shape, so this and the examples are going to be very handy. Thanks for making this!
Has anyone seen a fuzzer that creates variants based on a test suite with 100% coverage? Hmm... the fuzzer still wouldn't necessarily know how to create the correct invariants. #lazyweb
Check out the papers on Inspiratory Muscle Training (IMT) and bridge swallowing.