Explore >> Select a destination
|
You are here 
|
osc.garden | ||
| | | | |
sitr.us
|
|
| | | | | This is an excerpt of a post that I wrote for Olio Apps. I am always interested in making my coding process faster and more robust. I want to be confident that my code will work as expected. And I want to spend as little time as possible debugging, testing, and hunting down pieces of code that I forgot to update when I make changes to a project. That is why I am a fan of correct-by-construction methods. Those are methods of constructing programs where the program will not build / compile unless it behave... | |
| | | | |
vlad.website
|
|
| | | | | Sometimes, you want to add some code to test something out, but you definitely want to make sure you don't git commit it. Of course, you should always check the output of git diff before you make a commit (you do, right?), but if you have a lot of changes things can slip through the cracks. A solution is to write a comment containing a string such as "nocheckin": function do_stuff() { printf("hello!!! testing!!!\n"); // nocheckin call_important_thing(); call_other_thing(); } Then, you need to set git up such that it refuses to make a commit if it detects the "nocheckin" string anywhere in your changed files. Here's how to do it. | |
| | | | |
codeinthehole.com
|
|
| | | | | Yet another git tips article | |
| | | | |
www.dzombak.com
|
|
| | | How to set up a Raspberry Pi WiFi access point that the Bambu X1C can stay connected to. | ||
