dorinlazar's review
2.0
Disappointingly, the book has less to do with Prince of Persia, per se, and more to do with Jordan's life around the making of Prince of Persia which is mostly about how he doesn't really want to work on PoP.
And I'm slightly put down by the always complaining author that did one of the coolest things ever. Made me sad, and bored me for a short while. But, after all, it's what his view of things is, that's how he saw them back then, and there are some instructive lessons there, if you can manage to read in negative.
It's ok to read, it's short and it reads fast.
And I'm slightly put down by the always complaining author that did one of the coolest things ever. Made me sad, and bored me for a short while. But, after all, it's what his view of things is, that's how he saw them back then, and there are some instructive lessons there, if you can manage to read in negative.
It's ok to read, it's short and it reads fast.
d_is_reading's review
3.0
The first half: Making of Prince 1 was interesting. After that it became mostly meeting & travel log. A good read, nonetheless.
timdams's review
3.0
An interesting read. However the title is misleading: making of gives one the expectation to read a gazillion (technical) details of the making of prince of persia. Guess what, you o ly get glimpses. This book would triple in value if the author would commented on his journal entries and gave way more detail and background to his short notes.
laci's review
3.0
I must say, I liked it. It wasn't about Prince of Persia as such, but Mechner's personal journals from the time period that mostly intersected with the making of Prince. I'm fine with that; especially given how humane and mortal it made Mechner seem, when he let us see how he struggled with doubt, how he searched for a direction (he wanted to do movies and not games, except did he really?), how he changed his mind and his goals. That's something that probably most creative people experience in one way or another.
I'm not giving it four stars just because of the point where it got cut off. A big part of the book was about Prince 2 (and more movies.) I did enjoy it, and the contrast with Prince 1 was especially noteworthy - but it was cut off _before_ PoP2 was finished, and it felt just so jarringly incomplete.
Still, if you're interested in artistic processes or an artist's doubts and struggles (because I'd argue that's the core of the book more than PoP itself), I'd recommend reading it.
I'm not giving it four stars just because of the point where it got cut off. A big part of the book was about Prince 2 (and more movies.) I did enjoy it, and the contrast with Prince 1 was especially noteworthy - but it was cut off _before_ PoP2 was finished, and it felt just so jarringly incomplete.
Still, if you're interested in artistic processes or an artist's doubts and struggles (because I'd argue that's the core of the book more than PoP itself), I'd recommend reading it.
sbossen's review
4.0
This book is a great capsule of the past for anyone interested in the process of game development. Since the book documents the experience as it is happening, it gives you a special connection through a sense of suspense. As a bonus, this book gave me some ideas for how to be successful in my work life in terms of project management.
djotaku's review
4.0
I got this as part of a bundle - probably Storybundle as I've bought nearly all their video game bundles - and I had put it off in favor of other books because I don't have a strong connection to Prince of Persia (POP henceforth). My family was working poor until I was getting into later elementary school, by which time a lot of computer game industry had lost its first "death" to the consoles. By the time I was playing computer games, it was mostly just RTSes hanging on and we weren't anywhere near the Steam Renaissance that would make the PC the best place to play games again (except for bad ports).
But a couple months ago, I sat at my computer and took at look at my To Read list on Goodreads and the 400-odd unread ebooks in my Calibre database I'd bought because, "how could you not buy 15 books when they're about $1 each?" So I made a plan to try and satisfy my need to read newer books with my need to read the books I'd purchased (or face my wife's wrath at wasting money on books). So I basically sorted the books by date added to Calibre and selected (approximately) one book per bundle (or free release from Tor.com's ebook club) and when I got to this bundle, I decided to take a look at these journals.
While I was never an Amiga gamer (see above), I've read plenty of how it was the superior machine in terms of what it could do at the time compared with Macs or IBM-Clones (what we now call PCs) and yet management ran it into the ground and we were left making up for progress all these decades. Likewise, BeOS was superior to Windows and Mac when it came out, but MS used their anti-trust strong-arming to keep it from taking off. So I'm already used to the idea that the best don't always rise to the top. Nevertheless, it was frustrating to see how Mechner was thwarted and we almost lost this amazing contribution to video gaming.
Mechner had Broderbund as his publisher - one of the giants of computer gaming at the time. I remember everyone having Print Shop Pro. I remember playing Carmen Sandiego at school and eventually owning it when my family got a computer around the time I was 11. They merged with Sierra, maker of my favorite adventure games as a kid. But they didn't know what to do with this action game. And they refused to give Mechner a promotional budget. I'm sitting here in 2017, knowing how great this series becomes - I played a bit of the Xbox version when my brothers had it one time when I came home from college. It is the spiritual ancestor of the Assassin's Creed series. It ends up becoming a movie. Just goes to show it doesn't matter if what you're doing is brilliant if you don't have the right support. (Spoiler: Eventually he gets the right support)
Who should read this book? Anyone who's interested in the game development scene of the late 80s and early 90s. It was a time when one person could put together a great game and by allying himself with just a few others, produce an incredible game. Since these are his journals they're very personal, not technical so I think you can enjoy it even if you're not a technical person.
But a couple months ago, I sat at my computer and took at look at my To Read list on Goodreads and the 400-odd unread ebooks in my Calibre database I'd bought because, "how could you not buy 15 books when they're about $1 each?" So I made a plan to try and satisfy my need to read newer books with my need to read the books I'd purchased (or face my wife's wrath at wasting money on books). So I basically sorted the books by date added to Calibre and selected (approximately) one book per bundle (or free release from Tor.com's ebook club) and when I got to this bundle, I decided to take a look at these journals.
While I was never an Amiga gamer (see above), I've read plenty of how it was the superior machine in terms of what it could do at the time compared with Macs or IBM-Clones (what we now call PCs) and yet management ran it into the ground and we were left making up for progress all these decades. Likewise, BeOS was superior to Windows and Mac when it came out, but MS used their anti-trust strong-arming to keep it from taking off. So I'm already used to the idea that the best don't always rise to the top. Nevertheless, it was frustrating to see how Mechner was thwarted and we almost lost this amazing contribution to video gaming.
Mechner had Broderbund as his publisher - one of the giants of computer gaming at the time. I remember everyone having Print Shop Pro. I remember playing Carmen Sandiego at school and eventually owning it when my family got a computer around the time I was 11. They merged with Sierra, maker of my favorite adventure games as a kid. But they didn't know what to do with this action game. And they refused to give Mechner a promotional budget. I'm sitting here in 2017, knowing how great this series becomes - I played a bit of the Xbox version when my brothers had it one time when I came home from college. It is the spiritual ancestor of the Assassin's Creed series. It ends up becoming a movie. Just goes to show it doesn't matter if what you're doing is brilliant if you don't have the right support. (Spoiler: Eventually he gets the right support)
Who should read this book? Anyone who's interested in the game development scene of the late 80s and early 90s. It was a time when one person could put together a great game and by allying himself with just a few others, produce an incredible game. Since these are his journals they're very personal, not technical so I think you can enjoy it even if you're not a technical person.
alexkalopsia's review
hopeful
informative
inspiring
medium-paced
4.0
An incredible jump in the past, full of details and stories about how a classic was born. Very inspiring.
loonyboi's review
4.0
While certainly not for everyone, this book is a great read, and a terrific look at the creation of one of the greatest games of all-time. I especially liked it since A) I grew up playing the original Apple IIc version of Prince of Persia B) I'm a video game producer by trade, and so it's great to read such a detailed account of how games were made long before I entered the industry and C) Mechner is from my hometown of Chappaqua, New York, so any references to local places brought back tons of memories of my own.
I can't say how it will read to someone without those particular ties to the book, but to me, it was great. Highly recommended.
I can't say how it will read to someone without those particular ties to the book, but to me, it was great. Highly recommended.