I finished that book yesterday. I had exactly the same reaction.

Hehe. I kinda love this though :P

Also gclid and dclid. Not that I think this is a great idea.

:P

also missing google analytics cross-domain parameter _ga=xxxx

I agree with everything in this post. I rarely use my laptop as a laptop.

I stick it on my stand and plug in my Vortex Race3 and wait for Apple to make a laptop that doesn't suck.

Yep. I have been working on mapping the Patrick O'Brian age of sail novels for the last 11 years.

http://www.cannonade.net

They're good dogs.

He has dabbled with the Rift:

http://pegwars.blogspot.com.au/2013/09/oculus-rift-integrati...

Not sure if he has ever had plans to sell the game. I think it is mostly a fun (and epic) project to work on.

> Not sure if he has ever had plans to sell the game. I think it is mostly a fun (and epic) project to work on.

Which is perfectly fine! I was simply using money as an indicator of how polished and impressive it looks. Many of my favorite games have been free (roguelikes), and with impressive communities.

Mostly a fun side project but after my current gig, which hopefully will last no more than 4 years, I hope to kickstart or steam greenlight it in order to buy some artists and then release the game :)

http://www.goCatch.com | Sydney, Australia | Full Time Senior Software Engineer | ONSITE

We will be able to help with relocating a successful candidate. We are a small team who prize themselves on writing quality, readable, maintainable code, and are looking for like-minded individuals.

Requirements: - Clojure (or a Scheme or Common Lisp), Willingness to work closely with collaborators (including occasional pair programming). Cloud hosted systems; deployment on AWS.

Nice to have: - Knowledge of the Clojure ecosystem. RabbitMQ (or similar message broker). SCALA. REST architecture. iOS or Android Development.

If you are interested, please get in touch with tom@goCatch.com.

It's a false premise that App Store approval = 6 month deployment cycle. Sure you can move faster on the web, but not that much faster.

Considering you have to go through the app store approval process every time you push an update out (so sitting in queue for a week even for bug fixes), building for web or android first gives you much more agility.

Maybe not unedited, but definitely commentary would be cool :)