Idaho Books

Jana Harris, We Never Speak of It: Idaho-Wyoming Poems, 1889-90 (Ontario Review, 2003)

We Never Speak of It starts out with a bang, as good poetry books probably should; "Crossing Lava Creek," a poem that (and I feel like this is a spoiler) describes what can only be a tornado coming out of nowhere, but doing it in such a way that it's hard to tell it's anything but an everyday storm. Just, in other words, in the voice of its eleven-year-old narrator.

What happens after this is really the deciding factor as to whether this book is or is not one of the best books of poetry I've read in the past few years, and I still haven't figured that out. Either Harris is so in tune with her subjects, and manages to use the diction in which they speak, so much that the time period in which these poems take place becomes second nature, or the poems themselves slide into the realm of the good rather than the realm of the fantastic. (The end result is the same; everything that comes after "Crossing Lava Creek" seems rather an anticlimax, even the other storms.) The difference between the two is whether it's a conscious trick of technique (as in, say, the novels of Cormac McCarthy) or whether familiarity, in this case, bred contempt. I am more than willing to give Harris the benefit of the doubt, and wouldn't have even considered the other possibility save that such a talent is so very rare; as readers of McCarthy will attest, using such a rhythm so that it is both effortless for the author and for the reader is even more rare. If that really is what's happening here (and reading a few more books by Harris, which has shot up my list of priorities as I made my way through this, should tell me if it is), then, as is becoming increasingly common in the past few years, I have uncovered another seemingly overlooked gem in the pantheon, another poet whose work is in desperate need of being read by, well, anyone and everyone. If not, it's a book chock full of good, solid work, and should be read at least by those with a liking for poetry, for history, and especially for the combination of the two.

This rating may go way up in the future. *** ½

This book is at best a reference that must be used in conjunction with another book, or better yet, Forest Service maps. While the author does point this out, I feel that several necessary details could have easily been included in this ...book, but were not. For example, elevations are not included, reference maps are far too vague, hiking difficulty ratings are there, but are less than accurate; and when a road that must be traveled for 17 miles to get to the trailhead is very close to 4-wheel terrain, it should be noted so (fortunately I was in my 4-wheel truck). Also, if signage to the trailhead is poor, or non-existent, better instructions on finding it are in order. And the trail I'm referring to is one of the most traveled in Idaho. I later found that Falcon's 'Hiking Idaho' did a much better job making up for 'Wild Idaho's' shortcomings. Problem is, the former doesn't cover all the same hikes.

There are few more significant areas of historical study for twentieth century America than the development of aviation. For residents of the western part of the United States aviation was an especially significant engine of change, owing to the unique combination of open spaces, relatively small numbers of population, distances between urban areas, and, a pioneering spirit.

"Winqs Over Idaho" is a useful large-format illustrated history chronicling the growth of aviation in one Rocky Mountain state. The author describes in 16 chapters of referenced narrative and 184 photographs the aviation story of Idaho. Beginning with lighter-than-air activities with kites and balloons in the nineteenth century, Arthur A. Hart moves quickly into early air meets in Lewiston and Boise. He expends much effort dealing with barnstorming and daredevils but then moves on to the much more significant air mail activities of the 1920s and 1930s, the first time airplanes undertook practical activities.

From there, Hart delineates the development of a wide variety of aviation activities in Idaho. For example, he describes the maturation of a unique cadre of flyers in Idaho during the 1920s, the Mountain pilots--also called bush pilots in other parts of the world--who knew the terrain well and provided aircraft for hire for a variety of business, government, and sporting activities. In many instances inheritors of the legacy of these earlier skilled flyers still provide the only quick linkage to isolated areas in the region. His discussion of the growth of airline service is a welcome addition while still leaving room for additional work. Hart's description of airborne firefighting was useful for its detail about Idaho, while his narrative on coyote hunting from the air was both illuminating and slightly disturbing. His commentary on women aviators and the development of a state infrastructure for aviation are most worthwhile.

Arthur Hart finds, quite rightly, that World War II was the truly significant transforming force for aviation in Idaho, just as it was for the rest of the nation. The establishment of civilian pilot training programs at many locations by the Civil Aviation Authority, the creation of military airfields, and the expansion of knowledge about and access to aircraft (to say nothing of the technological developments that made aviation relatively safe and reliable) all combined to fundamentally alter public acceptance and use of airplanes in their daily lives. Hart's chapters on this period are especially valuable in beginning to understand this revolution.

Hart has done a creditable job of providing a general description of aviation in the state. While there is much positive that can be said for the book, "Winqs Over Idaho" lacks any analysis and interpretive structure. Hart understands this, and writes in his foreword that his book is only a beginning of inquiry into the subject. He hopes that "others will take up the needed and fascinating task of researching in depth the history of aviation in every Idaho town and region" (p. 6). Aviation in the American West very badly needs the in-depth study Hart recommends.

Alice Sebold's THE ALMOST MOON receives three-time Oscar nominee Joan Allen's fine professional acting voice as it tells of Clair and Helen, a parent and child locked in a dangerous relationship - and what happens when a boundary is crossed that will change both their worlds. The 24-hour period which follows, brings revelations to both in this moving novel.

Strange book. I'm of two minds about it. It is interesting in that it delves into the psychological problems of the protagonist's parents. Issues including depression, suicide, dementia, agoraphobia are all part of the novel. Helen acts in some ways after her mother's death that ring true. On the other hand, some of her actions do not ring true. And while caregiver stress was part of Helen's problem, I felt the author could have brought this more to life so we could understand better what made Helen kill her mother (not a spoiler - happens in the first chapter). As it stands, it takes the entire book to see any reason for her actions, and then the reasoning still seems hazy. Organizations can offer help to the homebound.

I read this book just a few months after the death of my own mother, and that might have colored the lens from which I viewed this book. The book cover says this book is "raw and powerful" and it is. But I finished the book feeling uneasy and unsettled.

I felt totally miserable after finishing this book and that's the way I DON'T want to feel. Helen is the artist's model daughter of Claire and Daniel, both of whom are tainted with hereditary madness. After Daniel's suicide, Helen succumbs to a final rage as her demented mother taunts her without let up, smothers her, washes her soiled body and stuffs her into a chest freezer until she decides which actions to take. She rings Jake, her ex husband who agrees to stay with her until she makes a decision and then contacts her elder daughter. It's then that the reader can see the cycle begin again with enough inherited madness seeping through to infect the next generation. It's a bleak, unforgiving book which depressed me beyond words and one which I would not recommend to anyone.

The best part of reading Sebold is the interesting, quirky way she approaches serious topics. She pushes her themes of madness and murder to the edge of the horror genre. Although the writer doesn't crossover to a true vampire tale, I almost wish she had. Instead, we get a life-sucking mother and the psychologically-bitten daughter. Both of whom are, not far into the book, unlikeable characters and impossible for me to connect with. The story has a promising start with Helen Knightly stating in the opening line that she's committed the most ignoble crime, matricide. The writer is masterful in capturing a tortured childhood ruled by mental illness - that of both the obviously sick mother and seemingly enabler father. You don't have to like the child or the adult she has become to appreciate how the child Helen tones survival skills to negotiate her place in the family. Although she is born late into her parents' marriage, she is not the adored only child one would expect to meet; she's the interloper between two people who would have done best if left to dance together alone. Yet, the good stuff about the book doesn't save it. The beautifully writ language notwithstanding, the characters fail to ring completely true. The characters and the plot hang, never becoming entirely believable as either the monsters of fantasy or in reality one's own declining parent or odd next-door neighbor. Two scenes are especially abhorrent: Helen's trophy-taking in serial-killer fashion and the mob of neighbors bent on hurting the mother and attacking the girl in her stead. This is a dark, disturbing story with an unfinished ending. It failed to illuminate the generational destruction of untreated mental illness. That's another crime.

Helen Knightly has spent all her life looking after her mother, Clair, in some form or fashion, being tied to her in an unhappy, unhealthy, unrelenting relationship that has taken a toll on her in various ways. Now, Clair's dementia has reached the point that something has to be done; she is going to have to leave the house--a task that was psychologically painful and difficult for Clair--as she is no longer fit to stay home by herself. Helen is relieved and anxious at the same time and as she deals with her mother's vitriolic tongue and loose bowels, she surprises herself by smothering Clair.

Over the next 24 hours, Helen behaves as irrationally as any human being would, becomes entangled more and more in a web of lies and (through memories) exorcises some of the demons of past as she deals with the mental illness of her family.

Sebold has done an incredible job of writing about mental illness, and as an author she passes no judgments, gives no advice, just has Helen tell her story and leaves the rest to the reader. In Helen, one sees a character so human and unpredictable that it was almost uncomfortable at times to read her thoughts, feeling like an intruder or eavesdropper.

I read several negative reviews and I think it was really Sebold's amazing talent that prompted these. Those readers that complained about this or that action of Helen's appear to have been expecting Sebold to pass the appropriate (to them) moral judgments on said action and when she didn't these readers assume she condones these actions. Other readers couldn't believe Helen would act the way she did, having apparently never acted irrationally under stress themselves, and didn't see the deep realism of Helen's character acted out in her irrationality.

I found it a very moving book and at times it was too emotionally taxing and I had to take a break from it. It's hard to say I "liked" it, because, how can one "like" a story about mental illness in all it's dirty, real life, day-to-day struggles. I was reminded of Nabokov's Lolita--I didn't "like" the subject matter, but loved the book. This is another instance of that. The Almost Moon, while not for everyone, is a emotion-packed, realistic novel from a very talented author.

I'm using this book for a class. We're up to chapter 6 now, and while I'm learning a lot of basic concepts, I've stumbled several times on the writing. It's terribly unclear in places, and clarity is essential in some of these places -- to be short, it's poorly written.

The scope of the book is so wide that it necessarily is shallow. The illustrations are a bit silly and are not a great improvement to clarifying the concept. I am reminded of manuals that go into overwhelming detail as to what mouse-clicks or menu items to select, but don't explain why you want to do this to begin with.

I haven't taken any certification exams as yet, but I would only recommend this book as a brief introduction to subjects that are covered more thoroughly and competently in other books.

I am a network engineer with almost 10 years experience. I have typically shied away from certification tests because I have always found them to be of the "right answer, wrong answer and TEST ANSWER" category. Security+ is absolutely no different but my job required that I take this certification. I signed up for a class at the local college and this was the textbook for that class.

I read the book cover to cover twice, skimmed it twice more, answered the end-of-chapter questions, took the practice exam included on the cd over 20 times and passed everytime with scores 85% and higher. I failed the security+ exam. The difference between the questions on the test and the topics in this book was amazing. DO NOT RELY ON THIS HORRIBLE BOOK TO GET YOU THRU THE TEST. IT IS A COMPLETE WASTE OF TIME AND MONEY.

If I could have given it negative stars, I would.

Generally speaking, this have to be by far one of the worst books I have come across for both the content related to the scope of the subject matter, and also extreme inaccuracies due to total lack of comprehension on the material from the author.

The subject matter is general security concepts as it relates to the Security+ exam. In this scope, I expected the material would focus the technologies themselves as they relate to security that is not specific to any one platform, as after all every major OS uses the Internet and E-mail for example. However, this book is overwhelmingly a Windows only book, and reflects a rather narrow vision of Windows-only problems, technologies, and solutions.

In the narrow view of Windows only security, there were so many deficiencies in this book, I could write a tomb on a material. I'll highlight a small sampling of the stuff that really stands out. When covering DNS, there is no mention of secure updates through TSKIP (page 118), nor was there any mention of Active Directory (LDAP) integrated DNS (page 118). These Windows DNS solutions are really important and fairly easy to configure. On UNIX side, one can block zone transfers completely and restrict it through tcpwrappers or xinetd (Exctended Internet Daemon), and Windows can do something using IPSec policy configuration. The book never touches any concept or thinking of this nature for DNS or any other technology for that matter.

On the topic of Windows domains, the author states that "Active Directory is stored in a Security Accounts Manager (SAM) database" (page 120), which oh my, is oh so wrong. Perhaps in older Windows NT this might have been true, but Active Directory uses a distributed database (LDAP) for storing passwords and such, which an extended Jet database stored on each domain controller. The author goes on to proclaim his ignorance of Active Directory noting that a "primary domain controller (PDC) is the name of the server that houses a SAM database. A domain can also have multiple backup domain controllers (BDCs) that are on other servers in the domain" (page 120). Anyone knowing anything about Active Directory is probably rolling on the floor laughing at this moment.

In the topic of databases, the author only discusses Microsoft SQL Server specific issues, and ignores general database security issues and solutions. In the extremely narrow scope of SQL Server, the author recommends installing a personal firewall to block the virus Slammer. However, if the author understood how Slammer works or read any technical articles published by Microsoft on the issue, he would understand that to stop slammer all one needs to do is have a password for SQL Server. What the author doesn't do is note that MSDE, a limited SQL Server database bundled with many Microsoft and third-party applications, doesn't have any password configured by default. However, a password can be added through use of a command-line tool.

For e-mail technologies, the author dissuades using POP3 with completely inaccurate statements about the protocol (page 192). The problem also being with his arguments besides being flat wrong, is that it is his personal opinion on which technology to use and doesn't use any arguments in regards to security. Additionally the author doesn't even cover how to secure either POP or IMAP using SSL or TLS. In the scope of Microsoft Exchange POP and IMAP, there's no mention of the extreme dangers of using un-encrypted POP or IMAP, where passwords fly across the wire in clear naked text. Exchange is integrated into Active Directory, and as such, passwords for these facilities are passwords into their account. Using insecure IMAP or POP traffic is broadcasting the keys to the fort as the expression goes. This situation is not shared by Unix solutions (as they can be configured differently), but as Exchange forces you to use domain accounts, securing the traffic is extremely, repeat extremely, vital and important for security. The author misses the boat with this concept, like other concepts.

In regards to web technologies, this has to be perhaps the most laughable area. The author confuses JavaScript with Java, and even goes so far as to state that JavaScript is a virtual machine and that JavaScript is based on Java (Page 201). Those laughing right now might know that JavaScript was originally called LiveScript and had nothing to do with Java. It was renamed to JavaScript for marketing purposes to popularize JavaScript in created an illusion that it was related to Java. The author goes on to cover only Internet Explorer on only Windows platform, and states that all browsers suffer from the same security weaknesses as ALL other browsers (page 202). If the author had any inkling about browser technology, he would know that the scripting engine in IE is from embedded solution (OLE) sometimes referred to ActiveScripting. This engine has access to all other OLE libraries including saving viruses, um files, on your computer without any sort of authentication. Thus, even if this engine was rock solid secure, it's base features allow hackers to bad things to your computer. This ActiveScripting is embedded into WSH (Windows Scripting Shell), and also IIS (ASP), which is a cause for many exploits in those systems. Internet Explorer itself is packaged up and is embedded into other applications like Outlook, Outlook Express, Windows Media Player, Windows Messenger, MSN Messenger, etc. As some might know, those applications have had many exploits in the past, especially Outlook. Of course all of this is well beyond the ken of the author.

For wi-fi solutions, this has to be the weakest section in the book. On the coverage of specifically WPA/802.11i, the author doesn't cover enterprise WPA or things like a RADIUS server used to authenticate VPN, dial-up, and WPA. He also doesn't even mention AES or EAP security with WPA.

This book is one of the most appalling books I have come across, and cannot even recommend the book even if only for a good laugh. The quality of books sometimes is concern for many in the industry, and this book sets an all new low standard to shoot for.

(I apologize for being unusually harsh, but I have rarely come across a book so regrettable.)

I studied the text - all 17 chapters and the Appendix, then I took every one of The included study CD-based CertBlaster "Subject matter drills", then all 4 of the exams (passing every one on the first pass, and coming very close to perfection on the 2nd pass on any given test.)

I took AND FAILED the S+ exam today. ANY SIMILARITY BETWEEN THE STUDY TOOLS, THE TEXT BOOK, AND THE PRACTICE TEST WITH THE REAL TEST WERE RARE!!!! I basically wasted a week and several hundred dollars.

BTW. The Comptia S+ Exam was probably one of the worst knowledge measurement tools (e.g. exam) that I have EVER taken - and I have taken a huge number of them....
Just FYI
Will Harper, MCSE (NT 3,51/NT 4/W2K/XP), MCT, CCNA, A+, N+, CTT+ (and a bunch of other certs) AAS(IT/Networking), BSEE(computers), MBA.

This textbook does not cover the material in the Security+ Exam. Entire test subjects are not included, and the lab exercises are terrible. The lab manual only includes a few useful labs and some of them are so outdated they are irrelevant. Authors contradict each other, and the chapters do not hold together well. If you're looking for a lightweight topical introduction, this may work for you, but it won't help you pass the certification exam. This is a very weak introduction to network security, and there are better books available that do cover the content you need to pass the exam. Consider instead "Principles of Computer Security: Security+ and Beyond" ISBN: 0072255099

This book does a great public disservice. The information in the book has not been updated in years and is terribly outdated. Quite a bit of the information is absolutely wrong. Send the publisher a message - don't buy the book until they update it. Save your money, there are much better, current books out there such as "Hot Springs and Hot Pools of the Southwest" & Northwest - which are updated ever two years

The only useful thing about this writer's books on hot springs are the USGS maps and the latitude/longitudes. I bought a book of his nearly 20 years ago and was thoroughly dissatisfied, & was incensed when it seemed to me he was more interested in providing info for the land yacht crowd. I wonder if his book alleging that the lunar landings were hoaxes is any better. I doubt it. He probably denies the Holocaust took place, too. If you want a book on hot springs, check out Jayson Loam's books. They are much better. If you want info on faked lunar landings, get the movie "Capricorn One."

depending on what your looking for you may not want this guide. it has a fairly well established list to many commercial hot springs, but little else. If your looking for hot springs where you can hook up your RV then this guide may work for you. If on the other hand your looking for real, natural hot springs off the beaten path, then this guide is worthless.

We have tried one hot spring listing and enjoyed our hot soak, found one shut down, one remodeling and one a bit too pricey for us. Would like to see some reference to actual costs rather than than reasonable or free or deluxe. One place inacessible without 4 wheel drive but we will keep trying, the maps are good.

I guard my copy closely, now that it's out of print, though as of this writing you can still find copies for sale. My pages are dog-eared, text underlined and maps annotated.

This book has all the major trails, and some lesser-known gems. The author, like me, isn't timid about heading up an unmaintained trail, or heading off-trail, to get away from the crowds. (Maybe that's why the book title starts with "Adventures." My philosophy is, someone who doesn't know how to use a compass, or needs manicured trails, should go to the park instead of hiking in a designated wilderness.)

I like the way the book is organized, it helps me evaluate the various loop hike options and side trips -- and there are many in the Sawtooths.

The maps are nicely drawn original maps, not the barely-readable copies of topo maps that have become popular in guidebooks lately.

This book was one of the first to reveal the locals' favorite biking trails, and follow-on biking books seem to only copy it. And the trails are all hiking and biking routes, no space wasted on horse trails.

I also relate to the author's passion for the wilderness. She's active in conservation and wilderness preservation, not just an armchair hiker writing from some den in Sun Valley.

No matter what other area trail guides you might have tried, get a copy of this book if you can find it. It was the first guide to the "last best place," and it's still the best.

Cool Trails To You!

This out-of-print book is quite outdated itself. If you stick to the most popular trails and don't venture off of them, you'll be fine, otherwise, prepare for a little adventure yourself. Again, very outdated material.

This was probably an excellent book when it was first written. The information is getting to be a bit dated. At least half of the hikes we have tried have had some outdated information.

On one hike, the trail was nearly gone after what appeared to be years of no use. It would have been somewhat dangerous for us to continue the hike.

I will probably throw the book away and get a more up to date one.

This is a book for those who have a solid base in java now. Don't even think about using it as a beginner. I used it in a senior level course and it was the first book I worked with that dealt adequately with threads. Use this to polish your java skills. If you want a beginner's book try one of the head first books. The books that develop progressive skills are a dime a dozen out there, few will bring you into the advanced topics like this one does.

As Java is my sixth programming language I have a fair bit of experience with these type of books, and all I can say is that this is the worst I have ever come across. It has no sense of progression and it does not seem to have the idea of learning in mind at all - ie progressing from simple to more complex... It seems to be written for people who already know Java entirely and are wanting some kind of refresher, but its not very good as a reference either, so I actually don't know who would find this book useful....whats particularly annoying is that its not actually an advanced book, but the authors manage to make simple concepts as obscure and complicated as possible, so you struggle for ages trying to understand, and once it finally clicks, you feel almost cheated.

The writing is very repetitive too - by chapter 15 why are they still telling you that "the structure of the package mirrors the file system, so you can find the code for this example in ...."before EVERY single code example? It sounds like a stupid complaint, but I swear that sentence alone is responsible for about 5 pages of this book.

If you are forced to buy this book by your uni or college as I was, my advice is that you read it cover to cover several times, and don't be too concerned with understanding it the first or second time... you need the later chapters to understand the earlier chapters properly. I think the best way to read it is to start with the chapter end summary, then try and figure out the code example and discussion, and only after that confuse yourself with the actual chapter. It is not comprehensive and you are likely to spend a lot of time on the net (your cash would be better spent printing out Suns java tutorial) and using other books instead.

It is also horribly biased to IBM VisualAge for Java, as Wigglesworth was one of the developers, and the first bit of advice given to me by senior students at my uni was to rather use anything else, even javac, than that peice of...

To be fair, the questions are quite good and challenging, but as others have said, its kinda pointless without access to the answers.

The unfortunate effect of all this is that you end up frustrated with Java itself rather than just this badly put together book.

This is the kind of book that gives you a ton of useless classes to install on your system, along with about 50 pages of how to install the ... on your computer. If you don't watch it or read the fine print, one of the IDE's that the accompanying cd installs, will go and screw up your classpath during its install. The simple installing procedure to install some jar files is so complicated that you will spend a half a day getting it installed. And once it is installed the docs, make it impossible to generate the docs you need to use the stuff.

From the beginning of the book, there is no smooth transition about how to use java, it just jumps all over the place. The examples you are suposed to do in chapter 2, ask you to do IO things which aren't even covered until chapter 8....? Why do people do that?

The writer of the book did not take the end-user into account, but just wrote to get the job done.

It is a terrible book.

The idea for the story sounded great but the book was badly written. I read the large print copy there were 524 pages only two hundred of those pages had to do with mail order bride concept. On page 442 she finally meets Jordan's family and only 82 of her meeting her future husband and marring him. The ending of the book was unbelievable and rushed. The annoying part in the book the author kept repeating her self. This book just drags on.

While the concept for this story is good, and could have been a good read....it wasn't! The level it was written for seemed to be for very young adults, and things were over explained. The dialogue was unrealistic and way to 'wordy' , and the bride wasn't even introduced until well into the book, after a rather pointless, and seemingly never ending part about the man's life as a young boy. I understand the concept of introducing Christ as a main theme...but it was done in an annoying way, a way that would in my opinion, push people away, as to bringing them to Him. Basically, the only reason I even made myself finish this book was because I have a need for closure! The ending was completely unrealistic and horribly written....I know this review is rude...but I would definitly recommend AGAINST reading this book!

Though not my absolute favorite of Al and Joanna Lacy's books, this one was a very nice read. The entire Mail Order Bride series is worth a look to anyone who likes historical Christian romance.
Anyway, the book is about a young woman, Diana, who lives in fear of an abusive father. She is willing to do almost anything to escape...even become a mail order bride. The man she secretly corresponds with is a selfish young man who places the ad because he is rebelling against his matchmaking parents. He gets his best friend,Knight, who is a writer at the local newspaper, to compose the ad. He later convinces Knight to answer his prospective bride's letters because he has a natural gift with words. Diana falls in love with the wonderful letters that she receives and eagerly journeys far from home to marry the man that has so touched her heart with his words. Knight has unwillingly fallen for Diana as well and dreads seeing her wed to his best friend. But when Diana arrives, her future husband is missing. As she joins the search for him, she is thrown into close proximity with Knight. As she falls for a man she can never have, she thinks that that is the worst possible thing that could ever happen, not knowing that her father has followed her and is determined to bring her home...no matter what.
The plot was interesting and I liked the hero and heroine a good deal, but the number one reason I have to suggest this book is that it features some of my writing. I was the winner of The Mail Order Bride writing contest and the ad and letters written by Diana and Knight that are featured in the book are all by me. I am recognized on the copyright page, or whatever it's called. So, give it a try and if you happen to like my letters look for anything written by me in the future. I'm a bestseller wannabe like most of us out there.

Pictures were very disappointing....text was far too brief and offered little or no fishing advice. Access information was almost non-existant. No index. I returned the book.

I though this book was pretty good, but then again I am from Idaho and so I know where most of these places are anyway. The fly chart at the end was very helpful, but he book does tend to make everything sound "soo gorgeous" trust me its pretty but it aint heaven. The author obviously is biased toward slot limits and catch and release etc.. I can see how this book really wouldn't help someone from out of state looking for some good fishing, the author gives bad directions and instead of going in to depth of the species, size, weight, and type of flies for the streams, it assumes that you should know. Other than that its pretty good, the pictures are Ok, but Its not woth $11 if you ask me.