This post serves a dual purpose: first of all it is to announce (to anyone who hasn’t see the original announcement on my social media accounts) that the book that I’ve been writing for the past year - that has kept me from more actively working with my blog - is finally finished! Second, I’m giving away 3 copies of that very same book! That’s right, I’m holding two giveaways at once: one for Backbone.js Patterns and Best Practices and one for my very one Better Backbone Applications with MarionetteJS!
The title may be a bit misleading. Yes, we’re having a giveaway, but we’re giving away so much more than just a copy of Backbone.js Patterns and Best Practices. I’m also giving away my personal computer, the rest of my physical book collection, all of my passwords for all of my online accounts, half of my income each month for the rest of my life, aaaannnddd you’ll take over as Google’s CEO. I hope that was sufficiently obvious that it was an April Fool’s joke, which of course is obligatory when posting on this day.
It’s been a long time since I’ve actually been on here teaching you something; 9 months since my last actual tutorial and really useful article. Sorry about that! I’m trying to get back on track now though. You should see much more frequent posting and hopefully some very useful posts. Anyway, this tutorial is about a great idea I implemented at work that involved the Adapter and Facade patterns. After using these patterns in this way, I have a much deeper respect for them and I want you to share that repect, so let’s take a look at some awesome ways/reasons to use them!
Every once in a while I get around to reading a book. Books are typically nicer than blog posts because they show the whole picture instead of zeroing in on a tidbit. I was contacted by Packt Publishing to do a review of Backbone.js Patterns and Best Practices. I was excited about this book because it had been a while since I read a good book on Backbone and the title gave the impression that it could be insightful to someone at my experience level with Backbone. So, did it live up to my expectations? Yes and No.
You all know that this site has been relatively inactive for quite a while. Well, I’m here to let you all know that big things are coming in the future. I wish I could say they will be coming soon, but until the book I’ve been writing it finished, I won’t be able to provide much, if any, content here for you all. Coming in early 2014, though, everyone should be happier. Here’s an update on the future of this blog.
Hi everyone! It’s been nearly two months since I’ve written my own post. This is pretty much unacceptable, but I do have some good excuses. Are you willing to listen to them? Or are you just gonna ignore this? Whatever, either way I don’t care too much. I just want to give an update on what is going on around here so you know what to expect and aren’t disappointed when you don’t see anything going on.
TodoMVC is a place where a large number of people have turned in examples of building the exact same Todo web application while using different MV frameworks (and even some non-MV frameworks). Why? So that developers can come explore the code and decide for themselves which libraries and frameworks look best to them. For those wishing to explore the MV* landscape, this is can be a huge help for getting a quick look each framework.