Subject says (most of) it all. I have been working with the command line more lately, partially out of need, largely out of preference, and am starting to collect a bunch of little snippets I have modified from other or created out of whole cloth to get me through my day.
The section has a germinal collection of command line snippets, but the real work lies in the shell scripting cheat sheet and info on creating a command line application with Xcode using Foundation classes.
The issue of whether comments should be on blogs in order for them to be considered blogs has been debated ad nauseum. I am firmly in the camp of not having comments and any reasoning I could muster has already been better explained by Alex Payne 1:
For most sites, though, comments are worse than useless. The anonymity of the Internet inspires hit-and-run attacks, unintelligible ramblings, and truckloads of spam. I believe that comments are evil by default, and the sites above that seem to have healthy communities are blessed flukes.
For me, the spam and hacking that come with allowing comments are really the main reason why I won’t allow them. I enjoy hearing other people’s opinions and have had luck with them in the past. But that was a long time ago. This site (and blog) is customized to be as low maintenance as I can make it without writing an entire framework myself, and the last thing I want to do here is intentionally leave myself open to security problems. So, off with the comments. I can understand (and can hear) the argument that this makes the blog an echo chamber, but I do not agree with that assessment because the quality of comments is usually really crappy and not worth their time to respond. Again, Alex Payne…
I think people do their best writing when they’re forced to defend their ideas on their own turf. It’s one thing to leave a comment on someone else’s blog, but quite another to put your argument in front of your own readers.
This is ultimately simple: My turf, my rules; their turf, their rules; optionally calling and responding across domains. Don’t like the rules, don’t play the game. I don’t like how commenting generally runs on websites, so I won’t allow them since I can avoid them. Done and done.
1 Please also see Daring Fireball who also links to Alex Payne.
There are a number of reasons why I moved away from using RapidWeaver to WordPress.
The primary one is that I need to flex my web skills regularly in such a way that RapidWeaver didn’t allow. I can tweak WordPress at a very low level whereas RapidWeaver keeps things at a very high, GUI level.
I also wanted to resurrect the blog, but RapidWeaver’s built-in blog tool doesn’t really suit my needs. I had to have RapidWeaver installed and running to post, but with WordPress I can manage the site from anywhere. I didn’t want a separate blog site where the designs didn’t match (or rather, I didn’t want to take the time to tweak the designs to match).
None of the above is to say that I don’t like RapidWeaver; I still use RapidWeaver for another ongoing project. I think I just wanted to add something new to the mix, so WordPress since it is new to me.
Oatmeal & Coffee is owned and operated by Philip Regan.
Applescript, Objective-C, and their variants are the main topics found on this site, mainly in the form of my favorite code snippets from my personal wiki. I post them in the hopes that they will help someone out of similar jams I have found myself in after I had found documentation seen elsewhere lacking for whatever reason. Some large and mostly complete projects have been placed on GitHub for others’ use and enjoyment.
Beyond that, there is also my resume and some obligatory legal jargon. Below is a copy of my usual avatar for the online forums I frequent to varying (usually lesser) degrees and elsewhere a picture of a shoe. The shoe is important.
Anyone is welcome to contact me (an email address is casually hidden in the Legal page) with comments and questions.