I just finished reading Media Moms and Digital Dads: A Fact-Not-Fear Approach to Parenting in the Digital Age by Yalda Uhls. It's become more relevant as screen time has become a bigger issue at home given the remote learning situation and general growing up. I got the book originally when I was still at Google when the author came to do an Authors@Google talk (see video below), and back then I didn't have any kids.
I enjoyed reading the book and learned some things. Most of all, I now feel more calm with the role of technology in a kid's life and enjoyed the overview of the scientific research done to date about its positive and negative effects. There are some decent pointers in the book about best practices at home related to mobile devices, social media, and video games.
My notes on the book are below.
A fellow Xoogler recommended to me the book Solve for Happy: Engineer Your Path to Joy by Mo Gawdat. I just finished it and thoroughly enjoyed it. While the last chapter on "intelligent design" may seem the most controversial, the rest of the book is grounded on (much less controversial) science and simple practical tools for happiness. The book covers mental biases, getting over fears, using meditation, and presents many other techniques and ideas that can help bring peace and happiness to everyday life.
I identified a lot with the author as he is an engineer and Xoogler. The story of the loss of his son and the many associated anecdotes related to that were gut-wrenching; it's amazing that someone who has lived through that can write a book to help others be happy. There are so many good lessons in this book, and I highly recommend it. My main notes and takeaways are below.
I recently finished reading Startup Studio Playbook: For entrepreneurs, pioneers and creators who want to build ventures faster and with higher chance of success. Master the studio framework and start building. by Attila Szigeti. I was interested in reading it because I was exploring opportunities related to startup studios and wanted to read more about their history and best practices.
While this book had some quality/language issues, it was still overall very helpful, especially in its detailed case studies. It would've been nice to have more case studies included of US-based studios, but the non-US based ones were still informative.
I learned that many studios begin as consulting/web development agencies first and then get into studio/company creation work later once they've stockpiled some capital. And they raise money usually after some early demonstrated successes.
The book discussed several model process flows that various studios have used successfully. It was also interesting to learn about some of the techniques they use for ideation like hackathons and the role of EIRs.
This is definitely a good resource for anyone looking to get involved with or start a startup studio.
My main highlights from the book are below.