Noel Rappin Writes Here

self promotion

Hey, I have a blog

Rails Test Prescriptions, self promotionNoel RappinComment

Making me happy

One of the things I want to do in 2015 is write more. This, like all New Year's type resolutions, is invariably doomed, but we'll take it as it comes. I also want to write more about things that aren't programming, because, well, there are a lot of things that aren't programming but are still interesting to write about.

Combining these ideas, I'm going to try (and probably fail) to do a weeklyish "What's making me happy this week" blog post based loosely on the similar feature at the end of the NPR Pop Culture Happy Hour Podcast. That’s, of course, not this post. But the first one is coming.

But first, a word from our sponsor

It's been a while since I did a flat-out update post. So here is one.

The book, by which I mean Rails 4 Test Prescriptions is out. In print, in an actual physical object that has been read by stuffed monkeys across this great planet of ours. And also a few people.

Couple things:

The book is, of course, available from Pragmatic. You can also get it from Amazon. And, unlike the previous version, you can buy the Kindle edition directly from Amazon, if, for some reason that's the only ebook version you want.

As part of what might, if you squinted at it hard enough, be called a marketing push, I was a guest on both the Ruby Rogues and Code Newbie podcasts. Happily enough, I repeat myself almost zero times between the two of them because the discussions went off in completely different directions. Also, the Code Newbie podcast is worth listening to even if you aren't a Code Newbie, and Saron is amazingly organized and putting together something really neat.

I also was lucky enough to be a guest chef for two episodes of Ruby Tapas. This isn't really part of any marketing push except coincidentally. Avdi was looking for a number of guests to help with his schedule as his family was gaining a new baby. They were fun to do, and I'm thinking about ways to distribute other screencasts if I can find the time to do some.

Oh, and according to the PragPub magazine, Rails 4 Test Prescriptions was the top selling book at Pragmatic in December, which I am putting here because someday I'll read this and it will make me happy. I will say a) this is a little bit less impressive than you might think, since Pragmatic only put out a couple of new titles in December, b) it's probably less books than you think, and c) I'm still a little too happy about this -- the first version of the book never got higher than 4th, and I wasn't really expecting any better this time around.

The relative sales between the two versions are actually kind of interesting. The comparison dates aren't quite exact (version one went on sale as a beta in April, and I think they started taking orders at the end of the following February, version two hit beta this June and shipped in December).

So, we're talking about April-Dec 2009 for the first book and June-Dec 2014 for the second. Although this is an extra couple of months for the first book, some of the first book's biggest moths were Feb/Mar 2010 and aren't counted here. So it's not really an apples to apples comparison.

Ebook sales for the two versions are almost identical (the first book is a hair higher). The physical book sales are a lot less this time around -- even though all the physical book sales being counted for the first book would have been pre-orders. For the first version, Ebooks outsold physical books about 6 to 1, this time around it's more like 17 to 1. (Though I expect that ratio to drop back down once Amazon and other bookstore sales get counted). Overall, sales are about 90% ish of the first version through December.

Coming up

I have a few conference and meetup talks coming up.

I'll be doing a talk entitled "What we talk about when we talk about testing" at both a Chicago Ruby North Shore meetup on February 7, and then again at Groupon Geekfest March 3.

I'll be at Ancient City Ruby March 25-27, doing two things. On March 25, I'll be doing what is, I think, iteration 4 of the "How to do Fancy Object Things in Rails Without Losing Your Mind" full-day work shop (not it's actual title). And then sometime during the conference itself I'll be giving a talk on estimation, and Trust-Driven development. Really looking forward to this one.

Oh, and the books

There are two things that you might have given me money for and still be expecting some content. Let's take them one at a time.

Trust-Driven Development

Status: was about 30-40 percent done when I abandoned it to start Rails 4 Test Prescriptions.

I've picked this back up. I was really hoping this would be done by the time Ancient City Ruby comes around. I think it's got a fair shot of getting there.

In retrospect, I may have overestimated the audience for people reading my rants about projects. However, I really like writing it, and I think it's got good advice. So you should read it.

Ember

Status: First edition finished. I promised I'd take another swing once HTMLBars came in and Ember Data hit 1.0, which I was hoping would be roughly August 2014.

Well, HTMLBars will officially be in Ember as of a week or two from now, Ember Data may well actually hit 1.0 some day, plus we've got a whole new suite of tools in Ember CLI, which also now brings in EC6 language features.

My probably ambitious goal is a redo of the whole book, top to bottom, using Ember CLI, EC6, and other cool new stuff to build an application. So it'll be almost 100% new, and probably under the more direct title Master Space and Time With Ember.

Existing owners will get it for free. I'm not sure what will happen to the other MSTWJS books or how I might bundle them.

I'm also not sure when I will start, though it probably will wait until Trust-Driven Dev finishes.

Monday Morning Me: Sep 16, 2003

self promotionNoel RappinComment

Here’s what’s going on.

WindyCityRails

Had another great time at WindyCityRails. I enjoyed the talks, and it was great to meet new people/see people I don’t see enough in person. As usual, Ray and the WCR team had the logistics of the event down (even the WiFi was pretty fast for a conference.) The venue is really nice, if maybe not perfectly arranged for the kinds of talks being given.

I very much loved Aaron Kalin waling around in his stormtrooper suit on day two, in response to a bet from Table XI to donate $50 to Facing Disability for each hour that Aaron wore it. You can see some of the results: here, here, here, here, and here.

As for my own talk (slides, video coming eventually, I assume), I was happy with it, but hope I get to give it again, because I feel like I was still discovering some ideas about how I was approaching the topic. For example, the framing idea of how practices get to become your new normal practice really only fully formed the night before, but I’m really interested in exploring it.

Also, as much as I really wanted to tell the “little web engine” story, I don’t think it’s as funny to anybody else as it is to me. (Right now, I have a much better time getting jokes to land in workshops then in formal talks, which is frustrating.)

Master Space and Time

The update is that today is the last day of the current pricing scheme. Tomorrow, the prices go up to $10 per book, or $25 for the bundle. So, if you want to get the cheaper price in under the wire, go to /mstwjs.

Rails Test Prescriptions

I’m currently in the process of auditing the existing book to determine all the things I wrote that still make sense, and all the things I wrote that don’t.

I’d like the next version to hit the “good tests equal good design” button a lot harder, and I’m trying to see how to structure the book to get that to work.

I’m also trying to figure out the minitest/RSpec balance. I’ll describe the basics of both, but I think I need to pick one as the primary focus of the code samples.

In favor of minitest: it’s the Rails default, it’s arguably simpler (or at least, it’s simpler internally), and the existing RTP code examples are compatible.

In favor of RSpec: it probably still has a larger share of Rails developers, it’s more expressive, and it has a more interesting ecosystem.

Anybody with an argument for focusing on one or the other that goes beyond “I use that one” is welcome to chime in.

Trust-Driven Development

I’m Doing an edit/finish some half-finished sections. I’d like to get a 30-some-odd page initial release out sometime in the next 10 days. Again, if you want to get it before the price goes up, it’s available at /trdd.

Status Update

Self Publishing, mstjs, self promotionNoel RappinComment

It’s been well over a month since the last official update to Master Space and Time with JavaScript, and since I was hoping to get updates out more-or-less weekly, it’s probably a good idea to check in and let you know what’s going on. (Could be worse, though, I’m still hoping to post my top 10 books I read list. From 2011.)

All of the MSTWJS customers out there have been either very patient in waiting for the next update, or you are completely disengaged. Personally, I’m choosing to assume patient.

I am continuing to work on the book, it’s just slowed down quite a bit. The next update will most likely be sometime after RailsConf — ideally sometime in the week or so following. So by, say, May 10th. I post this date publicly to increase the chance that I’ll actually hit it.

There are a few reasons why the book’s progress has slowed.

To some extent, it’s a deliberate slowdown so I don’t have to rewrite the thing a dozen times. Yes, Ember is in an API freeze, but they are still adding new things that preserve compatibility, and Ember-data is decidedly not in an API freeze. Just in the last week or so, integration testing tools are starting to emerge — see this discussion for details. Honestly, the fact that I had to throw my hands up over integration testing in the last update was very disappointing, and I’d very much like to get that working in the example.

There’s also been some fumbling about what I want to cover in the rest of the book and how I want to get there. This one, I think I’m getting a handle on.

I also got busy. For example, I’ve been starting this weekly sort-of-screecast series for Table XI called XI to eye. I’ve never done anything like it, but I’m pleased with how this is going. There are five so far, you can see them all at http://www.tablexi.com/blog/category/xi-to-eye. Please do check them out.

I’m also doing two sessions at RailsConf — a normal session comparing rich client MVC with the 37Signals Basecamp approach and an intro track session on testing complex systems. More on those next week, but I’m excited for both of them.

There’s also been some laziness, and some lack of momentum caused by the combination of the previous points.

Still, hoping that this will move a little more rapidly in May — we’re now coming on the two-year anniversary of me starting the project (though I suppose I’d be done if I hadn’t decided to pick up Ember as a topic), and I’m certainly ready to move on. (I have some idea what my upcoming writing projects will be, just not sure which one I want to tackle next.

Thanks for your patience, if you are enjoying the book more will be coming — there will also be another errata catch up on the first three books. Please do help spread the word, or maybe buy it yourself.

State of My Stuff, January, 2013

Self Publishing, self promotionNoel RappinComment

The state of the Noel Rappin publishing — I can use the word “empire”, right?

MSTWJS 3: Backbone

Master Space and Time With JavaScript, Book 3: Backbone is draft complete as of today’s release except for a page or so of summary at the end, which I will probably wait to write until the Ember chapter is complete.

The next release will be an edit pass, to clean up typos and bad sentences, smooth over the explanation, fix errata and generally polish stuff. I haven’t done any of this on the book yet, so it’s possible there will be some bigish changes depending on what I think is going on.

Any further releases will be errata and cleanup based.

MSTWJS 4: Ember

I’m starting to get actual questions about the Ember version.

In the wake of the Ember team getting their newest router API into master, and also updating a lot of their documentation, I’ve broken ground on this one and am moving forward.

I will release this in a pretty early state, I imagine, and continue with the weekly updates until it’s through, which I expect will be on the order of ten weeks. Ish.

I have two criteria for the initial release. The first is that I need the example in the book to go far enough to display some things on the screen and show off some event and property processing. Secondly, I have a couple of people who have volunteered to sanity check the book, and I’d like at least one of them to sign off on it before anything insane I write is exposed to the general public. So, optimistically, Jan 14, but maybe a week or two after.

MSTWJS 1 and 2

I do have some standing errata that have been reporting. I would expect not to see an actual update until after the Ember book is on sale, not least because then the update email can be used to tell all the free book one customers that the Ember book exists.

Next Projects

So, I do know what my next project is going to be, I’m planning on self publishing it. It’ll be Ruby and testing based, but I don’t plan to start on it until after the Ember book is out in the wild. I came up with an outline while I was waiting for the Ember team, but now that I they look solid, I want to get that out first.

How's it Going? MSTWJS Edition

Self Publishing, mstjs, self promotionNoel RappinComment

And now for a more inside-baseball post about how the self-publishing aspects of Master Space and Time With JavaScript are going. Did you know you can buy it?

Short answer: Pretty well, though I could always have done better. Still unclear how this will work over the long haul.

At this point, the book has been on sale for 10 days, plus the pre-sale to people who were on the mailing list. It’s clear that the initial burst of traffic from incoming links is slowing down, and I’m now entering the longer struggle to get people interested — not completely sure how to do that.

Anyway, a few disconnected points about the process so far

One of the big things I miss about a larger publisher is the marketing reach. That said, there’s something really nice about how people feel a little bit of ownership concerning self-published projects that they like. I’ve gotten a couple of very nice copy-edit runs, for example.

I’ve generally been lucky in reviews (notable exception: the two-star review of RTP on Amazon that I check out whenever my Impostor’s Syndrome feels insufficiently pronounced…), and so far, the people who have commented on the books where I can see them have been positive.

I can be a little transparent with numbers. As I type this, traffic is still about double the level that I had generated in the past on days that I posted to the blog, and much, much higher than the ambient level of traffic when I hadn’t been posting.

Over the course of the ten days, about one in six people that have hit the landing page at /mstwjs and aliases convert to either the free version or one of the paid versions. Low day was 12%, high day was just under 23%. There doesn’t seem to be a consistent trend between traffic and conversion rate.

So that’s about one in six doing anything, of those that do choose, about one in six or so actually bite on one of the paid versions. So that’s a paid conversion rate in the 2 - 3% range. That rate seems to be slightly negatively correlated with traffic, which is actually in line with what I would expect.

As for the pricing strategy, which I thought was so clever… So far, there have only been a very few people buying book 2 at the $7 level — most purchases have been of the whole book at $15. I’m not planning on changing the pricing (beyond my already-stated plan to raise the $15 when Book 3 gets near-final). I want to see how this looks when there are more individual books for sale. But there’s a good chance this means that I outsmarted myself, and probably could have priced a little higher.

So far, as best as I can tell, under 3% of people who originally downloaded the free version came back to upgrade. That seems very low, but it might be higher — the way I’m counting this, if somebody gave me a bogus email for their freebie, I wouldn’t track it as an upgrade. Also, I assume this number goes up a touch as people read the book and as upgrade reminders go out. Still, as it stands, it’s not a great data point for the “give away free stuff to increase sales” school of internet marketing.

Over the course of the ten days, the number one referrer, by far, was Peter Cooper’s JavaScript Weekly email newsletter. It’s the biggest by about a factor of three over the next highest measurable referrer. Next up was Twitter, and I think the highest link out of those came from JavaScript daily, and I think the second one was from my feed. It’s really hard to track those for sure, though. Third was Google Reader, though I think that was mostly blog posts and not links to the landing page. Fourth was Reddit — my post there didn’t get much traffic, and fifth was the Ruby5 podcast and show notes. Rounding out the referrals so far is Mike Gunderloy’s Fresh Cup links, and then we also get some noise with internal referrals and things like Pocket, and the Ruby Rogues link, which just came out.

Another point of comparison is that MSTWJS sales are about 150% + of RTP sales over the first ten days. That’s less impressive than it sounds, I really struggled to get traction with RTP after the initial burst. (That’s the paid number for MSTWJS, and it includes the pre-sale to the list). RTP had a free section as well, and I don’t have any stats on how often that was downloaded, but since it was just a link and not a shopping cart, I think it was pretty high.

That’s where we are — I hope that those of you that bought or downloaded the book are enjoying it, and if you are hoping to do your own self-publishing project, I hope this information is helpful.

Oh, and the book is still on sale.

The Origin of Master Space and Time With JavaScript

Self Publishing, mstjs, self promotionNoel RappinComment

I have a new book, Master Space and Time With JavaSript. You can buy it.

Here’s the secret origin.

This all started over a year ago. Rails Test Prescriptions had been complete for a few months, and I was getting a little antsy to take on a new project.

But what? I wanted it to be a project where I would learn something, and I wanted it to be something where I had a particular perspective to offer.

A couple of recent experiences pushed me toward view-level coding in general, and JavaScript in particular. About then, for the first time in a while, I worked on a project that had a reasonably serious JavaScript front-end on a team small enough that I was contributing some of the JavaScript.

It quickly became clear to me that JavaScript coding had changed dramatically, not just from my first pass at it (warning clients away from it circa 2000), or my second pass (avoiding it with RJS circa 2008). The tools were better, the idioms had changed, and the expectation was that future web applications would need to handle this stuff very well.

I was also working with a new Obtiva apprentice, who wanted to build a very JavaScript-heavy site, but didn’t really know much JavaScript. In searching for books to point him to, it seemed to me like there was an underserved part of the market, not for total beginners, not a description of a particular library, not a pronouncement from On High about The Right Way To Do Things, but a practical guide to writing and testing modern JavaScript to do cool stuff.

Which is what I set about to write. My original proposal for this book may well be one of the best pages of text I’ve ever written.

And yadda, yadda, yadda, here we are.

I knew I wanted the book to build up on a single web application example — I’ve always liked that style, even though it can be a pain in the neck to structure. I also knew that I wanted to have a lot of testing in the book. Not only is writing about testing in JavaScript something that seems pretty needed, it also felt like a perspective where I actually might have useful things to say. Plus, I had used the largely-test-first style of writing before (in the Wrox book), which I’m sure was appreciated by all three of the people who bought it. I thought I could do it again.

The idea of taking an application with no JavaScript and adding JavaScript features seemed like a good hook. I’d used the Time Travel Adventures travel agency before (for my testing legacy code workshop), and the idea of a time-traveling client who was confused about what modern web sites needed seemed like a suitably silly hook. (In the first draft, the client was named Emmett Brown, but I was guided away from using that name directly, hence the client becomes the mysterious Doctor What.)

And I was off…

Here’s what you get in the books.

Book 1 is largely concerned with a particular simple-seeming request: add a show/hide toggle link to each trip on the home page. Although this is simple, it actually winds up touching a fair amount of jQuery — using selectors to find elements, binding events, and manipulating element pieces.

We build up this toggle thing in a few stages. First is a quick pass writing a simple version of the toggle functionality test-first. The goal here is a sense of what a test-driven process looks like in JavaScript, plus the basics of how Jasmine and jQuery can be brought to bear to write the feature. It’s basically the book equivalent of “fast to green”. We solve the problem with the understanding that we’ll clean up the details later.

Then we go back with two more chapters that go more in-depth on first Jasmine, then jQuery. In these chapters, we don’t add new features as much as describe the library features that supported what we did and explore related functionality.

The final chapter of Part 1 covers the JavaScript object model and why it is confusing if you come to JavaScript from a more traditional Object-Oriented language. By the end of it, we’ve used the module pattern to build the most over-designed show/hide toggle ever. I’ve had some experience doing workshops based on the material in this chapter, and it seems like even people who have been doing JavaScript for a while get something new out of it.

And that’s Book 1. It’s available for the low, low price of zero dollars and zero cents. Worth every penny.

Book 2 is mostly about apply and extend. The first chapter is about building up an widget that combines an autocomplete text input with a list of currently chosen items. Test-first, of course. The we throw some Ajax in the mix, extending our already gold-plated toggler with the ability to get data from a server. This also gives us an excuse to talk about Jasmine spies. Finally, we build up a rating widget, with the clickable stars and a histogram and stuff, which lets us talk about JSON and Mustache. There’s also a small, slightly out of date bit on the Chrome developer tools. I’ll catch up on that at some point.

Book 2 is a mere $7.

Or you can get Books 1 & 2, Plus books 3 & 4 when they come out for $15. That $15 is a temporary price, and will go up when Book 3 gets closer to completion.

Book 3 is going to be about Backbone. I know the structure of most of it — first, we’ll recreate the front page using a Backbone structure. Next, we’ll build a buy page that allows you to make several calculations about differing trip purchase options on the client. Not sure about the last part, it will definitely include communicating back to the server, probably something else.

Book 3 is going to start appearing on the site in a couple of weeks, and will probably be draft complete by the end of September.

Book 4 will cover Ember.js. I’m not sure yet what we’ll build, though I want it to be a new part of the site, and not a recreation of the same things we do in Backbone. I’m hoping that Book 4 will be out by the end of 2012.

Oh — the title. I had a list of two word titles that were like POWERWORD JavaScript, but all of them were either taken, sounded ridiculously stentorian to me, or both. The original proposal titles were “Getting Things Done in JavaScript”, which nobody liked, or “JavaScript for People who Hate JavaScript”, which nobody liked (see the pattern).

I had Master Space and Time with JavaScript on my list as kind of a joke — a reference to the Time Travel conceit in the book. Plus I liked that it sounded like a pulp adventure novel, and would lend itself to a cover easily. I know it’s not the, like, SEO favorite title, but I’m hoping that people won’t forget it once they hear it.

The cover, by the way, is my own design, and I like it considerably more than many of the other things I’ve designed. (I’m also pretty happy with the PDF layout…) I think the cover particularly works well at thumbnail size, so you can see the difference between the individual books easily.

That’s the story. Hope you like it. Buy it!, or tell all your friends (Twitter hashtag #mstwjs).

Thanks.

Upcoming Me

self promotionNoel RappinComment

Updates, schedules, things, and stuff.

Scottish Ruby

The Scottish Ruby conference is having a charity workshop June 28, and I’m presenting my “Advanced Rails Design” workshop. This is the extended dance mix version of the workshop I did at Mountain West Ruby earlier this year. I thought it went really well (so did the attendees, I’m sure), and I’m very excited about this one. Details at http://scottishrubyconference.com/charity/ — you don’t need to be attending Scottish Ruby, but you do need to register in advance.

There are three workshops that day — a UX workshop that has sold out. A Dave Thomas advance Ruby workshop that hasn’t, and mine. Let’s just say there are more tickets available right now for mine than I’d like, and I hope that if you are in the neighborhood, you’ll stop by. It’ll be worth it.

Windy City Rails

Much closer to home, I’m speaking at Windy City Rails this year. According to their schedule, my talk will be “Let’s Make Testing Fun Again”. This conference is always great, the venue this year looks outstanding, and the speaker list is — myself excluded — top-notch. Hope to see you there.

Ignite Rails

My IgniteRailsConf talk: Manage Your Development Environment / Never Burn Another Burger by Noel Rappin is now available on line at http://www.youtube.com/watch?v=VLCLBdFsSOE. I don’t think my other RailsConf thing is up yet, but I’m sure I’ll let you know.

Master Space and Time With JavaScript

It’s near schedule. I think that converting all the text for the first two parts of the book will be done next week. Leaving me with a) a serious edit b) cover and incidental design, c) cleanup for epub and mobi, and d) product sale logistics. Still hoping that’ll go out in early July. If you’ve signed up at /mstjs-form, you’ll probably get an early look/chance to help me work the kinks out.

And Hey,

You can still buy Rails Test Prescriptions. Much of it is still up-to-date…

Self-assessment

JavaScript, Me, self promotionNoel RappinComment

Here’s what I’ve got.

2 chapters introducing jQuery and Jasmine via a walkthrough of a simple piece of JavaScript functionality.

1 need to convert all my text from its current proprietary format to something more Markdown based.

1 genuinely silly conceit tying together the application that gets built in the book. And I mean that in the best way. It should be silly, there’s no reason not to be bold. There is even a twist ending. I think.

1 slightly dusty self-publishing tool chain that converts a directory of markdown files into HTML, with syntax colored code. It’s possible that there’s a better library for some of the features these days.

1 chapter on converting that simple piece of jQuery into various patterns of JavaScript object. I quite like this one, actually.

1 website, which is currently hosted by WordPress – at one point, I had to abandon the railsrx.com site that actually sold stuff, and WordPress was easy. I think I’ll need to upgrade that a bit.

1 Intro chapter covering JavaScript basics and the Chrome developer tools. Not sure if this is at the right level for the audience I expect.

1 Prince XML license for converting said HTML files into PDF. No idea if that’s still the best tool for the job. Or even if my license is current.

1 chapter on building a marginally complex auto complete widget in jQuery and Jasmine. I like this example.

1 copy of most of the book’s JavaScript code in CoffeeScript. Not sure when I thought this was the right idea for the book, beyond an excuse to use CoffeeScript.

1 chapter on jQuery and Ajax.

0 toolchains for generating epub and mobi files. I know I can find this.

1 case of impostor’s syndrome, not helped by rereading the harsh review of Rails Test Prescriptions on Amazon. That was dumb, why would I do that?

1 chapter on using JSON. As far as I can remember, this chapter never went to edit.

3 people who mentioned on Twitter that they’d buy a self-published book. Don’t worry, I won’t hold you to it.

1 plan for writing 2 or three chapters on Backbone.js

5 people who reviewed the last version who I feel should get free copies when this comes out. It’s not their fault.

4 viewings of Ze Frank’s “Invocation for Beginnings”

So. Ready to go. Watch this space.

A Brief Announcement About A Book

JavaScript, Me, self promotionNoel RappinComment

So… The JavaScript book that I had contracted to do with Pragmatic will no longer be published by them.

I need to be careful as I write about this. I don’t want to be defensive – I’m proud of the work I did, and I like the book I was working on. But I don’t want to be negative either. Everybody that I worked with at Pragmatic was generous with their time and sincere in their enthusiasm for the project. Sometimes it doesn’t work out, despite the best intentions.

I haven’t spoken about this project publicly in a while because it was so up in the air. And also because I’m not sure what to say about it without sounding whiny or mean. And also because I was afraid of jinxing things, which is obviously less of an issue now.

Since November, the book has been in review and I’ve gone through a few cycles with Pragmatic trying to get things just right. The issues had more to do with the structure and presentation of the material then of the content or writing itself. I’m not completely sure what happened, but I think it’s fair to say that the book I was writing did not match the book they wanted in some way or another.

Anyway, that’s all water under the bridge. I have full rights to the text I’ve already produced. Self-publishing is clearly an option, though the phrase “sunk costs” keeps echoing in my head. It’s hard to resist the irony of starting with a Pragmatic contract and moving to self-publishing after having done it the other way around with Rails Test Prescriptions. I’m hoping to blog more – in addition to being a time sink, not being able to write about this book was kind of getting in my head about any blogging.

Thanks for listening, and watch this space for further announcements. I was excited about this project, and while this is disappointing, I’ll be excited about it again in a few days. Thanks to the people I worked with at Pragmatic for the shot, and thanks to all the people who have been supportive of this project.

June 7, 2010: Lot of Conferences Week Begins

Authentication, Mac, Rails 3, i18n, self promotionNoel RappinComment
Today is the RailsConf tutorial day, with the conference proper starting tomorrow. I was less disappointed than I thought I would be when my talks were not accepted, but I'm more disappointed than I thought I would be not to be going. Have fun, everybody.

On the other side of the country, today is the Apple WWDC keynote, which I'm sure I'll join the rest of the internet in obsessing over.

Book Status



Over the weekend, worked on the style chapter of the book, largely trying to incorporate the ideas from the Chicago Ruby talk, and also combining some of the short chapters. Need to find out if I have a page limit.

Lots Of Links



Plasma Rails is a new Rails RDoc presentation site that claims to update Rails 3 docs nightly. It's got a very TextMate-ish dark theme.

The Everyday Rails site has a quick rundown of three Rails Authentication methods, Restful Authentication, Authlogic, and Devise. Devise looks nice, and I'm considering moving the Rails Test Prescription examples to it since it seems to be an easier setup than Authlogic and also Rails 3 compatible.

Not to be outdone, I Suck At Ruby mentions a feature of the the Ruby TextMate bundle that validates Ruby code on save.

Josh Owens at RailsFreak has a suitably quick post with thoughts on how to do a quick launch of a web application.

DHH himself has released Tolk, which is a Rails engine providing a web interface to support translators entering text and converting it to the Rails YAML locale files. I think this was extracted from the recent Basecamp multiple language release, looks like it'd be useful.

Ars Technica named the winners of their design awards. I concur on two of the three apps that I use (Tweetie -- please finish the Mac version 2.0 -- and Dropbox), I like 1Password, but wouldn't consider the app itself to have a particularly great design. Don't use the others, although Soulver is pretty cool.

Finally, In Self Promotion



This has been around for a while, I think, but it just passed back in front of my eyes. Antonio Cangiano has a list of recommended Ruby books, and a separate list of Rails books.

Somewhat flattered to have my Wrox book, Professional Ruby on Rails, be included. There are parts of that book that I think are really great. And parts of it that were obsolete almost the moment it was printed (for instance the entire chapter on using Subversion with Rails...). Anyway, thanks!