This book was published the year I was born. I recall reading it when I was a kid and being imressed by the mystery.
I wanted to see how it held up after all these years.
I think it's still a pretty interesting mystery and a fun adventure.
There are cultural issues (the only women in the story are mothers whose only job is to stop the fun).
As an adult, I appreciate the lecture the kids get about how important it is to not disrupt ancient sites,
If your kids read it, you might have to explain some stuff about telephones in here.
A good entry in the series. As an adult, having much of the plot being driven because Danny is foolish is a little annoying. As a kid, I never noticed this.
The story holds up to modern times.
It's nice to see a girl (Irene) in a boys book portrayed this positively.
So you can gives these to your kids, confident that Danny is shown to be a bad example and Irene is a role model.
I am a 67 year old professional software developer.
So I am way outside the target audience.
I have taught a lot of people at local colleges about computer programming
and I was curious about how the authors would introduce the topic to young people.
I thought this did OK at presenting how coders go about solving problems and manage their projects.
For me, I would have preferred more discussion of programming concepts like loops, functions, etc and less about whether the narrator will get asked to the dance.
But, as I said, I am not the target audience.
So if I knew any 6th grade girls I would give them these books.
I first came across Unix in the late 970's in college. It was instantly better for programming than the mainframe Univac computer many of my classes have been on.
Reading this book about it's early days was a delight.
Especially since I also worked for the real AT&T (not Bell Labs, but in the computer systems part of the company). Many of the tools and systems described in the book were and are things I use every day.
If you have used Windows, MacOS, IOS, Android or linux, you have encountered Unix.
If you are a software developer you should read this. If you are not, it's still a good introduction to the history of the computers you use everyday.
I quickly decided I didn't like the main character. She is on a date and decides to bail because he wanted to talk about things he was interested in like grunge music ( this is written to make it clear that this is a dumb thing to be interested in) and role playing games (even dumber) and not important things like books. Not a specific genre, just books in general. Maybe she had strong opinions on binding techniques.
I didn't find the magic system very interesting either.
So I abandoned the book and moved on to something else.
This is a lot of fun. hat if we are living in simulation and you learned how to manipulate the parameters that represent you?
Change the value of location and you are instantly somewhere else.
Change the value of hair color and you are a redhead.
What would you do?
Cleverly written and full of interesting ideas.
A little slow during the training montage but all in all, very enjoyable.
This is an autobiography about Mary Seacole in the mid to late 1800s.
Like other books like this, it's often confusing because the author sees no reason to explain
common terms, cultural actions etc that people from that time would just know.
She had an amazing life and the book is a good read.
I would recommend that you also listen to the History Chicks podcast about her.
She also appears in a recent Dr. Who episode.
I wish I remembered more chemistry than I do, parts of the book would have been more impressive.
I liked the story but sometimes the writing style made me think I had missed a few pages.
I prefer SF where its about big ideas or new discoveries, etc, I generally am less interested in the characters.
And this had a lot of science and engineering in it. It felt like Clarke or Asimov.