Years ago I wrote about Ruby’s English and/or operators and why they are the way they are. I’ve never been completely happy with how I made my case in that article, and more recently I took another whack at it in a RubyTapas episode. However, until now that episode hasn’t been available to the general public. Today that changes; I’ve made the episode freely available and you can watch it right here.
Someone wrote in asking:
you always have ideas… How do you generate ideas to build something?
Which is a great opportunity to pontificate. (I swear, I did not make this question up!)
Let’s get this out of the way: I am the wrong person to ask. I am not an effective “idea guy”. I’m white, male, I was born in the USA, I’m 34 years old, and I’ve been writing software since I was in my teens. If I were any good at ideas, I’d be a millionaire by now.
So you probably shouldn’t listen to a word I say. But I’m going to say it anyway, because there’s nothing quite so much fun as making up answers to the big questions.
The other day I put an app in production with (gasp) no automated tests. I’m careful to say no automated tests, because of course I had been testing it manually throughout the ~12 hours it took me to write the initial version of the app. In lieu of tests, I made sure to log copious amounts of information, which I then collected from my deployed app into Papertrail.
For a single day’s work this was acceptable. But I knew that once I had a version in production, pushing out even the smallest, seemingly benign change would be an extremely dicey proposition without some automated regression tests in place.
TL;DR: New book project, The Rake Field Manual. Today only, buy early access to it at half-price ($12.50) with coupon code HAPPY0X22. Or get any of my other books and videos at half price with code BDAY0X22. Or get your first three months of RubyTapas for the price of one by signing up using this link.
Hi folks! It’s that time of year again. The time of year when I celebrate another revolution around the sun by announcing new projects and putting everything on sale!
Oh, and drinking lots of beer and playing Badminton all afternoon, but sadly our yard isn’t big enough to invite you all over for that part.
The Rake Field Manual
First off! It’s been way too long since I started a new project. I’ve mentioned it once or twice on Twitter, but today I’m officially announcing my new book project, The Rake Field Manual.
Some of you may have seen the video/blog post series I released about advanced Rake. In the past year as I have transitioned my digital bookbinding toolchain over from GNU Make to Rake, I’ve learned a lot about the power and flexibility of the Rake build tool. Of course I had used Rake for many years in conjunction with various Ruby projects. But as it turns out, I had barely scratched the surface of what it is capable of.
So in this book I’m going to share what I’ve learned, and no doubt learn even more along the way. It will be laid out in a “cookbook” style, each short chapter addressing a real-world automation problem with a practical Rake solution. However, I don’t want the book to only be applicable to people who are already familiar with Rake. So I will be structuring the recipes in such a way that if you read it from the beginning, you’ll get a solid Rake tutorial starting with basic principles.
Here’s are some example chapters:
- “Execute a sub-process in a clean environment”
- “Run a series of tasks, continuing even if some fail”
I also believe that Rake is applicable far beyond automating just Ruby project builds. In order to give the book the widest potential audience, I’ll be constraining most examples to use a small subset of Ruby 1.9 features. In addition, in the finished product I’ll include an appendix containing a brief introduction to just enough Ruby to understand the examples in the book.
I’m not announcing a timeline for this book; it’ll be done when it’s done. A lot of that will hinge on the feedback I get from readers. And that’s where you come in.
As a self-publishing author, I don’t get publisher advances to cover the cost of writing a book. Instead, in the past I’ve pre-sold my books while they were in an early state, both to get reader feedback and to fund the writing process.
I’m doing that again with The Rake Field Manual, but this time I’ll be collaborating with early readers more closely than ever before. Early buyers of this book will receive immediate access to the working Github repo where I’m writing it. There, you’ll be able to see the daily changes as I make them, report errata, and file issues requesting coverage of topics that are important to you. More than any other book I’ve written, the direction of this one will be guided by the input of my readers.
Oh yeah, one other thing: I’ve decided to donate 10% of the proceeds from this book to the Weirich Fund, in honor of the man who gave us Rake (and so much besides).
Every year I throw a big sale on my birthday, and this year is no exception. Today only, you can purchase early access to The Rake Field Manual as I write it at half price, only $12.50. Just use coupon code HAPPY0X22 when you check out.
So if you want to support my work, give me a sweet birthday present, support a good cause, help guide the evolution of my new book, and get a great deal, buy it now!
Sale on other products
What about the rest of my books and videos, like Confident Ruby, Exceptional Ruby, and The Making of Cowsays.com? They are all on sale too! For one day, take 50% off of anything in my store using the coupon code: BDAY0X22 (note that this is a different code).
Thanks for all the business over the years! Happy hacking!
I love most aspects of making RubyTapas. I love the research, and the writing. I enjoy doing voice-over. I even like editing the video, at least some of the time. And of course I love the feedback that the videos generate.
What I don’t really enjoy is the actual screen-recording part. I am a terrible typist, and once I’ve scripted an episode and come up with all the sample code I find recording those samples for the screen to be a tedious process.
So, as part of my overall strategy of streamlining my process as much as possible, I’m thinking of delegating the screen recording part of my production pipeline. Read on if you think you might be interested in the job. Here are some notes on the job:
- Probably ~1 hour a week of work, based on how long it takes me.
- Modest compensation. I’m not prepared to pay consultant-level rates, since this isn’t a consulting job; but I’m not expecting work for free. Also (it should go without saying) all the RubyTapas you can eat.
- You should know Ruby, but you don’t need to be an expert. You should at least know how to diagnose the problem if something in a code example doesn’t work the way it was supposed to.
- I don’t care what editor you use, but you should be able to set it up with the same theme, font, etc. that I use on RubyTapas, as well as set up xmpfilter integration in order to show inline results. There may be some other editor setup nitpicks as well.
- You’d be responsible for figuring out how to record your screen, although if you use Linux I have some tools you could try. Importantly, you’d be responsible for coming up with a 16×9 recording without any window decorations. I don’t want to have to crop borders in post.
- You don’t have to be a perfect typist. When I record for RubyTapas I just keep trying until I get a section right, and then edit out all the bad tries in post. That said, the less I have to edit out the better.
- No, you wouldn’t have to synchronize with voice-over. I record VO after the screen-recording, and edit the screen recording to match the pacing of the VO.
- No, I can’t replace this job with a program. While I occasionally automate typing large code samples, a lot of RubyTapas screen recordings involve following the script and moving around the code adding, changing, and evaluating things just as if I were live-coding during a presentation. Scripts aren’t really good for that kind of thing.
- You’d need to have the spare time and inclination to record two ‘casts a week, every week.
- Perks, other than compensation: you get to see RubyTapas scripts early, and you get to yell at me if an example doesn’t make sense.
Interested? Drop me an email. (Warning: I’m mostly heads-down on a new project right now, so I can’t guarantee a timely reply.)