Homoiconic is an experiment in publishing code and words about code on a small scale. When I write, I add files to the homoiconic git repository, organized by date. Code is included in the posts and also in the folder with the posts that discuss them, so it's easy to download what you like. You can even download the entire site as an archive!
Homoiconic is really simple: Snippets of code and words about snippets of code. I am avoiding words by themselves. And the words exist to amplify and explain the code, rather than the code existing to illustrate the words. This is the opposite of most of the posts you find on traditional (circa 2004) blogs.
what can I read right now?
Asking me what to read is like asking the chef what's good on the menu. It's all excellent, of course! That being said, I have a few personal favourites:
My series on combinators: Kestrels, The Thrush, Songs of the Cardinal, Quirky Birds and Meta-Syntactic Programming, Aspect-Oriented Programming in Ruby using Combinator Birds, The Enchaining and Obdurate Kestrels, Finding Joy in Combinators, Refactoring Methods with Recursive Combinators, Practical Recursive Combinators, The Hopelessly Egocentric Blog Post, and Wrapping Combinators.
how to subscribe
I tag new posts in del.icio.us. You can subscribe to an RSS feed that will alert you when I manually tag a new post.
If you're into git and like fine-grained updates, you can follow homoiconic here on GitHub or subscribe to commit messages letting you know what I've added or updated in your feed reader. The latter option is likely to be moderate volume, as I like to make edits and corrections as I go.
advocacy-free
My writing used to be heavily philosophical, with lots of advocacy and questioning. I still consider the why of things much more meaningful than the how, but it's time to focus on the how rather than the why. I'm making this little writing place a "no trolling zone." I will try to avoid preaching, and the obvious corollary is that I will also avoid worrying about whether people agree or disagree. Instead, I will try to simply share little pieces of code as it comes to me.
There is no advocacy on here. I frequent a few scuba diving forums. One annoying part of scuba culture is that it can be very polarizing. A bunch of people over here say there is only One True Way to dive, right down to using the exact same equipment as each other. Another bunch of people over there disregard the conventional wisdom and choose to dive solo, attracting criticism from young and old. The forums discovered a long time ago that running flame wars simply drove members away, so they have instituted "no trolling" zones within their boards, places where people can discuss the how of solo diving, or sidemounting, or DIR, without getting into a battle of whether such a thing is a good idea or not.
So, one of the reasons there is no advocacy is that I am hoping to increase the signal-to-noise ratio. That being said, what is noise to one person is music to another, so I have no problem with people using their blogs or community sites like Hacker News to express their feelings.
The other reason there is no advocacy is that I am invoking the "Transit Cop Cop-Out" on myself:
I used to commute into Toronto on the GO train. They have an honour system: you can buy a monthly pass or purchase tickets that you punch yourself before boarding. Roving transit cops check your ticket, and if you didn't punch it you get a $90 fine. Of course, the miscreants have a litany of excuses "I forgot," "I left my pass in my other tuxedo," and so forth.
When you ride every day you get to know the cops well. One of them told me that he had a policy of letting people off Scot-free if they told him a story he hadn't heard before. He told me that the last novel excuse he had heard was from a woman who claimed her nails were too wet to reach into her bag, remove the ticket, and punch it before boarding. Nice. He said he let her off on the grounds of novelty and chutzpah.
I have already said a number of things about abstractions, functional programming, meta-programming, metaprogramming again, brevity, and much more. But I don't want to say any more on subjects like these until I can think of something novel. It may be awhile. In the meantime, share and enjoy.
comments?
At the moment, there are no comments. This is a blog about code, not words. I welcome bug reports and other code-centric feedback by email. I would be delighted to post your snippets and examples. And you know... This is hosted on Github. So you can always fork my unblog, commit an update, and send me a pull request.
That is a lot more work than just submitting a comment. I'm sorry, it's a trade-off. I lose a lot of good feedback, but I also shed myself of a damaging temptation to pander to the crowd. When blogs become "conversations," they also tend to converge on a common group-think. All I can tell you is that if you have a change you want to make or an observation you want to add, go ahead and make it.
credit where credit is due
I originally set up a blog at homoiconic.com, but I spotted David Baldwin's blog, and I knew right away that a blog that is about the how of code ought to be hosted on Github.
I am Reg Braithwaite. You can reach me by email. My first name is reg, and that works fine for sending email to braythwayt.com. I look forward to hearing from you.
My recent work:
- JavaScript Allongé, CoffeeScript Ristretto, and my other books.
- allong.es, practical function combinators and decorators for JavaScript.
- Method Combinators, a CoffeeScript/JavaScript library for writing method decorators, simply and easily.
- jQuery Combinators, what else? A jQuery plugin for writing your own fluent, jQuery-like code.
(Spot a bug or a spelling mistake? This is a Github repo, fork it and send me a pull request!)