.jpg)
By There's a syndrome, so to speak, in guitar-player circles. It's rather unfortunately known by the acronym GAS, which stands for Guitar Acquisition Syndrome. And while that might seem sort of odd, it's completely relevant to our latest releases, Head First JavaScript and Head First Software Development. Curious? Read on...
The thing that GAS implies -- and why it's so relevant for guitar players -- is that you're never (hardly ever) satisfied with the guitar you actually buy and take home. It's wonderful in the store, it sounds great, it feels right under your fingers, it rings out, it's beautiful... but about three days later, you're surfing EBay looking for a Collings OM1AC to supplement your wonderful Martin Laurence Juber model. It just happens... over and over again.
Books, it turns out, are often the same way -- especially when they're books you work on for months or even years. I've been working on Head First Software Development with at least one of the co-authors for two years, I found the author for Head First JavaScript eighteen months ago, and the C# authors, well, we've been working together for well over a year, too. So there's a tendency to get the actual book, look at it, and realize, "Wow, this wasn't everything I thought it would be."
Maybe it's HFPAS, Head First Project Acquisition Syndrome. You finish a project, you love it, think it's great, it's wonderful, it can't get better, and then three weeks pass, the book gets printed, and it shows up on your doorstep. And you see errors, you see things you wish had been better, you grimace... the whole bit. And, honestly, I've felt that way before, actually about some books I've written.
For example, when I got Head Rush Ajax, there were a lot of things I wish I could have added. We did that book really quickly, to get it out for lots of anxious readers, but the final product left me a little disappointed. Happily, we're working hard on a complete treatment in Head First Ajax, due out next year. 650 pages or so, and we'll be able to address a lot of things I wanted to. I had the same reaction, long ago, with the first edition of Java and XML, and then after about a month of living with Building Java Enterprise Applications (Volume I of a 3-volume set that never became more than one volume).
ISo with book in hand, I wanted to report on my feelings about Head First Software Development (I didn't live with Head First JavaScript day-in and day-out, so I'm not commenting on that one, we'll let Catherine do that!). Honestly, I love it. I don't want to go back and add things, or change things; I really love the book. It feels strong, really engaging, and complete. In fact, it most reminds me of Head First Design Patterns, and that's saying a lot (Design Patterns is arguably our most-loved, and best-selling, title).
It's great. I have no HFPAS. I can enjoy my Christmas without looking on EBay for a new Head First project (besides, I have plenty to keep me busy!). I love the book, and I'm confident you will, too.
But one question (and I just want to see if you read this far): do you know what Head First Software Development covers? Do you feel like you know what you'd see in the book? Are you wondering exactly what it covers? I'm very curious... let us know.
Happy with my book,
Brett :-)
Share:
The passion you folks have is what makes waiting for your books bearable because I know every day you spend with it is making it that much better.
To answer your question, I don't really know what HFSD is about. I assumed it was project lifecycle stuff, kind of like a sequel to the PMP book. I think it will be more theoretical like the Patterns and OOAD books, but I really have no idea.
No idea.
Velocity, burn down rate, TDD... Is this actually agile development?
Brett,
You had me worried there! As one of the technical reviewers, I was wondering what problems I missed or areas I should have suggested be covered differently.
I'm glad this was one of those surprise ending stories - and I can't wait to see the book. Any idea when it should hit the shelves?
Thanks,
Burk
P.S. I'm not going to put down what I expect to see in the book. It'd be to much like insider trading.
When I first heard the title, and knowing that it came from Head First Labs, I expected it to be similar to The Pragmatic Programmer. However, with the December newsletter highlighting the software development Big Board concept in the book, I figure I'm pretty far off.
Now my best guess is that it has more to do with the process of software development projects, and less to do with the best practices of being an excellent software developer, regardless of programming environment.
Best case, it's both!
I have the book and I'm two thirds of the way through.
It is excellent!
Very nice job to all involved.