Explore >> Select a destination
|
You are here 
|
blog.ltgt.net | ||
| | | | |
chambers.io
|
|
| | | | | So far this week we've talked about what Git is and how to use it. If you're anything like me, you want to know how things work under the hood. When you first learn Git it can seem like magic...but it also seems like something that can easily break. Or something that works by pure demonic byte voodoo. One of the best things Git does is allow you to write code with confidence - fear not about breaking things or losing files. They're always recoverable. To feel confident, it helps to know how things work. | |
| | | | |
betterdev.blog
|
|
| | | | | Git allows us to define aliases, which are our own commands we can use. Here I will show Git aliases that I use in everyday work. With explanation. | |
| | | | |
jvns.ca
|
|
| | | | | git rebase: what can go wrong? | |
| | | | |
blog.martinig.ch
|
|
| | | Architecture is an important asset for good programming and the notion of "pattern" is here to help us apply already trusted code architecture solutions to common problems. Jason McDonald has done a wonderful job to group some of them in a document that should be useful to most software developers. Go to his blog to | ||
