Skip to main content

On The Steel Breeze

by Alastair Reynolds
ISBN: 978-0575090453

Fantastic! I loved this book. I really struggled to put it down and was reading it at every opportunity. I was even reading it for the three minutes it took to microwave my lunch at work each day.

It’s great not to have to start my review saying that this book is excellent, but not as good as Revelation Space, because it is, although it’s not as broad in terms of the scope of the story.

Unlike Blue Remembered Earth, you’re straight into the action with On the Steel Breeze and there’s none of the slow character building. It sits so well on the foundations created by Blue Remembered Earth that I wish I’d gone back and read it again first. I also liked all the characters this time.

There’s a great sense of mystery right up to the end. Most science fiction stories based around a paranoid machine intelligence remind me of HAL. However, HAL was a well intentioned, mislead child. Arachne, at least the version of her integrated into the Earth mech is clearly evil.

Science fiction is usually a look at possible future societies and many of them are utopian futures where there is no more conflict or murder and all of them are wavering on the brink of falling back into chaos. It’s the same in the future painted by On the Steel Breeze. And of course the characters acting for the good of everyone push it over the brink.

Following an experiment that went catastrophically wrong and destroyed a holoship, all development of the engines needed to slow the holoships down and allow them to reach their goal was prohibited. I was frustrated with the authorities making this decisions all the way through the book. It just felt so short sighted, but this is often how governments are. I also missed why the holoships couldn’t turn themselves over and use the engines they’d used to reach their transit velocity to slow down.

The end only answers about 90% of the questions asked by the rest of the book and sets the scene perfectly for the third and final part of Poseidon's Children. In the meantime I’ll be readying Doctor Who: Harvest of Time, also by Alastair Reynolds.



Comments

Popular posts from this blog

I, Robot

The Foundation series has been my go to for a good, enjoyable read over the last two years, so naturally I moved on to Asimov’s Robot series afterwards. However, the short stories in I, Robot were mostly a disappointment. They feel self indulgent, with too much philosophy and science, Asimov showing off, and not enough story. The most enjoyable moments come from the stories featuring Gregory Powell and Mike Donovan. Their banter and the relationship between them provide some much needed amusement and were easily the highlight of the book for me. However, it did give me food for thought for the current potential issues with the rapid development of AI at the moment, and the many concerns around safety. I wonder if all we need is: An AI may not injure a human being or, through inaction, allow a human being to come to harm. An AI must obey the orders given it by human beings except where such orders would conflict with the First Law. An AI must protect its own existence as long as such p...

It's great to be back at the ACCU Conference 2025!

Last week I was back at the ACCU Conference in Bristol, for the first time since I gave an opening keynote in 2019 . In March 2020, COVID hit the UK and I got out of the habit of attending and speaking at conferences. Plus the ACCU Conference, and the organisation in general, took a big step back towards C++ and that hasn’t been relevant to me for nearly two decades. It’s taken until now, 2025 for me to want to talk again, and I was really pleased to be accepted for the ACCU Conference again. It was just a 20 minute session and I only attended for the day I was speaking. There was enough varied content for it to be interesting to me and I’m hoping to be back for the full conference next year. I really enjoyed attending and it was great to catch up with people I hadn’t seen for years. I felt re-engaged and particularly liked being asked if I’d been to nor(DEV):con . Learning to stop writing code (and why you won't miss it) Daisy Hollman I should have read the summary of the openin...

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...