The Programming Tools
When possible, I want to choose tools that are available on Mac, Windows, and Linux. Right now, what I have seems a little clunky with the number of windows I have to keep open: a browser, a terminal window, and an editor. This seems like a step back from using an Integrated Development Environment (IDE), but I’m thinking that I will find out ways to be more efficient after I use these for a while.
Source File Editing
Terminal / Command Line Interface
The build tools are all on the command line, mostly using grunt to compile and test. MacOS has a perfectly fine terminal built-in, but I also picked up Cathode 2 because it’s just sexy looking.
While I have been using Mercurial for most of my web projects, I probably can’t avoid Git any longer. I had chosen Mercurial originally because it seemed slightly easier to understand, but I have since gotten a quick lesson in using Git with “pull-requests” and see it now as a better option. Plus, Git is already installed as part of the installed tool chain.
I’m using Atlassian’s SourceTree program to manage my web projects, but I am going to use Git from the command line to get into the habit of its use rather than rely on a GUI. At least for now.
After looking through a few “best of” articles like this one comparing Mac programmer editors, I’ve come to the conclusion that I need to live with the tools I have for a bit before I can make a more informed decision. I don’t like having a bunch of windows open, but I haven’t really experienced the workflow in a way to have an informed opinion about what’s good and bad. Time to write some fancy code and see!