Explore >> Select a destination
|
You are here 
|
codeinthehole.com | ||
| | | | |
ricardolopes.net
|
|
| | | | | How using existing processes and tools can massively improve documentation and give you debugging superpowers. | |
| | | | |
simonwillison.net
|
|
| | | | | For the last few years I've been trying to center my work around creating what I consider to be the Perfect Commit. This is a single commit that contains all ... | |
| | | | |
popey.com
|
|
| | | | | This is a bit of a dayjob post, but as I maintain a bunch of snaps in my own time, I figured its not out of place here. Typically when I (or indeed any developer) uses snapcraft to build a snap, a snapcraft.yaml drives the process. Ill integrate some kind of CI or build system, and start publishing to the Snap Store. Usually, once created, the yaml doesnt need much in the way of changes. | |
| | | | |
citizen428.net
|
|
| | | I originally wrote this article for Codementor in October 2014. It should have something for everyone, from fairly new git users to experienced developers. 1. Discard local file modifications Sometimes the best way to get a feel for a problem is diving in and playing around with the code. Unfortunately, the changes made in the process sometimes turn out to be less than optimal, in which case reverting the file to its original state can be the fastest and easiest solution: | ||
