Bio: I've been a science fiction fan for as long as I can remember. Some of my fondest childhood memories involve discovery of H. G. Wells, Jules Verne, the Heinlein juveniles, and Golden Age SF anthologies. (That said, my interests were never limited to SF. I've always been an avid reader of history and science. I recall fondly a minor childhood illness that provided the time to read a lengthy history of Rome.)
Young visions of becoming literally a rocket scientist morphed into a degree in physics. Mid-degree, I had an epiphany: I was good at physics-but intuitive with computers. I completed the physics program and went straight on for a masters in CS. Physics was a terrific foundation for my newly chosen field-and later on, of course, for writing SF.
My computer career began at Bell Labs, where my assignments dealt with telephone switching systems and design for ultra-reliability. I moved to Honeywell, entering engineering management and an evening MBA program. The work at Honeywell involved automated building controls, real-time systems for which my Bell Labs training was tremendously valuable.
Completion of the MBA brought an unexpected "problem": evenings and weekends to call my own. Suddenly, there was more time than I'd had in years for recreational reading. With more to read, I found much to criticize. My wife, Ruth, eventually suggested that if I thought I could do better, I should.
And so, circuitously (pun intended), began my writing career �
Significant traces of my Bell Labs and Honeywell experience appear in my first novel, but what's most interesting in hindsight is how Probe foreshadowed my later career. By the time Probe appeared in print, I had changed employers, and my state of residence, twice. I was then newly arrived at Hughes Aircraft, one of a team chasing a large NASA contract. (We won.) While NASA personnel and settings play key roles in Probe (about which I'll say only that it opens as a first-contact novel), it was completed before my first NASA encounter.
I never met any rocket scientists, but I did spend several fascinating years developing parts of the Earth Observing System (NASA's third-largest effort, after the space station and the shuttle). I got to know an astronaut. I even flew the shuttle training simulator twice, which was great fun. (Fortunately it was a simulator � I never got it back onto the "ground" in one piece.)
The downside of NASA contracting was its impact on my writing. I squeezed in time for some short stories, two of which appeared in Analog. As my engineering management career took off (I admit it: the pun is always intended), there was little room for hobbies. On the plus side, the next several years-in which few words of fiction were committed to electrons-produced a stockpile of source material for future stories.
I eventually left Hughes to explore the alien worlds of start-ups and the Internet bubble. 1999 found me restless in my day job. A sabbatical spent writing recharged my batteries-and produced a flurry of story sales (to Analog and Artemis).
After a few more years in engineering and project management -- more telecom and government contracting work -- I decided it was time to take the plunge. I'm now writing full time.
I like to think my technical background lends realism and depth to my fiction. Of course I like to think that Windows won't require daily rebooting, that Ed McMahon will come through with the check he keeps teasing me about, and that chicken-fried steak is a health food. Perhaps you should sample my writing and form your own opinion �
Computing is mere decades young, a set of technologies we have scarcely begun to develop. It's already been quite a ride. Now: Imagine every gadget around you becoming ever faster, cheaper, tinier, more interconnected, more intelligent ... especially more intelligent. The stories in Creative Destruction explore what we could face in the next half century or so: artificial intelligence, malicious software to makes us nostalgic for mere viruses, ever-more-perfect virtual reality, direct neural int... more info>>