A year and a half ago and the Mac terminal scared me spitless. I didn’t know how to do anything with it and I didn’t know of anything that I really wanted to do with it. Then I started working with Vagrant, and then Git, and then Grunt, and pretty soon the command line didn’t seem so frightening any more. In fact, once I got down a few basic commands I started helping with server administration and other command liney things at the agency I worked for. Read more
I am neither a command line wiz or a git expert, but learning a few commands in the terminal and learning the basics of Git has changed my workflow forever!
Here is the scenario that I’ve run into more times than I care to count. While working on a new feature for a project you find it necessary to submit a patch that conflicts with the files you are modifying for the new feature. What is the solution? In the past, this meant undoing all the progress on the new feature request so that nothing is accidentally deployed, writing the patch, deploying, and then try to paste in or rewrite all of the work you just undid. This is uncool and very inefficient.
Or how about this: your client requests a new feature that spans several files, but once it is completed decides that the site audience is not ready for it. Now what do you do? There are more features that need to be developed but how do you continue on without trashing the feature that is now on hold?
Let me introduce you to a better way.
PDF Download: Core Function Definitions