A basic introduction to HTML5
HTML5: The Missing Manual
Matthew MacDonald
O’Reilly
O’Reilly Publishing provided me access to an electronic copy of this book for review purposes.
When I start looking at books on programming languages, such as HTML5, I look for a few different things. 1) Easy to read and understand language
2) Clear cut, easy to follow (and correct) examples of code
3) Good additional resources to look at
4) Layout and organization of chapters and subtopics flows well
5) And depending upon the language, an in-depth look at how it works.
While this book doesn't offer an in-depth look at every aspect of HTML5 (it is meant for beginners) it does meet the first three criteria that I look for and mostly meets the clear organizational path.
This book doesn't give an in-depth look at HTML5 because what Matthew is trying to do is provide a basic introduction to the various tools and components of HTML5 and how you might be able to use them in your day-to-day work. And this is where the book excels. Matthew breaks down the book into three broad themes (meet the new language, creating modern webpages, building web apps with desktop smarts) and further broken down into 12 chapters on each of these broader themes. Plus he includes a great 4th section with appendices and other additional resources and real world examples of code in use.
In the first section Matthew does a great job of explaining how HTML5 came into being versus the continuation of XHTML and how W3C works to approve code. This is important to understand in the context of this book as not every standard developed by the committee or shown in this book works with every browser at this time (there is at least one that only works with one browser thus far.) Matthew does a good job of letting the reader know which standard will work with which browsers and when, if ever, the standard might be widely adapted. He also does a good job of breaking down the various standards that have the most real world use in building webpages, such as the discussion on semantic tags in Chapter 2. Matthew provides clear cut examples of code and explains how you might be able to use them.
04 October 2011
03 October 2011
Why do we fall?
I love "Batman Begins". Not just because it brought Batman back to life in the movies, but because of a line that Alfred Peenyworth says to Bruce Wayne: "Why do we fall sir? So we might learn to pick ourselves up."
I mean seriously, just how awesome is that line? Ole Alfred isn't talking about the physical fall, but the mental fall as well. And boy do I need to remember that line a lot these days. I keep falling over broken promises, perceived slights from others, and goals that I set for myself. I keep letting myself be overcome by the stupid and worrying over the things that I can't change. And I've got to remember, to pick myself back up, dust off my clothes, and go back to being the kick ass person I know I am, both professionally and personally.
I mean seriously, just how awesome is that line? Ole Alfred isn't talking about the physical fall, but the mental fall as well. And boy do I need to remember that line a lot these days. I keep falling over broken promises, perceived slights from others, and goals that I set for myself. I keep letting myself be overcome by the stupid and worrying over the things that I can't change. And I've got to remember, to pick myself back up, dust off my clothes, and go back to being the kick ass person I know I am, both professionally and personally.
Where do we go from here?
I've seen quite a few things recently about the future of libraries...ok almost everything I see is about the future of libraries and how we're either in competition with Amazon, Google is going to kill libraries, Amazon is destroying us, or some unknown alien race is going to show up and displace libraries and librarians with their galactic encyclopedia. And all of this is interesting...but why do we keep worrying about who or what we're in competition with? Yes there are a lot of different places that offer some of the same services that we do, but there's nothing that offers everything that we do. We keep talking about how libraries aren't just the brick and mortar buildings, that we're the resources, we're the digital, and most importantly we're the people who can help our users find what they need. That we're all of these different things that work together to become an integral part of the community. That we know the people that come in our library by name. That we know what resources they need.
Well can Amazon offer that? Can Google offer it? No they can't. They can make recommendations via computer algorithms, but they can't be everything that a library can be. They don't have people there to ask them how they're doing or how their pet is. Or know their homework assignment because they talked to the professor or teacher last week. These businesses, these companies, these aliens, these whatever can only do part of what we do. We can do so much more.
Can we learn from these companies though? Sure. 1st lesson: Apple, Amazon, Google and the others didn't get to where they were by coming out in public and wailing that the next company over was going to put them out of business. They looked at the world around them and said "f'it. we can do better than that" (not a direct quote by the way) and went out and made it better. So what do we do? We go out and make it better (which we have been doing.) We've just got to start following the 2nd lesson which is...
2nd lesson: Amazon, Apple, and Google didn't stand on the sidelines and mumble about how they did it better. They shouted it from the rooftops and didn't let themselves be pushed out of the way. So let's stop spending our energy on worrying how x is going to put us out of business and start focusing on learning from them and improving what they can offer. So that we can better serve our community. Our users. Those people that we know by name (even if we sometimes wish we didn't.)
3rd lesson: Stop letting other people take credit for the things that we've done and show our users, show the people that fund us just how great we really are. Talk to the press, tell them what we're doing, what we've done and how we've influenced the world. We've got to stop doing things the same way and go out there and promote ourselves.
It's a new age and we're not going anywhere. Let's show the world that.
Well can Amazon offer that? Can Google offer it? No they can't. They can make recommendations via computer algorithms, but they can't be everything that a library can be. They don't have people there to ask them how they're doing or how their pet is. Or know their homework assignment because they talked to the professor or teacher last week. These businesses, these companies, these aliens, these whatever can only do part of what we do. We can do so much more.
Can we learn from these companies though? Sure. 1st lesson: Apple, Amazon, Google and the others didn't get to where they were by coming out in public and wailing that the next company over was going to put them out of business. They looked at the world around them and said "f'it. we can do better than that" (not a direct quote by the way) and went out and made it better. So what do we do? We go out and make it better (which we have been doing.) We've just got to start following the 2nd lesson which is...
2nd lesson: Amazon, Apple, and Google didn't stand on the sidelines and mumble about how they did it better. They shouted it from the rooftops and didn't let themselves be pushed out of the way. So let's stop spending our energy on worrying how x is going to put us out of business and start focusing on learning from them and improving what they can offer. So that we can better serve our community. Our users. Those people that we know by name (even if we sometimes wish we didn't.)
3rd lesson: Stop letting other people take credit for the things that we've done and show our users, show the people that fund us just how great we really are. Talk to the press, tell them what we're doing, what we've done and how we've influenced the world. We've got to stop doing things the same way and go out there and promote ourselves.
It's a new age and we're not going anywhere. Let's show the world that.
22 September 2011
Book Review--Book of Ruby
The Book of Ruby: A Hands-On Guide for the Adventurous
by Huw Collingbourne
No Starch Press 2011
O’Reilly Publishing provided me access to an electronic copy of this book for review purposes.
Thanks to Ruby on Rails, the Ruby programming language is one of the most popular languages at the moment to learn. But according to the author you can't just jump into Rails without first learning a bit of Ruby and thus this book was born. This book was written and developed for the novice to learn the basics of how Ruby works and what some of it's pitfalls are. The author points out in the introduction that although Ruby may look deceptively simple to learn, it really isn't and it is his hope to help people navigate and learn this complex language. This massive book (over 400 pages) is broken down into 20 chapters each on specific topic of Ruby (such as strings and ranges) and then further broken down into subtopics on the main topic, with screenshots and examples of the language scattered throughout to better help the reader place into context what the code should look like.
First I should say I'm not an experienced programmer (I've been learning the languages but don't have a chance to use them as often as I'd like.) So what I'm looking for and got out of this book may be different than what others are for. I'm looking at this book as a way to pick up some of the basics of Ruby to get started with, how it compares with other languages, and what the biggest headaches are about it--so I can't speak to whether or not there are better (or perhaps more standard) ways of preforming the same function/example that others maybe able to. What I can say is that, at least the beginning of the book, gave me a good feel for some of the things that the language can do and what the code might look like in the real world (or at least how to recognize that the code I'm looking at is Ruby.) Huw's writing style is written to be more non-technical than some other programming books so it's relatively easy for the novice to understand and follow along. The later chapters however, didn't give as much information on a topic as I would have liked, such as the chapter on debugging. I get that Huw was just trying to give an introduction to the concept, but I think it deserved longer treatment, especially since it's a book for the novice and this seems like an important part of getting Ruby working correctly.
The other thing that really bothers me about the book is how comments are done in the coding examples in the book. They are written just like you would find them in real world code, but for me it was confusing at times and just added to the jumble especially when they came on each line. I just wanted to be able to focus on walking through the Ruby code and not figure out the annotations at that moment. Perhaps if it had been a different color it would have helped or if it was explained beneath the example (as other programming books have done), but as is some of the coding examples were less than helpful. So while the beginning of the book provided a somewhat useful introduction on Ruby and what it could do, I know that I can get the same information and examples that are more beneficial to my learning style through some online tutorials and in other books.
If you do well with having a printed book next to you to help you learn a new language then at least the first part of the book might be useful to you. If you're already an experienced programmer or have a bit of Ruby knowledge then you might get better value at looking at online tutorials/schools or other more in depth books. I will say for me that if I hadn't been provided a review copy of the book I wouldn't have picked the book up and I won't be buying it for my library as I think that are books better suited for my students learning style (and with more information) than this one.

by Huw Collingbourne
No Starch Press 2011
O’Reilly Publishing provided me access to an electronic copy of this book for review purposes.
Thanks to Ruby on Rails, the Ruby programming language is one of the most popular languages at the moment to learn. But according to the author you can't just jump into Rails without first learning a bit of Ruby and thus this book was born. This book was written and developed for the novice to learn the basics of how Ruby works and what some of it's pitfalls are. The author points out in the introduction that although Ruby may look deceptively simple to learn, it really isn't and it is his hope to help people navigate and learn this complex language. This massive book (over 400 pages) is broken down into 20 chapters each on specific topic of Ruby (such as strings and ranges) and then further broken down into subtopics on the main topic, with screenshots and examples of the language scattered throughout to better help the reader place into context what the code should look like.
First I should say I'm not an experienced programmer (I've been learning the languages but don't have a chance to use them as often as I'd like.) So what I'm looking for and got out of this book may be different than what others are for. I'm looking at this book as a way to pick up some of the basics of Ruby to get started with, how it compares with other languages, and what the biggest headaches are about it--so I can't speak to whether or not there are better (or perhaps more standard) ways of preforming the same function/example that others maybe able to. What I can say is that, at least the beginning of the book, gave me a good feel for some of the things that the language can do and what the code might look like in the real world (or at least how to recognize that the code I'm looking at is Ruby.) Huw's writing style is written to be more non-technical than some other programming books so it's relatively easy for the novice to understand and follow along. The later chapters however, didn't give as much information on a topic as I would have liked, such as the chapter on debugging. I get that Huw was just trying to give an introduction to the concept, but I think it deserved longer treatment, especially since it's a book for the novice and this seems like an important part of getting Ruby working correctly.
The other thing that really bothers me about the book is how comments are done in the coding examples in the book. They are written just like you would find them in real world code, but for me it was confusing at times and just added to the jumble especially when they came on each line. I just wanted to be able to focus on walking through the Ruby code and not figure out the annotations at that moment. Perhaps if it had been a different color it would have helped or if it was explained beneath the example (as other programming books have done), but as is some of the coding examples were less than helpful. So while the beginning of the book provided a somewhat useful introduction on Ruby and what it could do, I know that I can get the same information and examples that are more beneficial to my learning style through some online tutorials and in other books.
If you do well with having a printed book next to you to help you learn a new language then at least the first part of the book might be useful to you. If you're already an experienced programmer or have a bit of Ruby knowledge then you might get better value at looking at online tutorials/schools or other more in depth books. I will say for me that if I hadn't been provided a review copy of the book I wouldn't have picked the book up and I won't be buying it for my library as I think that are books better suited for my students learning style (and with more information) than this one.
Labels:
book reviews,
o'reilly,
Rails,
ruby,
Ruby on Rails
Subscribe to:
Posts (Atom)