Explore >> Select a destination
|
You are here 
|
blog.keikooda.net | ||
| | | | |
jo-m.ch
|
|
| | | | | Software Engineering Principles # Start simple and iterate, you won't get it right the first time anyways Make it fail gracefully There can never be enough logging, debug statements, asserts Measure before you optimize Make it hard to do the wrong thing Ugly hacks keep the world spinning Limitations are as important as features. Magic is bad Hyrums Law is very real and needs to actively worked against if you don't want to deal with it's fallout Specifications are important. If someone wants you to build something, it needs to be specified. Documents # Design and Decision # Should contain: | |
| | | | |
tannerdolby.com
|
|
| | | | | To begin contributing to open-source software, you might want to become familiar with Git. Understanding the workflow of creating your own local copy of a repository and keeping it up to date with the upstream repository is integral to start contributing in public projects. | |
| | | | |
wittchen.io
|
|
| | | | | When you fork GitHub repository, you usually want to have your fork up to date with the original repository. You can update your fork in a few easy steps. Just look at the following example of the Git commands: Add the remote, call it upstream: git remote add upstream https://github.com/whoever/whatever.git Fetch all the branches of that remote into remote-tracking branches, such as upstream/master: git fetch upstream Make sure that you're on your master branch: | |
| | | | |
itwont.work
|
|
| | | in which I complain about blogging. (imported post) | ||
