• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Foreword

Foreword

It’s customary for authors to gratefully acknowledge the labors of the many people whose work goes into putting a book together. It’s all true: In addition to the hundreds of hours Jeff and Nat have devoted to this book, editors have poured over the text for any slips in grammar or spelling, technical reviewers have examined every bit of code looking for possible bugs, graphic artists have labored to make concepts visually clear, and the publisher has gone to great efforts to ensure that this book got into your hands.

All of which means nothing to us readers. Our time is scarce and the demands on it are great. This book asks us to devote a little of our money and a good deal more of our time to learn about Fusebox 3’s framework and methodology. Should we? It seems to me that there are three questions we want answered first.

What’s so great about the Fusebox framework? As a web developer, I want a framework that gives me something I couldn’t have easily done myself. Why learn something new if new isn’t better? If you talk to some of the thousands of active Fusebox developers, you’ll hear them speak passionately about how Fusebox makes it easier to develop complex web applications. These Fuseboxers talk about the framework that promotes reuse, making applications easier to maintain and better able to scale. Unlike the glowing reports we hear from many frameworks vying for adoption, these aren’t coming from the pens of highly paid PR professionals. These are letters from the front, so to speak.

What’s so great about the Fusebox methodology? Talk to these same Fuseboxers and they’ll tell you this: The Fusebox Lifecycle Process (FLiP) is a methodology that is proven to work in the diverse environments that Fuseboxers work in. In fact, the methodology grew from the frustrations with project failures, and it represents the best practices that produced successful deployments. Fuseboxers find that FLiP provides a space in which developers of differing skills and levels can work productively together. Ask Fuseboxers what the community of Fusebox developers is like, and they’ll tell you how warmly the community welcomes newcomers and how quickly requests for help receive answers.

What’s so great about this book? It’s rare when the authors of a technical book are not only guides, but also guiding lights in the technology about which they write. Stated simply, Fusebox 3 would not be what it is without the contributions Jeff and Nat have made to it. Their unique perspective on the goals and philosophies behind Fusebox 3, as well as the details that make it work, will help you understand not only how to do things, but why.

Because Nat and Jeff are both full-time developers, they can offer you help using Fusebox amidst the stresses of pressing deadlines and pointy-haired bosses with no understanding of the technology they manage. This grounding in reality means you won’t waste time learning something that you’ll never use.

Anyone who has tried to write clearly knows how devilishly hard this is to achieve. So many technical books suffer from the same problem: The people who know can’t write, and the people who can write don’t know. When done well, though, writing becomes transparent, leaving the reader the space to learn. Luckily for us, their readers, Nat and Jeff have crafted their words with the same care with which they write their code. The happy results are this book, which you now hold in your hands. Nat and Jeff have admirably done their job of writing. Now, it’s up to us. Let’s get reading!

—Hal Helms

  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint