Explore >> Select a destination
|
You are here 
|
nalanj.dev | ||
| | | | |
javier.io
|
|
| | | | | youtube videos from terminal | |
| | | | |
arnorhs.dev
|
|
| | | | | We use git as our versioning tool at work and I've gradually been learning a few tricks on how to speed up my development time and time spent managing my repo. When jumping between branches, continuing your work from where you stopped last time, etc., you very often open the same files as you were editing in a previous commit. This may not be a problem if you use something like Command-T for vim or rely on the file browsing in TextMate, but often it might just be quicker to open all the files from a part... | |
| | | | |
bitsofco.de
|
|
| | | | | Articles on frontend development and more. | |
| | | | |
ryanharter.com
|
|
| | | This is the second post in my Start to Finish series. You can check out my first post introducing the series and my tools here. What is SCM? SCM, or source code management, is a system that helps developers manage the source code for their projects. They have been around forever, things like CVS, Subversion (SVN) and now Git are the popular ones. SCMs allow you to version your source code, which is why they are also called Version Control Systems. | ||
