Today I was working on integrating product recommendations for emails. The provider of the recommendations engine requires submission of HTML markup. This markup then gets rendered as a dynamic image by their platform. I needed a way to test this in a realistic way. Loading the markup in the browser wasn't going to work.
Someone asked me about a year ago what skills I felt made for good leadership. They themselves were unable to put into words what I displayed that made them feel I had the qualities of a good leader. I've been pondering my response to them for some time.
External and even internal script tags can slow down page loading. The quickest way to alleviate that problem is by making them load after all rendering has taken place. It is important to note that scripts that are loaded asynchronously and that modify the DOM after the DOM has finished loading can cause "render thrashing" where the browser renders, and re-renders parts of the page due to DOM manipulations.
I recently used Migration Assistant to transfer data from my old Mac Book Pro to my new iMac 27". (sooo many pixels!) While doing so it dropped my profile into a different home directory than I had on my previous machine. Needless to say that caused a whole slew of problems. So I followed the instructions in Apple's support article on How to change your account name or home directory name.
The output of
which -a ruby ends up being a path per line for every 'ruby' executable found within the user's PATH. This is an excellent type of output to pipe into another command—or series of them.