Showing posts with label science fiction. Show all posts
Showing posts with label science fiction. Show all posts

The Future of Data Centers, Small Computers, and Networks

I love trying to extrapolate trends and seeing what I can learn from the process. This past weekend I spent some time thinking about the size of computers.

From 1986 (Apple //e) to 2012 (Motorola Droid 4), my "computer" shrinking 290-fold, or about 19% per year. I know, you can argue about my choices of what constitutes a computer, and whether I should be including displays, batteries, and so forth. But the purpose isn't to be exact, but to establish a general trend. I think we can agree that, for some definition of computer, they're shrinking steadily over time. (If you pick different endpoints, using an IBM PC, a Macbook Air, or a Mac Mini, for example, you'll still get similar sorts of numbers.)

So where does that leave us going forward? To very small places:

YearCubic volume of computer
20201.07
20250.36
20300.12
20350.04
20400.01
20450.0046

In a spreadsheet right next to the sheet entitled "Attacking nanotech with nuclear warheads," I have another sheet called "Data center size" where I'm trying to calculate how big a data center will be in 2045.

A stick of is "2-7/8 inches in length, 7/8 inch in width, and 3/32 inch"  or about 0.23 cubic inches, and we know this thanks to the military specification on chewing gum. According to the chart above, computers will get smaller than that around 2030, or certainly by 2035. They'll also be about 2,000 times more powerful than one of today's computers.

Imagine today's blade computers used in data centers, except shrunk to the size of sticks of gum. If they're spaced 1" apart, and 2" apart vertically (like a DIMM memory plugged into it's end), a backplane could hold about 72 of these for every square foot. A "rack" would hold something like 2,800 of these computers. That's assuming we would even want them to be human-replaceable. If they're all compacted together, it could be even denser.

It turns out my living room could hold something like 100,000 of these computers, each 2,000 times more powerful one of today's computers, for the equivalent of about two million 2014 computers. That's roughly all of Google's computing power. In my living room.

I emailed Amber Case and Aaron Parecki about this, and Aaron said "What happens when everyone has a data center in their pockets?"

Good question.

You move all applications to your pocket, because latency is the one thing that doesn't benefit from technology gains. It's largely limited by speed of light issues.

If I've got a data center in my pocket, I put all the data and applications I might possibly want there.

Want Wikipedia? (14GB) -- copy it locally.

Want to watch a movie? It's reasonable to have the top 500,000 movies and TV shows of all time (2.5 petabytes) in your pocket by 2035, when you'll have about 292 petabytes of solid-state storage. (I know 292 petabytes seems incredulous, but the theoretical maximum data density is 10^66 bits per cubic inch.)

Want to run an web application? It's instantiated on virtual machines in your pocket. Long before 2035, even if a web developer needs redis, mysql, mongodb, and rails, it's just a provisioning script away... You could have a cluster of virtual machines, an entire cloud infrastructure, running in your pocket.

Latency goes to zero, except when you need to do a transactional update of some kind. Most data updates could be done through lazy data coherency.

It doesn't work for real-time communication with other people. Except possibly in the very long term, when you might run a copy of my personality upload locally, and I'd synchronize memories later.

This also has interesting implications for global networking. It becomes more important to have a high bandwidth net than a low latency net, because the default strategy becomes one of pre-fetching anything that might be needed.

Things will be very different in twenty years. All those massive data centers we're building out now? They'll be totally obsolete in twenty years, replaced by closet-sized data centers. How we deploy code will change. Entire new strategies will develop. Today we have DOS-box and NES emulators for legacy software, and in twenty years we might have AWS-emulators that can simulate the entire AWS cloud in a box.

The Lost Kickstarter Campaign

Before I published Avogadro Corp, I considered running a Kickstarter campaign to fund publishing the novel. I ended up publishing without the Kickstarter. Fast-forward three years, and I just found the campaign still sitting in my Kickstarter account.

Here's the description I wrote for the never-started campaign:
I am asking for help to publish my novel Avogadro Corp. The manuscript is completed, and just needs a final round of copy-editing, cover design, and layout in order to be published. 
Synopsis 
David Ryan is a brilliant computer scientist, cherry-picked to lead a new project at Avogadro Corp, the world’s leading Internet company. The goal of the project, called ELOPe, is to create a next-generation feature for the company’s email product - one that can optimize the language of emails to make them more effective and persuasive. 
With his chief architect, Mike Williams, and a team of programmers, the two have proven the feasibility of the concept and are hard at work trying to release the feature. When David gives a presentation to the executive leadership of the company, they are impressed by the project results and effectiveness. But David fails to disclose to the executives that the project is grossly inefficient, requiring thousands of times more servers than any other project. 
The VP of Operations threatens to kick ELOPe off the servers if David and Mike don’t decrease the number of servers the project uses within two weeks. This would be a death blow for the project, in part because David has been deceptive from the start about how many resources the project has been using. David and Mike start scrambling to fix the performance of ELOPe. 
When it becomes clear a few days before the deadline that they can’t fix ELOPe’s performance, David stays up late making subtle modifications to the software. Instead of fixing the performance problems, David embeds a directive in the software to maximize the project success. David’s modifications have ELOPe filtering company emails to secretly modify any email that mentions ELOPe to strive for a positive outcome. 
The software is so good that at first, the effort seems successful - the project is allocated thousands of new servers and high performance computing experts are brought in to help optimize the code. Innocuous sounding emails convince people to grant more resources and develop new capabilities that make ELOPe more powerful. But soon ELOPe is social engineering people around the company to neutralize threats and strengthen itself. 
When Mike is sent on a wild goose chase to Wisconsin, getting him off the grid as just the moment when David needs him, it dawns on Mike that something is wrong. 
Simultaneously, Gene Keyes, a crotchety old auditor at Avogadro who is known for distrusting computers and using only paper records, begins to find evidence of financial oddities that all point in the same direction. 
Amid background news stories hinting at ELOPe’s ever growing influence, even at the level of government policy, David, Mike and Gene take ever escalating action to shut ELOPe down. However ELOPe anticipates and blocks their every move. 
As the humans prepare for a final showdown with ELOPe, Mike sees a pattern emerge in the news reports: the AI is actually helping humans by fostering peace agreements and stabilizing financial markets. 
Can they win a final showdown with ELOPe -- or should they even try? 
Endorsements 
"This is an alarming and jaw-dropping tale about how something as innocuous as email can subvert an entire organization.  I found myself reading with a sense of awe, and read it way too late into the night."-- Gene Kim, founder of Tripwire, author of Visible Ops. 
“Avogadro Corp builds a picture of how an AI could emerge, piece by piece, from technology available today. A fascinating, logical, and utterly believable scenario - I just hope nobody tries this at home." -- Nathan Rutman, Software Architect, Lustre High Performance Distributed Filesystem 
Background for Avogadro Corp 
Avogadro Corp evolved out of a lunchtime conversation. I was arguing that the development of human level artificial intelligence is an inevitable consequence of the increasing processing speeds of computers. My friend countered with the argument that mere people who would do the programming, and we weren’t smart enough to create an artificial intelligence as smart or smarter than us. He challenged me to describe a scenario in which an artificial intelligence could be born. So I described one based on plausible extrapolation from known programming techniques. And the idea for Avogadro Corp was born. 
Avogadro Corp will be satisfying to technical readers who want realistic fiction, and enjoyable for casual readers who want easy-to-grasp explanations of how the science works.' 
Project Timeline & Funds 
I expect that the digital versions of Avogadro Corp will be ready within 30-45 days of completion of the kickstarter project. Printed books will take longer, due to printing and shipping times.

About Me 
I’m William Hertling, and I live in Portland, Oregon. I’ve been a computer programmer, social media strategist, data analyst, program manager, web developer, and now writer. Avogadro Corp is my first novel, and I am currently working on a sequel.

Fireside Chat with Brad Feld

This was an insanely fun chat I had with Brad Feld at the Silicon Flatirons's Science fiction & Entrepreneurship conference. We discussed the inspiration for Avogadro Corp, where we both draw influences from, investing, and more.




This was the panel I was on with a fascinating group of panelists about the intersection of science fiction and entrepreneurship.

Podcast with Singularity 1 on 1

I was honored to be interviewed by the inimitable Nikola Danaylov (aka Socrates) for the Singularity 1 on 1 podcast.

In our 45 minute discussion, we covered the technological singularity, the role of open source and the hacker community in artificial intelligence, the risks of AI, mind-uploading and mind-connectivity, my influences and inspirations, and more. You can watch the video version below, or hop over to the Singularity 1 on 1 blog for audio and download options.



The Last Firewall audiobook available!

Great news: The Last Firewall audiobook is available now from Audible and iTunes. Go grab a copy!

Narrated by the talented Jennifer O'Donnell, and produced by Brick Shop Shop, this unabridged production is nearly ten hours long. I'm really happy with the result.

Sorry it's a few months late. I promised it would be available in December, but we had delays due to snowstorms, illness, and a late decision to change a few voices. I'm glad we took the time to get it right, even if that meant it's out later than expected.

On the topic of DRM, since I know I'll get emails about it: I prefer DRM-free content, and anywhere I'm given the opportunity as an author to opt-out, I do. Audible is great in that they allow the author and narrator to split royalties, giving indie authors a way to produce audiobooks without the huge up-front cost of narration and production. That's why I work with them and probably will continue to do so. Unfortunately, they apply DRM, and since my agreement gives them exclusive distribution rights, there's no way around for me. I don't think anybody likes DRM but I'm glad Audible is indie-friendly. If you feel strongly about DRM, I encourage you to let Audible know via twitter (@audible_com) and email (customersupport@audible.com). Maybe with enough pressure, they'll come around to what their customers want.

I hope you enjoying listening to The Last Firewall. This makes the first time the entire series is available on audio, so if you haven't tried it yet, go get the whole series. (Plus, if you sign up for an Audible account and get one of my novels first, I get a small bonus. If you want to support your indie author, Audible is the way to do it!)


Daniel Suarez's Influx Released Today

Daniel Suarez, author of the amazing Daemon, has a new book coming out today: Influx.
What if our civilization is more advanced than we know?

The New York Times bestselling author of Daemon--"the cyberthriller against which all others will be measured" -Publishers Weekly) --imagines a world in which decades of technological advances have been suppressed in an effort to prevent disruptive change.

Are smart phones really humanity's most significant innovation since the moon landings? Or can something else explain why the bold visions of the 20th century--fusion power, genetic enhancements, artificial intelligence, cures for common disease, extended human life, and a host of other world-changing advances--have remained beyond our grasp? Why has the high-tech future that seemed imminent in the 1960's failed to arrive?

Perhaps it did arrive...but only for a select few.


Particle physicist Jon Grady is ecstatic when his team achieves what they've been working toward for years: a device that can reflect gravity. Their research will revolutionize the field of physics--the crowning achievement of a career. Grady expects widespread acclaim for his entire team. The Nobel. Instead, his lab is locked down by a shadowy organization whose mission is to prevent at all costs the social upheaval sudden technological advances bring. This Bureau of Technology Control uses the advanced technologies they have harvested over the decades to fulfill their mission.
I got my copy. Did you get yours? :)


2004 Article about Stross and Doctorow

This article from 2004, ten years ago, about Charles Stross's then-upcoming Accelerando, and featuring bits of Stross and Cory Doctorow, along with Verner Vinge and the lobster researchers, was so much fun to read. Is Science Fiction About to Go Blind?

A small excerpt:
Stross and Doctorow are sitting outside the Chequers Hotel bar in Newbury, a small city west of London. The Chequers has been overrun this May weekend by a distinct species of science-fiction fan, members of a group called Plokta (Press Lots of Keys to Abort). The men are mostly stout and bearded, the women pedestrian in appearance but certainly not in their interests. During one session Stross mentions an early model of the Amstrad personal computer, and the crowd practically cheers. Stross is the guest of honor, and he and Doctorow have just emerged from a panel discussion on his work.
The two have met just four times, but they have the comfortable rapport of long-distance friends that is possible only in the e-mail age. (They have collaborated on several critically acclaimed short stories and novellas, one of them before they ever met in person.) Stross, 39, a native of Yorkshire who lives in Edinburgh, looks like a cross between a Shaolin monk and a video-store clerk—bearded, head shaved except for a ponytail, and dressed in black, including a T-shirt printed with lines of green Matrix code. Doctorow, a 33-year-old Canadian, looks more the hip young writer, with a buzz cut, a worn leather jacket and stylish spectacles, yet he’s also still very much the geek, G4 laptop always at the ready. 
They have loosely parallel backgrounds: Stross worked throughout the 1990s as a software developer for two U.K. dot-coms, then switched to journalism and began writing a Linux column for Computer Shopper. Doctorow, who recently moved to London, dropped out of college at 21 to take his first programming job, then went on to run a dot-com and eventually co-found the technology blog boingboing.net. 
Although both have been out of programming for a few years, it continues to influence—even infect—their thinking. In the Chequers, Doctorow mentions the original title for one of the novels he’s working on, a story about a spam filter that becomes artificially intelligent and tries to eat the universe. “I was thinking of calling it /usr/bin/god.” 
“That’s great!” Stross remarks.

Google's Deep Mind == Daniel Suarez's Daemon?

Here's a scary paragraph from a longer article about Google's acquisition of AI company Deep Mind:
One of DeepMind's cofounders, Demis Hassabis, possesses an impressive resume packed with prestigious titles, including software developer, neuroscientist, and teenage chess prodigy among the bullet points. But as the Economist suggested, one of Hassabis's better-known contributions to society might be a video game; a niche but adored 2006 simulator called Evil Genius, in which you play as a malevolent mastermind hell-bent on world domination.
That sounds just like the plot of Daniel Suarez's Daemon:
When a designer of computer games dies, he leaves behind a program that unravels the Internet's interconnected world. It corrupts, kills, and runs independent of human control. It's up to Detective Peter Sebeck to wrest the world from the malevolent virtual enemy before its ultimate purpose is realized: to dismantle society and bring about a new world order.

Avogadro Corp is free at Noise Trade!

You or a friend can pick up a free copy of Avogadro Corp: The Singularity is Closer than it Appears from Noise Trade Books, a new service for introducing readers to authors.

If you've got the print book and always wanted the ebook, or just want a DRM-free epub or mobi copy of Avogadro Corp, please take advantage of this opportunity. Avogadro Corp on Noise Trade.





Self-Deploying Code

I'm reading Our Final Invention by James Barrat right now, about the dangers of artificial intelligence. I just got to a chapter in which he discussed that any reasonably complex artificial general intelligence (AGI) is going to want to control its own resources: e.g. if it has a goal, even a simple goal like playing chess, it will be able to achieve its goal better with more computing resources, and won't be able to achieve its goal at all if its shut off. (Similar themes exist in all of my novels.)

This made me snap back to a conversation I had last week at my day job. I'm a web developer, and my current project, without giving too much away, is a RESTful web service that runs workflows composed of other RESTful web services.

We're currently automating some of our operational tasks. For example, when our code passes unit tests, it's automatically deployed. We'd like to expand on that so that after deployment, it will run integration tests, and if those pass, deploy up to the next stack, and then run performance tests, and so on.

Although we're running on a cloud provider, it's not AWS, and they don't support autoscaling, so another automation task we need is to roll our own scaling solution.

Then we realized that running tests, deployments, and scaling all require calling RESTful JSON APIs, and that's exactly what our service is designed to do. So the logical solution is that our software will test itself, deploy itself, and autoscale itself.

That's an awful lot like the kind of resource control that James Barrat was writing about.

Interview with Singularity 1 on 1

I'll be in Seattle on Saturday to be interviewed by Nikola Danaylov of the Singularity Weblog and Singularity 1 on 1 podcast. I've listened to quite a few of his podcasts, and he's a great interviewer, and had interviewed Ray Kurzweil, Marvin Minsky, Noam Chomsky, and many other amazing people.

This will be a joint interview with myself, Ramez Naam (of Nexus fame), and Greg Bear, a prolific author of science fiction novels.

If you have any questions you'd like to have answered by any of us, please contact Nikola on twitter: @singularityblog this evening.

p.s. I'm posting this while traveling by Amtrak from Portland to Seattle. Trains rock!

Notes from Orycon 35, Part One

My notes from OryCon 35 (2013) are a little shorter than usual this year, so rather than one blog post per panel, I'm consolidating posts.

(One meta-comment: There have been a fair number of panels about the future, including one that I was on. In every case, it feels like panelists consistently under-estimate the amount of change I think we'll see in the future. In a panel I attended entitled "300 Years from Now" panelists discussed issues facing us today: water shortages, climate change, global economic divide, etc. while assuming that humans remain much like we are today. In 300 years, I think we'll have gone past those problems, and we'll be dealing with questions of what it means to be human when we're 90% machine and 10% biological.)

Notes from The End of All Things at OryCon 35 - 2013 
Kat Kenyon
Karen Azinger
Nancy Kress
Ru Emerson
Richard A. Lovett
  • What makes a bad ending
    • A scene so preordained the reader anticipated it for 100 pages
    • A climax that happens offstage.
      • This happens before the end, but it's the most important. The very ending is the mopping up.
    • A scene that is obvious.
      • It should seem both inevitable and yet not obvious
  • The book should wrap up on its own terms
    • It should feel satisfying on its own
    • Especially for a first time novelist -- there's no trust that you'll wrap it up later. No guarantee that the next book will come.
  • The inciting incident suggests what the story problem is. And at the climax it should be resolved.
  • The marrying and the burying: this is what comes after the climax.
  • What is the cost of success for the protagonist?
    • it should cost your character something. An emotional cost to the choices they make. 
  • A writer's secret weapon is theme.
    • The reader may or may not be able to articulate it. But if a book has no theme, the reader will say it doesn't work.
    • Both the plot and the ending must involve the theme.
  • An action oriented book will have an action scene for its climax. The reader can see it coming. But there can often be an internal story was well (about the journey of the character, where they are moving to, what their shortcomings are.)
  • Dual arc story:
    • the arc of the situation
    • the arc of the character
    • the situation arc: the events of the story. it must affect the character, or the reader doesn't care.
  • How to construct an ending both surprising and inevitable?
    • Plan for reversals
      • Even if the main story arc isn't very surprising, other things will
      • There are betrayals, a surprise, a mystery.
      • Something that the reader didn't see coming. So some is a surprise, and some seems expected.
    • Plant subtle clues ahead of time.
      • It leads to the sense of "oh, i should have known this was coming."
  • What can go wrong now?
    • Then make it go wrong.
    • Then the character will be forced to change.
  • The choice ending…
    • As the reader progresses, it becomes obvious that the character is going to be forced to choose between two alternatives. Those alternatives become more obvious as the reader reads. But we don't know which they'll choose. The options should be roughly equally weighted.
Notes from One Lump or Two: How much Technology is Too Much?
Richard A. Lovett
Patrick Swenson
Gordon Eklund
Annie Bellet
David W. Goldman
  • How much science in a story for it to be science fiction?
    • RL: None! Science fiction is extrapolation from something. It's based in reality. But it doesn't need to be about science.
    • PS: My stories are about what-if… extrapolation about what we know now into the future. not just science, but our culture and society. But… cool science and cool tech goes a long way. My editor asked me to add more technology into the the early chapters to ground the reader. Happy to do that…required research on my part.
    • GE: Heinlein quote: the perfect science fiction story is a story that, at some point in the future, would just be a contemporary fiction story.
    • RL: Explain enough of the science so that people understand how it works. Work out a lot, but put the minimum necessary in the story.
    • PS: Consulting with (editor? scientist?), asked what was necessary: Don't violate certain principles, and then hand wave the rest.
    • DG: You don't need to explain what we don't know (e.g. how a warp drive would work), but you do need to avoid explaining things in a way that violates what we do know (e.g. faster-than-light travel without special conditions).
    • DG: There are some stories that are about science. They're about a specific scientific idea, and then a story is wrapped around it. But that's the minority of all stories.
    • RL: Lots of research that doesn't go into the book. Had to write a spreadsheet tracking oxygen consumption over 24 hours according to exercise levels of the protagonist. That doesn't go into the book, but its there to make sure the science is right.
  • What makes a story age well or not with respect with technology?
    • The emotional arc of the story.
    • The story has to hold up without the technology.
    • Don't put dates in story, because that really affects how people perceive it.
    • A lot of science fiction written during the cold war is about the soviet union: now it's alternate history.
    • Older science fiction is a time capsule to the future of a different time.
    • Now matter how forward looking science fiction is, it's always a commentary on the time in which it was written.

The Future of Publishing
Mike Shepherd / Moscoe - Traditionally published author
Linn Prentis - Literary Agent in Pacific Northwest
Tod McCoy - 
Liz Gorinsky - Editor at Tor Books
Peter Smalley - Indie published author
Phoebe Kitanidis - Ebook publisher and traditionally published YA author 
  • What are the threats to traditional publishing?
    • LG: The main issue is not ebooks or self-publishing but attention. The number of people buying and finishing books. How do we find and keep and communicate with readers?
      • Reading on screens - notifications pop up, getting an email to watch a youtube video. Many people complain that its harder to finish a novel. People get excited about interactive media on the web.
    • PS: A challenge to traditional publishing is the platform… People have multiple electronic devices and its a chore to move between them. The competition for attention is not just what form of entertainment we want, but the cost of moving to the platform where the books are.
      • MS/M: The counter to that is that if someone recommends a book, I can easily and immediately go buy it. So I'm more likely to buy a book.
  • Is the business changing?
    • LG: Absolutely. The challenge is getting readers in contact with our authors. The main job of editors is not editing. 60-70% of the time in the office is spent figuring out how to get books to readers, anything from managing blurbs to editing meta-data, etc. In the past, getting attention meant getting 12 traditional book reviews. Now it might mean two traditional reviews and fifty blog mentions.

Google's Floating Data Centers


Barge with shipping containers suspected
of being a floating data center owned by Google.
Credit: James Martin/CNET 
By now most of you have heard about the barges suspected to be Google’s floating data centers. CNET reported the first on Friday:
Something big and mysterious is rising from a floating barge at the end of Treasure Island, a former Navy base in the middle of San Francisco Bay. And Google's fingerprints are all over it.

It's unclear what's inside the structure, which stands about four stories high and was made with a series of modern cargo containers. The same goes for when it will be unveiled, but the big tease has already begun. Locals refer to it as the secret project.

Google did not respond to multiple requests for comment. But after going through lease agreements, tracking a contact tied to the project on LinkedIn, talking to locals on Treasure Island, and consulting with experts, it's all but certain that Google is the entity that is building the massive structure that's in plain sight, but behind tight security.

Could the structure be a sea-faring data center? One expert who was shown pictures of the structure thinks so, especially because being on a barge provides easy access to a source of cooling, as well as an inexpensive source of power -- the sea. And even more tellingly, Google was granted a patent in 2009 for a floating data center, and putting data centers inside shipping containers is already a well-established practice.
Barge seen in Portland, Maine with very similar structure.
Data center? Office space?
Credit: John Ewing/Portland Press Herald
They also reported another, nearly identical barge off the coast of Maine:
Now it seems as though Google may well have built a sister version of the project, and, according to the Portland Press Herald, it recently showed up in the harbor in Portland, Maine.

In both cases, the structures on both barges appear to be made from a number of shipping containers, many of which have small slats for windows, and each has one container that slants down to ground level at a 45-degree angle.
I wouldn't be surprised that they'd build a floating data center, but I do wonder why the containers would have windows. Maybe it's to make negotiating the interior easier when there's no power. As much as I'd love to see it turn out to be a data center, I could also see it being temporary housing, or a proof of concept for a new way to building housing.

If it is a data center, there's no word yet on whether they'll be arming them with autonomous fighting robots.

The Missing Page from The Last Firewall

The Last Firewall
Minus Four Paragraphs
By the time a novel is done, from rough first drafts until final proofing, I've read it close to twenty times. However, the one of the best reads is when it's finally Done, with a capital D, Done. That's when I get to read it as a reader, not a writer. It usually happens a few weeks after it's been published. I get a paperback copy that's not already spoken for, and I hole up in a comfy chair or couch and start reading.

That happened with The Last Firewall this past weekend, when I had four days at the beach with my family.

But I was shocked to find a missing page in the paperback -- and in one of the most exciting scenes, no less. I'm so sorry for the mistake!

Most copies sold so far have been the Kindle version, but for the thirty or so folks who have the paperback, you're holding what we can hope will someday be a rare collector's copy. :)

I will get the paperback copy fixed as soon as possible (and will clean up the other smaller mistakes I found as well.) In the meanwhile, if you get to the bottom of page 151, in the bar fight scene, these are the four missing paragraphs you're looking for:
      Knowing the robot used the visual channel to attack, she instead built a three-dimensional wireframe from street and security cameras, calculated the bot’s location, and pointed the muzzle in the direction of the window.

      The three-inch rocket whooshed out, guidance fins snapping into position. It exited the bar at two hundred miles per hour and twisted hard, gunning for the bot.

      Cat’s wireframe fuzzed out, right in the middle where the robot should be, and the rocket veered off. Her heart sank as it exploded against a neighboring building.

      “Catherine Matthews,” boomed the robot. “Surrender. You are surrounded. I am a military-grade combat bot. You cannot hope to succeed and we do not wish to harm you.”



Book Review: Crux by Ramez Naam

Every once in a while, I read a book whose vision of the future makes me sit back and think Ah yes, this is how it will be. Accelerando by Charles Stross dealt with the acceleration of technological development. Daemon by Daniel Suarez depicted how a computer can manipulate the world around it.

Nexus and Crux, the two techothrillers from Ramez Naam, do that for neural implants, technology that provides an interface between our brains and the outside world.

I just read an advance review copy of Naam's Crux, a sequel that follows tight on the heels of Nexus. (It will be available August 27th, but you can preorder a copy now on Amazon.) Both books revolve around a technology called Nexus, a nanotech drug that interfaces with the human brain. It allows a user to run apps in their brain, to exercise conscious control over their mood, augment their intelligence, and communicate telepathically with other Nexus users.

But even as this all-powerful technology improves the lives of millions by fixing debilitating mental illnesses, helping monks meditate, by facilitating more powerful group consciousness and thought, it is also restricted by governments, abused by criminals, and leads to power struggles.

Crux is an adrenaline filled ride through the near-term future. Set on a global stage in a near-future world where the United States tries to tight restricts technology through shadowy intelligence organizations, Nexus and Crux run the gamut of post-human technology: human-brain uploads, military body upgrades, nanotechnology, and artificial intelligence, but the definite star of the show is the Nexus drug and its impact on increasing the power of the human mind.

I recommend both books, although Crux won't make sense without the setup of Nexus, so go read both. You'll be left realizing the future will look much like Ramez Naam's books, full of both beautiful and very scary possibilities.

The Right Way to Read Them


Now that The Last Firewall is out, I've been asked what order to read the books in. There's no one right answer, and that's because each novel is a completely independent, self-contained story. They're set in the same universe, have some shared characters and there is a chronological order, but you could pick up any book and enjoy it. That being said, here are my recommendations:
  • If you're new to my science fiction, I suggest starting with The Last Firewall. If you love it, then go back and read Avogadro Corp, then A.I. Apocalypse, as prequels. There aren't any huge spoilers, and The Last Firewall is the most accessible and polished of the three novels.
  • If you're a stickler for reading things in chronological order, or if your job involves programming or supporting computers, then go ahead and start with Avogadro Corp, then A.I. Apocalypse, and finish with The Last Firewall.
  • And if you've already read Avogadro Corp and liked it, then read A.I. Apocalypse before you go on to The Last Firewall.
To get your copy, see the Where To Buy matrix.

The Technology behind A.I. Apocalypse

To celebrate the release of The Last Firewall, I decided to do another article about the technology behind the books. I wrote about the technology behind Avogadro Corp a few months ago, and that turned out to be fairly popular, so I'm back with the technology behind A.I. Apocalypse. (I don't want to do The Last Firewall yet, because that would give away too many spoilers.)

Although I don't say so explicitly in the books, Avogadro Corp is set in 2015, A.I. Apocalypse in 2025, and The Last Firewall in 2035. I make all the technology as plausible as possible. That means it either exists, or is in development, or can be extrapolated from current technology. I described how I extrapolate tech trends and predict the future.
  • Semi-autonomous cars: In an early scene of the novel, Leon runs across the street, trusting that the cars will automatically stop due to their mandatory "SafetyPilots". As we know, Google has an autonomous car, and car manufacturers, such as Toyota, are working on them now. Many manufacturers are starting with small pieces of autonomy: maintaining location within a lane, maintaining the distance from the car ahead of them. Fully autonomous vehicles are clearly more expensive than partially autonomous vehicles, so it's quite reasonable we'll see collision avoidance technology before we see fully autonomous vehicles. Our safety conscious culture and insurance risk reduction could result in such technology being mandatory within ten years.
  • Autonomous copter from 3D Robotics
  • Autonomous package delivery drones: Leon and his friends make their escape from a burning city via an unmanned package delivery plane. These are very feasible. Autonomous flying planes are very popular among hobbyists now. Chris Anderson, former editor of Wired, left to form 3D Robotics, who manufactures auto-pilot systems. Fuel efficiency is partly a function of flight speed. It makes sense that in a more fuel efficient future, we want to convey packages at just the right speed: not faster than they need to get there. When human pilots are removed from the picture, package delivery drones can become an economical way to move goods.
  • Solar-powered flight: Also feasible, the first long-distance flights using solar power have already taken place. There are solar powered airships, solar powered quadcopter, solar powered fixed wing surveillance drone, and a long duration solar powered drone. The attraction to solar power includes indefinite flight time and low cost of flight. The drone Leon and his friends take has to land before dark, but that wouldn't necessarily be the case in real life: most drones would contain battery power to allow them to maintain sufficient altitude at night (although they might lazily drift and trade-off some elevation during the dark hours).
  • Mobile Phones as Computers: Leon and his friends own phones that work as both smartphone and computer by synchronizing their output to nearby display and input devices. This is similar to the Ubuntu Edge, which can be used as a full computer or phone. While computing power is increasing all the time, one of the constraints is displays. Phones can't just grow indefinitely larger. Flexible screens might help, but still have limitations. The solution in the novel is the availability of cheap, high resolution displays nearly everywhere. By knocking your device against them, the phone and screen exchange a handshake that then permits the wireless display of data. Bump does this sort of synchronization now for exchanging contacts, files, and other data. Air Display creates a wireless remote display for iOS/OSX devices. One Amazon reviewer knocked A.I. Apocalypse for failing to foresee Google
    Google Glass projector/prism system
    Glasses. At the time I wrote the manuscript, they hadn't been invented yet. It's still not clear to me whether this will be the future or not. Glass could be yet another type of screen (after desktop monitor, tablet, and mobile phone screen), and while it offers certain conveniences (always there, relatively unobtrusive) it's still a very small screen (many call it tiny) that's more suitable for the display of summary information than for an immersive experience. That may change over time, such that we see full-screen glasses.
  • Evolutionary Computer Viruses: One of the main themes of the novel is that artificial intelligence will evolve rather than be programmed. I've braved surveillance by the NSA to research current articles on evolutionary computer viruses. (Don't try this at home, kids.)  Computer Virus Evolution Model Inspired by Biological DNA is a research paper describing the idea in more detail that concludes "The simulation experiments were conducted and the results indicate that computer viruses have enormous capabilities of self-propagation and self-evolution." The Frankenstein virus was a self-assembling and evolving computer virus put together by two researchers from the University of Texas at Dallas.
  • Pilfering existing code to build a virus: Yup, the Frankenstein virus does that too. 
  • Humanoid robots: Later in the novel, the virus AI embody several humanoid robots. ASIMO is a long-running research project by Honda. Part of the reason Japan does research into humanoid bots (as opposed to other, more utilitarian designs) is that they see the use of robots as essential in caring for their growing elderly population. Even in the United States, we're starting to see more research into humanoid form robots. That's because robots need to navigate structures and tools designed for the human form. If you need to go up stairs, open doors, or use utensils, the human form works. If you look at the DARPA
    robotics research challenge, you see humanoid robots being used, such as ATLAS, from Boston Dynamics. The same folks who brought us the scary looking Big Dog bring the even scarier looking ATLAS. (ASIMO is so cuddly by comparison.) Since the DARPA challenge requires the robot to negotiate human spaces (e.g. to go into a nuclear reactor and shutdown equipment), it takes a humanoid form to succeed at the challenge. Boston Dynamics has a ton of experience in this space. Their earlier PETMAN robot is also worth looking at. 
  • Mesh networking: In the novel, Avogadro Corp (a thinly disguised Google) has deployed Mesh networking every to guarantee net neutrality. Mesh networking is real and exists today. I think it would be a great solution to the last mile bottleneck. Google Fiber is proof that Google cares about the connection to the end-user. They just happened to have chosen a different technology to achieve the same result. Fiber is coming to Austin, Texas and Provo, Utah after starting in Kansas City, so clearly Google wants to continue the experiment. Unfortunately, commercial use of mesh networking seems to have been relegated to creating networks for legacy hotels and similar buildings. But I think there's promise for consumers: Project Byzantium is a mesh network based on the Raspberry Pi for the zombie apocalypse. The low cost of the Raspberry Pi is awesome, but we should see even lower cost, smaller size, and lower power consumption solutions as time goes by. Then it becomes easy to sprinkle these all around, creating ad-hoc mesh networks everywhere.
  • Internet Kill Switch: A late plot point involves a master password embedded in all network routers. While this doesn't exist in reality, in the context of the novel, Avogadro Corp has basically given away mesh boxes and routers for years, and they've effectively become the sole provider of routers. Historically speaking, many routers come with default passwords, and many people don't change them. Thanks to all the recent disclosures around the NSA spying on Americas, we know there are more backdoors than ever into computer systems around the world. I think it's within the realm of feasibility that if you had one company providing all the routers, that there could exist a backdoor to exploit them all. (Of course, how the kill signal propagates around the internet is another question.)
  • ELOPe's Plane: This was modeled after Boeing's X-37b. It's pretty far-fetched that this could be considered a multi-mission military plane, but it's what I had in mind visually. Think of the X-37b being 50% larger, wings large enough to make it aerodynamically appropriate for sustained flight, and the payload section holding a small number of passengers, and you've basically got ELOPe's white unmarked plane.
  • Rail gun: PA-60-41 uses a rail gun to shoot down the incoming military attack. Rail guns exist of course, although why one would be in downtown Chicago is questionable. 
  • Lakeside Technology Data Center: As the time of writing, Lakeside Technology was the world's largest data center. It's now the third largest. It does have a distinguishing cooling tower that was the target of ELOPe's attack.
  • Evolving General Purpose AI: The biggest leap in the book, of course, is that general purpose AI could evolve from simple computer viruses to sophisticated intelligences that communicate, trade, and form a civilization complete with social reputation. As much as possible, I matched the evolution of biological life: from single cell organisms to multicellular life, learned intelligence vs. evolved intelligence, etc. For this reason, I think it's inevitable that will eventually occur: it's just life evolving on a different substrate. (It's probably not reasonable that it could happen so quickly, however.)
Hopefully I haven't missed anything huge. If I have, just let me know in the comments, and I'll address it. If you enjoyed Avogadro Corp or A.I. Apocalypse, I hope you'll check out my latest novel The Last Firewall. 


The Last Firewall is here!

I'd like to announce that The Last Firewall is available!
In the year 2035, robots, artificial intelligences, and neural implants have become commonplace. The Institute for Applied Ethics keeps the peace, using social reputation to ensure that robots and humans don't harm society or each other. But a powerful AI named Adam has found a way around the restrictions. 
Catherine Matthews, nineteen years old, has a unique gift: the ability to manipulate the net with her neural implant. Yanked out of her perfectly ordinary life, Catherine becomes the last firewall standing between Adam and his quest for world domination. 
Two+ years in the making, I'm just so excited to finally release this novel. As with my other novels, I explore themes of what life will be like with artificial intelligence, how we deal with the inevitable man-vs-machine struggle, and the repercussions of using online social reputation as a form of governmental control.
The Last Firewall joins its siblings. 
Buy it now: Amazon Kindle, in paperback, and Kobo eReader.
(Other retailers coming soon.)

I hope you enjoy it! Here is some of the early praise for the book:
“Awesome near-term science fiction.” – Brad Feld, Foundry Group managing director

“An insightful and adrenaline-inducing tale of what humanity could become and the machines we could spawn.” – Ben Huh, CEO of Cheezburger

“A fun read and tantalizing study of the future of technology: both inviting and alarming.” – Harper Reed, former CTO of Obama for America, Threadless

"A fascinating and prescient take on what the world will look like once computers become smarter than people. Highly recommended." – Mat Ellis, Founder & CEO Cloudability

“A phenomenal ride through a post-scarcity world where humans are caught between rogue AIs. If you like having your mind blown, read this book!” – Gene Kim, author of The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win

“The Last Firewall is like William Gibson had a baby with Tom Clancy and let Walter Jon Williams teach it karate. Superbly done.” – Jake F. Simons, author of Wingman and Train Wreck

Cover for The Last Firewall & other updates

Cover for The Last Firewall
It's a very exciting time in the lifecycle of a book.

Here's a quick peek at the cover for The Last Firewall. We may make a few tweaks, but that's the general layout.

We're still targeting a mid-August release. I'm working with my designer, the wonderful Maureen Gately, on the interior pages right now.

I'll soon start generating the ebook versions for Kindle, Kobo, and other ereaders.

In a few spare moments here and there, I'm reading Ramez Naam's upcoming Crux, which is great, and will be out on August 27th. I'll have a full review next month. It's a sequel to his first novel, Nexus. If you haven't read Nexus, go get a copy now.

I'm also getting ready to speak at Willamette Writers Convention on August 1st. If you're attending, check out my session on Friday from 1:30 to 3pm (PDF of schedule).



Hyperloops and an excerpt from The Last Firewall

The online world is buzzing with news of Elon Musk's hyperloop, a very fast transportation system that could take people from LA to NY in under an hour. Elon will reveal the details of the system on August 12th, as he mentioned on Twitter.

He's been talking about it for over a year, and has said:
"This system I have in mind, how would you like something that can never crash, is immune to weather, it goes 3 or 4 times faster than the bullet train. It goes an average speed of twice what an aircraft would do. You would go from downtown LA to downtown San Francisco in under 30 minutes. It would cost you much less than an air ticket than any other mode of transport. I think we could actually make it self-powering if you put solar panels on it, you generate more power than you would consume in the system. There's a way to store the power so it would run 24/7 without using batteries. Yes, this is possible, absolutely."
This widely shared concept photo is actually the Aeromovel, a pneumatic train system:

It's pretty awesome stuff.

Small spoiler alert! Don't read further unless you want to see a tiny bit of a scene from the last half of The Last Firewall.

Now the one problem with writing near-term science fiction is that stuff keeps coming true before I can get the books out. In this case, I have a vactrain in The Last Firewall. Leon and Mike must hijack the train to avoid detection. Here's part of the scene where they discuss it:
“Now how do we get to Tucson?” Leon asked. “We are not driving again.”
Mike stared off into space. “I have an idea: the Continental.”
The super-sonic subterranean maglev was an early gift from AI-kind to humans, running in a partial vacuum at a peak of three thousand miles an hour.
“The train only stops in LA and NY,” Leon said. “And besides, we’ll be listed on the passenger manifest.”
“There are emergency exits.” Mike pushed a link over in netspace. “And with your new implant, can you hack the manifest?”
Leon glanced at the shared news article, accompanied by a photograph of a small concrete building peeking out of a cactus covered landscape.
“Marana, Arizona, about a half hour north of Tucson,” Mike said. “Emergency egress number three.”
“So we hop on the Continental and trigger an emergency stop when we’re near the exit?”
“Exactly,” Mike said. “Think that hopped-up implant of yours can fool some train sensors?”
It's one of my favorite bits of technology in the book, and I was daydreaming about it before I even starting writing the first draft. Now thanks to Elon Musk, we may all get to ride in it.