Boat Hacking and Gonzo Engineering
April 24, 2011
Much of what has driven my complex technomadic projects since 1983 is publishing the ongoing narrative, and there have been stories ranging from the insanely geeky to the deeply terrifying… with a whole spectrum in between. And this creates a challenge.
There are three clear extremes in this unfolding tale, and blending them into a single thread (like a blog) doesn’t work. We really need separate publishing vehicles:
- The real-time technical narrative of the project with all its gonzo engineering, variations, puzzles, amusing interludes, geeky noodling, pointers to resources, and direct reader interaction. By definition, some of this is completely wrong, because we learn and make corrections as we go.
- Technical monographs about completed systems, well documented as stand-alone publications, with enough detail to clone (or at least fully understand) a design or set of techniques. These should have a shelf life of many years, and not be cluttered with unrelated material. Depending on the subject, these can be eBooks or hard-copy publications.
- A friendly collection of stories that are of interest to a wide audience, covering everything from system integration to geek adventure… but not terribly detailed.
Over the past three decades, I’ve taken a variety of approaches to solving this problem… generally finding that email updates to a mailing list work well at one extreme, with books and articles at the others. About ten years ago, available publishing tools went through some major changes, so like everyone else, I started blogging.
The problem with that is that it is not what we used to call “push technology” – I don’t know about you, but I am constantly forgetting to read the latest blog posts from interesting friends (even with RSS; I’m just in constant information overload). Blogs are superb for parking stuff on the web with a nice graphic flow of photos and linky goodness, but… except for die-hard fans… they are not ideal for staying in touch with a community.
From 2011 to 2013, I produced what I thought was the perfect solution: a magazine-style PDF series that was available by subscription for $20/year. These were lovingly polished, and I ended up publishing 22 issues totaling about 200 pages of material (the 192-page compilation book is in my store). I am very happy with the results, though it was a LOT of work.
But deadlines came (and went!) without regard for the status of the projects, and dated issues don’t work well as stand-alone publications (single systems span multiple articles). I started to find them a burden, and announced an end to the series in April of 2013. Yet the readers are there, still just as curious, and a lot is going on at Nomadic Research Labs. What to do?
The answer is embedded in those bulleted points up the page a bit, so here’s what I now have to offer if you’re interested in following these adventures in geek expressionism:
- Free subscription to email Nomadness News updates (random intervals), with a relaxed technical style. These assume that the reader is pretty much on board with the ongoing project, and thus do not spend time on context-setting or attempts to be comprehensive. During the Microship era, I posted a couple hundred issues of something much like this, with a mailing list that reached 4,500 before the project wound down.
- Blog which is right here, and gets updates at random intervals presenting current projects, adventures, random tales, favorite bits of gizmology, noodlings, and all that other bloggy goodness.
- Boat Hacking Collection of stand-alone eBooks about single, well-defined projects or techniques. These are designed to be much more useful than “Issue #n of something,” and will include schematics, software listings, detailed parts lists, how-to material, and so on. A la carte prices will vary.
Publications are what keep this project going, so I will make sure to keep cranking out amusing nautical geekery as we build the starship Nomadness!
NOTE: As with any vintage forward-looking statements, some of that didn’t happen!
You must log in to post a comment.