Book Review: Girls Who Code


Girls Who Code is an organisation aimed at helping women get into tech.

The founder Reshma Saujani wrote a book by the same name. The book’s recommended age is 8-12. It’s a comprehensive guide for learning to code.

While well-intentioned as it is, I don’t think this is a very book as means for learning to code. For a book that is intended for children – it is too long and overwritten.

From a feminist perspective, isn’t a STEM book targeted at women a little ironic?

One of the main points in discourse around women in tech is that tech is gender neutral – tech isn’t an inherently boyish activity.

I find it a little amusing then, that this book fundamentally uses gender roles to sell itself.

I don’t think it’s wrong to do it. If there really is a cultural norm of ‘girls don’t do tech’ and this book gives permission for a girl to be interested in tech, then that’s a good thing.

Also, the book is filled with profiles of important women in tech – and that’s great. Probably my favourite part of the book.

A disclaimer

I haven’t read the whole book. I got a good few pages in before I gave up, and just quickly skimmed the rest. The book is too wordy.

My review

This book is way too large and cumbersome.

It’s 160 pages long, and each page is filled with with text.

If the goal is to encourage young girls into tech – this isn’t the right way to do it. It’s not the right way to encourage any young person into tech.

It might impress parents, and other adults – with its comprehensiveness – but a child is going to find it overwhelming, and unfun.

I think being comprehensive is good. But this book uses too many words to do it.

An introduction to computer science book for children should be first and foremost interesting and fun, and easy.

One hundred and sixty pages of fairly dense reading, doesn’t really sound like fun.

Another thing this book suffers from, is bad design. The book uses a lot of cute handwriting style comments and arrows – I guess in an attempt to make it seem more friendly.


I think it’s just bad design.

A coding book should just aim to communicate as effectively as possible. Using recognisable and tidy layouts is the best way do to this.

This isn’t to say that a coding book shouldn’t be fun. Infact – I tend to prefer reading tutorials that have a more informal tone – but I’m going to find if it said ‘Righto lads, here’s how to create a for loop’ off putting.

The taco creation algorithm they used to demonstrate for loops was interesting, as was the bead creation algorithm. The profiles and timelines throughout the book are good.

What does make a good coding book for children?

It’s easy enough for me to criticise – but what would a good coding book for children look like?

It would be far shorter, for one. I think the way I would go about it – is I would create a first introductory book intended to be as fun and easy as possible, and then if the child showed continued interested in it – then they could purchase a second more indepth book.

I would aim to use as few words as possible. Each page, basically containing one simple concept.

I would intersperse simple quizzes through the book, testing the child’s knowledge. Quizzes are effective tool for maintaining engagement, as the child is given a sense achievement and progress when they answer the question correctly.

I’d intersperse cartoon pictures throughout the book to keep it interesting.

So that’s it. Seeing this book, makes me think I should I considering writing my own one.


Technological challenges of travelling.

1. Keeping your phone charged.

2. Having an internet connection. (Even if you have mobile data, your phone is often out of reception).

3. Syncing your photos from camera to laptop.

To mitigate, I definitely recommend bringing

1. A fast charger.

2. A phone charging power pack.

I’ll have to look into seeing if you can sync Dropbox via USB.