/explore
|
You are here 
|
davidalfonso.es | ||
| | | | |
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 be actively worked against. Specifications are important. If someone wants you to build something, it needs to be specified. Documents # Design and Decision # Should contain: | |
| | | | |
techtldr.com
|
|
| | | | | Here are the steps that I too to merge multiple GitHub repos into one, while preserving all commit history. The process took about 30 minutes for 5 repos. As a result, I feel like my GitHub page is cleaner and code is actually better organized and easier to find. TLDR: Create new repo (or use [...] | |
| | | | |
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: | |
| | | | |
ryanharter.com
|
|
| | | I recently shared how I use Git to automatically track my versions. There's quite a bit more to my git workflow than just tagging versions, though, so I'd like to dive into my git usage just a little more. One of my clients introduced me to a very popular, and useful, git branching strategy commonly called Git-Flow based on Vincent Driessen's branching model. I highly recommend reading his article, it's quite good and describes a very useful branching model. | ||
