
In 1982 -- the era of Apple II and Commodore 64 -- 17-year-old college freshman and aspiring game designer Jordan Mechner began keeping a private journal. This first volume is a candid account of the personal, creative and technical struggles that led to his breakthrough success with Karateka, which topped bestseller charts in 1985, and planted the seeds of his next game, Prince of Persia.
It's a fun media experience with a lot of playable prototypes.
Full of his hopes, thoughts, fears, struggles, aspirations, setbacks, and successes. Old sketches and screen captures. Just reading about his workflow for the animation on Prince of Persia is fascinating.
Jordan has a way with storytelling.
The book for me is about spirit of working on your own projects, about curiosity and passion on whatever you choose to pursuit.
First, you should ask yourself - what kind of engineer do you want to be. Why are you building?
Then, read about the people who became the best and their early days. What did they do when they were in your position? Did they study a set of topics or did they pursue their passions? Taking and highly-weighing advice from people not at the top of the field could be very detrimental to your development as an engineer.
From reading books like: Coders at work, Masters of Doom, Making of Karateka, you will realize that the best engineers were driven by their ideas and projects very early on. They ended up learning to make things happen. But don't take my word for it, find these people, study their stories and pick the path you would enjoy the most.
This approach will not just make you a strong career engineer, but could turn you into one of the greats - the people that get to push the field forward.
The Making of Karateka https://www.amazon.com/dp/1480297232/
The Making of Prince of Persia https://www.amazon.com/dp/1468093657/
I recommend reading them in order.
I read both books 4 or 5 times, basically once a year everytime I start having doubts about being indie (non-game) developer.