Here’s everything I know about git without having to google. It isn’t much. When I first setup git on a new OSX machine, I edit my .bash_profile and add the following lines: export PS1='$(git branch &>/dev/null; if [ $? -eq 0 ]; then \ echo "\[\e[0;32m\][GIT: \[\e[0;31m\]$(basename `pwd`); \[\e[0;33m\]$(git branch | grep ^*|sed s/\*\ //) \ $(echo `git status` | grep "nothing to commit" > /dev/null 2>&1; if [ "$?" -eq "0" ]; then \ echo "\[\e[0;32m\]clean"; else \ echo "\[\e[0;31m\]dirty"; fi)\[\e[0;32m\]] \$ "; else \ echo "\[\e[0;31m\][\w]\[\e[m\] \$ "; fi) \[\e[0m\]' I can’t following everything going on in that bit of bash but I don’t need to and neither do you.
I’m just about done with the Mythical Man Month by Frederick Brooks Jr. The influence of archaic patriarchal norms are present in more than just the title, but it was a good read. I hope to read more books like this where the point is learning how to write/compose/build software projects rather just how to write software. Many of us have proudly looked on the results of various “Hello World” outputs and then wondered…what do I do now?
I have a blog already. Have had it for many years. I really got all jazzed about running my own server and golang blog stuff, but then I decided that the contraption I’d made wasn’t all that fun to work with. I’d think of a post and then think of all the SSH hoops I’d have to jump through to make it live. I’ll give blogger one thing, it sure made it easy to write content.