Jesse Pinkman: "It's SCIENCE, B*tch!"

Lesley and I have been crossing a lot of bridges lately. (I mean the literal kind, not the metaphorical ones.) First in our trailer and now in our motorhome, we've been doing a lot of driving throughout the Pacific Northwest and Northern California, and there's plenty of water here—entire oceans of it, in fact. And where there is water, there are—not surprisingly—bridges to enable us to cross that water.

Early on, this was nerve-wracking. Towing a 19' trailer across a bridge with a fairly small Chevy pickup truck, trying to stay in the middle of what seemed a terrifyingly narrow lane was, at first, pretty scary—especially if the wind was up. We eventually got used to the feeling of being suspended on this thin concrete-and-steel lifeline hundreds of feet above the water, dragging all of our worldly goods behind us. Eventually, we got to the point where we could cross a bridge, even a narrow one, without giving it too much thought. Now we do the same thing in a somewhat larger motorhome. And, as expected, it was frightening at first, but eventually became second nature. Other than making sure that it’s not too windy, we now cross bridges without giving the crossing a second thought.

But even at our most terrified, one thing we never worried much about was the integrity of the bridge itself. We might veer off of the bridge, or be blown off of it, or be pushed off by a trucker who'd lost his brakes or been blown into another lane, but we never thought, "Oh, my God! What if the bridge falls down?!" Circumstances might intervene to do us damage, but the bridge itself would stand, we could be pretty sure.

Sometimes the "guarantee" is implied by a sign that you can
see before you get on the bridge itself. (Image in the public
domain.)

That's because bridges are engineered. And with only a few exceptions, they are well engineered, designed by men and women who understand both physics and structural engineering. These people are civil engineers and architects, experienced designers who know how materials will react to a given amount of stress and to the wear and tear of wind and weather and traffic. How do they know? They know because they hypothesize and calculate and test and revisit the original hypothesis, all while taking into account the known properties of various materials. As Aaron Paul's Jesse Pinkman said so eloquently on Breaking Bad, "It's science, Bitch!"

Bridges are usually massive and are guaranteed to carry a certain amount of traffic. The Yaquina Bay Bridge, which we cross almost every week, was built in 1936, one of a series of bridges designed by Conde B. McCullough. It is over 3,000 feet in length, and it stands 133 feet above the water at its highest point. It contains 30,000 cubic yards of concrete and over 3,000 tons of steel. As I said, massive. (And this bridge is quite small compared to many other suspension bridges around the world.) And because it's so substantial and so well-designed, the bridge is guaranteed to be able to hold the weight of the traffic crossing it.

Sometimes the "guarantee" is fairly explicit, as in the

case of the Clark's Bridge, a covered bridge in New

Hampshire, which specifically states that it will carry

200 tons. (Image  licensed under the Creative

Commons Attribution-Share Alike 3.0 Unported

license.)

Which brings us to software. 

When I was heading up the software development team for a publishing company in Texas, the powers-that-be (of which I was most assuredly not one) decided that all of our programmers would be given a new title: henceforth, they would all be known not as developers or programmers, but as "software engineers." I really didn't care what they were called, so long as they showed up at the office and did cool programmy things, preferably while wearing shoes and long pants. And to tell the truth, the programmers didn't care, either. You could call them whatever you wanted; as long as they got paid and had snacks and got to do cool software things, they were happy. (And most of them wore shoes and long pants most of the time.)

But one of my developers emphatically did not want to be called a "software engineer." This man—we'll just call him "John," because, well, that was his name—felt that as programmers, they did not deserve to be called engineers. The programming profession, he felt, was not precise enough, nor its results predictable enough, to be called "engineering." Engineering, he said, meant that the end result, the product, was designed in such a way that the builders could guarantee the outcome of its use.

The example he used was, in fact, a bridge. A bridge is designed and built and guaranteed to carry a certain amount of weight. If built correctly, it will in fact carry that weight, and it will do so for a specified period of time.

Software, on the other hand, is never guaranteed. It's too complex and used in too many different environments for the developer to absolutely guarantee that it will function as designed. And sure enough, if you go looking for guarantees for software you've purchased (or, more likely, licensed), you will find a lot of vague legal-ese that basically boils down to "This really should work, but if not, well, we're not responsible. Sorry." If you go looking for remedies for failure, you'll find that those remedies are almost always limited to replacement of the media on which the software was supplied. (Which is even more meaningless these days, since most of your software was probably downloaded or is provided as a cloud service.)

Code is complicated. And the interaction
of thousands (sometimes millions) of lines
of code with one another and with the
software and hardware environments
within which that code runs make it close
to impossible to guarantee that a software
product will behave as designed at all
times.

John felt that, until programming had evolved to the point where designers and programmers could guarantee their work, then it was not deserving of the name engineering, and he would rather just have his title listed as "Programmer" on his business card.

I sympathized with John and told him that I would convey his feelings to the aforementioned powers-that-be. I did so, and the PTB explained to me that they were going to do exactly what they had intended to do all along, that John's title was now "Software Engineer," and that I should now scuttle back to my dark and forbidding lair and prepare for the next in a seemingly endless series of product delivery deadlines.

I returned to John, gave him the bad news, and sympathized heartily with him, while patting him gently on the shoulder. Then I asked him to please put his shoes back on.

He was right, though.

Data Mining for Fun and (Mostly for) Profit

So, big to-do over Localblox, a Washington state-based data mining firm that built 48 million personal profiles by scraping data from social networks such as Facebook, Twitter, Zillow, and the like. Much grumbling and gnashing of teeth over the "loss of privacy" and especially over the company's sloppy security: the collection of profiles, over 1.2 TB in size, was left unprotected on a public (though unlisted) Amazon storage server, where it was discovered by a security researcher. (Damn those pesky researchers, anyway!)

A couple of months earlier, it was Cambridge Analytica in the crosshairs of privacy supporters everywhere, after the data mining firm collected similar data and used it to help Republican candidates in their various bids for election. The catch there was that CA may have drifted into the realm of illegality by assigning non-US citizens to work on the campaigns. Technically, those non-citizens could in fact collect and analyze data, but the company was advised that it must not allow those non-citizens to "play strategic roles including the giving of strategic advice to candidates, campaigns, political parties or independent expenditure committees.” Which, of course, is exactly what they did. According to former CA employee-turned-whistleblower, Chris Wylie, ". . . there was no one American involved in [one campaign] . . . it was a de facto foreign agent, working on an American election."

Alexander Nix, CEO of Cambridge Analytica at Web Summit 2017
in Lisbon. Image used under the Creative Common Attribution 2.0
Generic license.

There's a big difference between these two scenarios. To take the second case first, had CA simply collected and analyzed data and then handed it over to a (in this case, Republican) campaign to use, no laws would have been broken; the data itself is out there for anyone to collect, aggregate, and use for any (legal) purpose. The company's mistake was in assigning foreigners to strategic duties that could affect a US election campaign. Some privacy supporters may have chafed at the use of PII (personally identifiable information) for purposes counter to their beliefs (read: we Democrats were not happy that the data was used to help Republican candidates) and without their knowledge or consent, but the reality is that you put that data out there. Why would various companies not collect and use it? (And let's be honest: Would the hue and cry among us libs have been quite as loud had the data been used to help Democratic candidates? I don't think so.)

Which brings me to the first case, one which involves a far more common—and perfectly legal—activity. We worry a great deal about privacy, but seemingly not enough to not place our entire lives out there on the Internet for the world to see. It's been said many times, but apparently it needs repeating: NOTHING YOU DO ON THE INTERNET IS PRIVATE. This is especially true when you post information that can be used against you or can be used to help people profile you and then use that profile to sell you things, including political candidates.

Alternatively, but quite commonly, such information is used by social engineers to scam you or talk you or one of your contacts into giving up names, passwords, and other data that ought to be kept confidential. Most so-called hacks actually start with a social engineering exploit, and most of those are predicated on data the scammer found on social media.

He looks so young and innocent, doesn't he? And he might
have been, back then. This is Mark Zuckerberg in his
Harvard dorm room back in 2005. Image used under the
Creative Commons Attribution 2.5 Generic license.

The thing is that a seemingly insignificant and innocuous Facebook, Instagram, or Snapchat post can tell marketers and thieves (one assumes that there is a difference) a great deal about you, your habits, your location, your typical travel plans, etc. I can trawl (not troll; well, I suppose I could do that, too) through Facebook and know who is on vacation, where they went, and when they'll return. I know what you like to eat. What you like to wear. I know your marital status—and if I dig a little, I might even be able to figure out if that marriage is in trouble. Got a public Amazon wish list? I know your hobbies, your future renovation plans, what musical instruments you play, what pets you have, and what kind of books you read. I also know if you're into essential oils and have an Apple Watch. (Why else would you list an Apple Watch Stand and a wireless charger on your wish list?) I know if you curl your hair, and whether you're a Mac person or a Windows person. (All of this goes double if you click the little Facebook "I just bought…" icon that pops up when you make an Amazon purchase.)

I have security tools that some may lack, but I'm no security whiz. Nonetheless, if your phone has its geolocation turned on, I can see many of the Facebook, Pinterest, Snapchat, and other posts you make, and I can track them by name, by date, by keyword, and by the location from which they were sent. To do this, I use a piece of software that's often used by law enforcement officers, but the truth is that anyone can buy access to it. But the reason the software can access the data to begin with is that we put that information out there to be found.

If I were smart enough to write an algorithm that could collect, aggregate, and collate all of this information, I could know all about you. (No worries; I'm not smart enough. Then again, I know people who are.) That's all that Localblox did: the company wrote software that scraped information from social media sites, aggregated it, and created code that pieced the information together and built individual portfolios. (And then they stupidly left it out there unprotected for a security researcher to find.)

If you lived in New York in 1948 and were one of the few people
who owned a television, this woman really wanted to sell you a
faucet aerator. Image in the public domain.

All of this data is valuable. Why do you think Facebook exists? It's not a charity. It's not out to make the world better a better place by enabling more people to communicate. (Though some might argue that such a thing could happen. If it did, it would be a byproduct, a happy accident.) Facebook's purpose—and the purpose of all social media—is to collect marketable data and sell it. To anyone: retailers, other marketers, even political parties. That's how they make money. LOTS of money.

Facebook has over 2 billion users. WhatsApp has 1.5 billion. Instagram has almost a billion. These are big numbers. And big numbers translate to big dollars. Dollars they make by selling information about us, because we were dumb enough to put that information out there to be sold. As others have said, when it's being given to you for "free" (and this includes network television), you're not really a customer—you're the product.

Failing Retirement

My 9th grade Intro to Algebra teacher lied to me. I was given the impression that in my life there would be numerous occasions when I would be required to determine exactly when the blue train would meet the green train, both of them having left different stations at different times and traveling toward each other at different rates of speed. This has yet to happen to me. And it's a good thing, because I had no idea how to figure out when the trains would cross paths, and I still have no idea how to figure this out. If the occasion did suddenly arise, I would have to call my friend Rick, who knows all of this stuff. (I'm trying to figure out what could possibly happen that would cause this issue to arise; perhaps if I were tied to the tracks, it would become a matter of some import to me. I'm working very hard at avoiding such a situation.)

See? Working. Work, work, work.
That's all I do on these trips. (Photo
by Lesley Scher.)

But all of this is just to say that life never quite works out as we expect. I had planned to be a psychologist. I really loved all the psychology classes I took—and also the related coursework in sociology, anthropology… You know. All of those -ologies. But then it turned out that psych majors had to take a statistics course. This is when I became an English major. (But the joke was on me. When I went to graduate school as an Education major, it turned out that I still had to take a statistics course!)

So, here I am many years later, retired. Sort of. It turns out that I apparently don't know how to be retired. I had the best of intentions. I was going to fish. A lot. I bought new fishing gear, some for freshwater fishing on lakes and rivers, and some much larger, more intimidatingly manly gear for surfcasting. The latter I have never used. The former I've used once, in a muddy river seemingly bereft of fish. (Though I did catch a very nice branch, which I had planned to take home and mount on the wall, until Lesley unplanned that for me.)

We even bought a beautiful little travel trailer; we take it all over and love camping in the beautiful state parks in Oregon and Washington. The private RV parks are a little pricier, but they often have amenities that are lacking in some of the parks. (Boondocking sites—places to park your RV for free or almost free—are often very beautiful, but generally lack all amenities, including showers, dump stations, or bathrooms. Since one cannot dump one's tanks at most such sites, the longest we can stay at a boondocking site is 3-4 days; after that it's time to dump our tanks and take a very long hot shower.) And we do take the trailer out as often as we can. In fact, we're currently planning a 3-week trip, which means that a new editing job will show up in my inbox exactly 6 hours before we leave.

 

There. See? Working. Slaving away while everyone
else is out hiking, sweating, mired in the mud, being
chased by bears and cougars and angry moose...
Actually, you know what? Never mind. I'm good.
(Photo by Lesley Scher.)

See, even though I do a lot of camping, and in spite of this theoretical "retirement," I'm still working. Even when I'm "camping" I'm often working. All I need, after all, is a cell signal. (Actual Wi-Fi is rare, but it does happen.) So, I've spent many an hour with our trailer nestled in the beauty of a forest of pines, blue skies overhead, the sounds of a rushing river in the background, the smell of fresh elk poop wafting all around—and there I am, hunched over our little dinette table, working away on my laptop, editing a book or writing an article.

In fact, I had planned to start my own little company (doing some very secret, cybersecurity-related stuff), but every time I get a few minutes to think about that project, in comes another editing gig. I'd really like to have another source of income, but I'm too busy working to figure out how to work.

And here's our cute little trailer, stopped for lunch
somewhere on the road. (Photo by Lesley. Or Rod.
Or possibly some passer-by, I'm not sure.)

I can't complain, really. I mean, the money is needed to help pay for Lesley's health insurance and to buy camping equipment and computer gear. And possibly a fully restored 1963 Austin-Healey 3000 convertible. (I just snuck that in there to see if Lesley was actually reading these blog entries. My plan, if she doesn’t read this, is to just buy the car and when she says, "Where—and WHY—did you buy that car, dammit?!" I can simply respond, "But Honey, I told you I was going to buy it! It was right there in blog post #37!" This is a foolproof plan, I can tell already.)

Still, I had always thought retirement would involve more fishing.

The Power of Media Compels You

I don't care much for sports bars. They’re usually loud and filled with obnoxious people who've had a few too many beers, and everyone's yelling at each other and at various television monitors mounted all over the room as their favorite (or least favorite) teams cavort onscreen, running around on a field doing various . . . uh, sports things.

Of course, I have (and almost always exercise) the option of simply avoiding sports bars; that way I can have a nice peaceful lunch or dinner, and the sports fanatics among us can scream spittle-flecked invective at the television, eat wings, and smear various sauces all over themselves while watching the Falcons, Penguins, Cardinals, Orioles, Seahawks or other such avian-themed sports teams. (In America, there seems to be a weird association between ornithology and sports teams. I suppose there's a Master's thesis in there someplace. Or maybe the Audubon Society would sponsor a grant.)

Now, this is a bar. This is the Table Bluff hotel and saloon in Table
Bluff, CA. The photo was taken in 1889, so it may have been
spruced up some since. But see? Not a television in sight! Image
courtesy of the Sonoma County Library.

But I'm not immune to the allure of sports, just sports bars. Why, only yesterday, I watched the Super Bowl. I don't remember which Super Bowl it was, maybe Super Bowl MMMMCMXCIX. But the Patriots and the Eagles (see?!) "gave it everything they had," "brought their A game," "played to win," and all of them "gave 110 percent." And to be honest, it was a good game, especially since I didn't really care who won. Also, we had enchiladas and beer.

But even when I go out to eat at a restaurant that's NOT a sports bar, I can't escape the television on the wall. These days, most restaurants have a television or two or twelve scattered about. Given that I am a child of the 60s, my eyes are unavoidably drawn to any flickering image in a box. (Perhaps students today would pay more attention to teachers if we found a way to flicker.) This is unfortunate when eating dinner with my wife and/or a group of friends. I may be paying close, even rapt attention to what is no doubt a very important discussion about . . . uh, something, but then out of the corner of my eye I can see that flickering, blue-tinged image beckoning. I always turn to look. I must turn to look. I've been conditioned to do so. The power of media compels me. And when Lesley draws my attention by coughing gently and touching me on the hand (perhaps with the business end of a fork), I have to pretend that I was not absent during the last 30 seconds or so of the conversation. I usually just smile and nod and try to look intrigued and amenable to whatever has just been said. (Sometimes this results in me accidentally agreeing to go hiking. I don't really see the point of hiking. I spent a lot of money on a very nice truck. It has air conditioning, soft leather seats, and XM radio. Hiking does not have those things.)

But it's not just television; non-electric media also compels us. Lesley and her mother enjoy putting together jigsaw puzzles. (God knows why. Perhaps it's some Episcopalian form of penance. Like flagellation, but more painful.) These puzzles are usually laid out on the dining room table, because it's the most convenient large, flat surface in the house. But I have to watch Mom and Lesley very closely during dinner. We'll be enjoying our food and talking, and I can see their eyes beginning to steal away, glancing surreptitiously at the puzzle, just a few inches from our plates. Eventually they desert our meal (and me) and enter into a full-fledged puzzle-solving frenzy. Like me watching a television image, they can't not do it. At first, they were sheepish about it, but now they don't even bother pretending that they think it's weird to work on a puzzle during dinner.

Media, it turns out, is media, and none of us (well, few of us) are immune.

You've all seen this photo of commuters ignoring one another in order
to concentrate on their newspapers. It's supposed to make the ironic
point that it's not only modern media that has distanced us from one
another. Which it does, of course, but keep in mind that these folks
may well have finished their papers on the way and then spoken with
one another about what they had just read. Image in the public domain.

I don't think that the kids we berate for spending their lives with their faces in Facebook or Instagram or Snapchat (or whatever is big these days—I may be a few weeks out of date) are really any different than any of the rest of us; they too are compelled by media, but I suppose it's a matter of degree. They are all about being connected, all the time. It's very difficult for them to disconnect. I saw this during the college classes I taught; asking students to put their phones away for an hour was almost physically painful for them. The thing about other forms of media is that they're there and then gone. We read the newspaper (remember those?) and then we were finished and perhaps we even (God forbid!) spoke to people about what we'd just read. We would connect intermittently to television (perhaps after school or in the evening), we might read a book or listen to the radio, but then we were finished, at least for the time being. These days, though, people (not all of them kids) are connected to other people all the time. It must be exhausting! Who would want to be connected to everyone 24/7?! I don't even like people that much! (But I love dogs. If we could connect to dogs, now, that would be different. I could definitely connect with dogs all day. I would most certainly sign up for DogBook or InstaPaw or PupChat or something.)

My granddaughter is going on a medical mission trip to Guatemala this summer, during which she and other scientifically-minded students will teach basic hygiene, measure villagers' blood pressure and glucose levels, and do other science-y things for a couple of weeks. (All of this will be covered in greater detail in my upcoming book, entitled My Grandchild is Smarter than Your Grandchild and All of Your Entire Family Put Together—and Better-Looking, Too.) But on this trip, she has to disconnect for an entire 10 days! No phone. No texting. No Instagram. No computer. For almost two weeks, she will be in a foreign country, forced to interact with actual people in real-time. I shudder to think what this might do to her. What if she accidentally reads a newspaper?

Right again, dammit.

Sometimes I hate being right. (I am informed by my wife that this doesn't happen often enough for it to be a real concern, so…) Nonetheless, I knew that this would happen.

If you've read my book—and of course you have!—you may recall that I spent some time talking about the dark, dangerous side of the Internet. I love the Internet, but along with all of the wonderful things it has brought us, there's also quite a lot of ugliness.

An FBI SWAT team training in New York. Image used
under the Creative Commons Attribution 2.0
Generic license.

I refer, for example, to various forms of bullying: name-calling, vituperative attacks, and malicious threats delivered mostly by folks who revel in their ability to deliver messages of hate while cloaked in the anonymity provided by the Internet. Often this hate is directed at women, of course, but we're all vulnerable; and much more frightening still, our children are vulnerable. (Bullying used to be restricted mainly to schools, but now that kids are pretty much connected 24/7, they're even bullied at home or while out and about. These kids—and some adults—must feel as if there is simply no escape from their assailants.)

In chapter 6 of Leveling the Playing Field, I recounted an interview with two of the Gamergate principals, Zoe Quinn and Alex Lifschitz. You may recall the Gamergate incident: It began as a reasonable argument amongst gamers about ethics in game-related journalism, but quickly escalated into vicious attacks, name-calling, doxing, and death threats, all delivered (mostly anonymously) via the Web. Zoe and Alex were two of the favored (if that's the right word) targets, and the two of them essentially had to go on the run, afraid to stay at their own homes or to be seen in public with their friends and colleagues.

 

Zoe Quinn is one of the Gamergate
folks targeted by folks who attacked
her, released her personal information
(called "doxing":), and threatened to
"swat" her and her friends.

Perhaps worst of all, said Zoe, was the threat of swatting, in which an attacker calls the police and reports a fake emergency at the target's address. The caller might tell the police that he had heard gunshots at the target's address or that he knows someone is holed up there with firearms and/or explosives. You get the idea. The goal is to get the cops to deploy a SWAT team to that address; the attacker's presumed goal is to get someone at that address hurt or possibly even killed. This is why Zoe Quinn and others have called swatting "attempted murder by proxy."

It's incredibly dangerous. You have heavily armed, nervous, excited (and sometimes frightened) police officers breaking open a door and entering the premises of someone who has no idea what is happening, why these assault weapons are suddenly pointed at him, or why these people are breaking into his house. (I suppose that the smart thing for the victim to do would be to drop to the floor with his hands behind his head, but in those circumstances, who would have the presence of mind to do the smart thing? Then again, what if, when you drop, the cop thinks that you're diving for a weapon? And how is he or she supposed to know that you're not?!)

Swatting has been going on for several years now (the FBI estimates that some 400 cases occur each year), and it finally resulted—as we knew it eventually would—in someone's death. On December 28th, Andrew Finch was killed in Wichita, KS when he came to the front door in response to police officers who had been sent there by a swatting "prank." (Ironically, the address the attacker had wasn't even the correct address; Finch was not a party to the argument that caused the swatting call, and was therefore unaware that there was a problem, making the whole nightmare doubly tragic.)

Representative Katherine Clark
(D - Mass.) sponsored the Interstate
Swatting Hoax Act of 2015 and almost
immediately became  the victim of a
swatting attack herself. Image in the
public domain.

A few years ago, Democratic congressperson Katherine Clark introduced a bill that would impose serious penalties for such online attacks and hoax calls, especially ones that result in death. (Naturally, Clark herself became the target of swatting attacks and other online threats.) The bill is still in committee, and people who know about such things say that it has little chance of passing.

Some argue that we don't need laws specifically aimed at swatting, in any case. The L.A. Times Editorial Board, for example, argues that existing laws cover such situations: there are, for instance, already laws against making threats and against filing false police reports. However, most of these laws are local in nature, and each state determines how to file charges. In most cases, callers are charged with misdemeanors, but even if a felony charge is brought, the punishment may vary wildly.

Zoe Quinn is right: a swatting call is attempted murder by proxy. If apprehended, the "prankster" should be charged with attempted murder or another serious felony. If someone dies as a result of a swatting call, the caller should be charged with, at minimum, manslaughter.

And if it takes a federal law to ensure that this happens, then so be it.

Bows and Arrows, Sticks and Stones

I've been reading about primitive bow-making. Not the kind of bow one might use on a gift box (though my efforts in that area are certainly primitive enough), but bows that one might use to shoot arrows while hunting or for target practice. You know, bows of the sort that archers use.

Bows and arrows have been around for many thousands of years, of course, and with the introduction of fiberglass, and then the addition of pulleys, sighting mechanisms, carbon laminates, stabilizers, and other such paraphernalia, the technology of bows has advanced such that some modern compound bows look only vaguely like the bows carried by Native American and early European and Asian archers. To my eye, they don't look like bows at all.

This is Albina Nikolayevna Loginova, a Russian compound
archer. She is the current world archery champion in women's
compound archery. Her modern compound bow, simpler than
some, nonetheless looks pretty complicated. Image licensed
under the Creative Commons Attribution-Share Alike 3.0
Unported license.

I'm much more interested in traditional bows, generally made of wood—though they can also be made of horn—and sometimes adorned or enhanced with backings of sinew, silk, or rawhide. They seem simple, and somehow pure. (Primitive is, of course, the wrong word for it, laden as that term is with both ambiguity and potentially negative connotations. Traditional is the favored term, one that works well, since a given tradition can be pinpointed somewhat accurately in both time and place; thus, one can pattern a bow after those of the Klamath, Kiowa, Siletz, or Comanche tribes, and we can also classify a bow shape or construction according to when it was made.)

As a technologist of sorts, I've wondered what attracts me to these seemingly less technical endeavors; why, for instance, do I get such pleasure out of seeing a straightforward, simple design? It's not that I don't appreciate the complexity of a modern compound bow, I do—and in much the same way that I appreciate any other sophisticated design, whether in a motorcycle, a computer, a building, or a piece of software. Basically, I'm a sucker for good engineering of any sort. Sometimes that engineering is pretty complicated, but often—as in the case of a so-called primitive bow—it's quite simple, at least on the surface. (A good bowyer—for that is what we call someone who makes bows—can explain the many ways in which traditional bows are actually quite sophisticated. But, at least at first glance, they look to the eye disarmingly simple, even rudimentary.)

Simple can nonetheless be beautiful. This is a yew longbow.
It’s a selfbow, i.e., a bow carved from one piece of wood.
A medieval longbow had a range approaching 400 yards.
Image placed in the public domain by the photographer,
James Cram.

As with most of forms of engineering, a traditional bow results from the melding of art and craft and science; as with any good woodworker, a seasoned bowyer puts his skill and knowledge and sense of aesthetics to work creating something new, building something beautiful with his hands and his heart and his brain. It's hard not to like something like that.

And yet, there's an irony here, one that I thoroughly enjoy. I'm reading and learning about primitive archery and bowyery, but I'm doing it in a modern home; when my coffee cools as I read, I walk over to a microwave oven to reheat it. I sit in front of a flat-panel TV, streaming an Amazon movie (which I'm mostly ignoring) and read a book about “primitive” bow-making, but the book I’m reading is being displayed on my iPad; as my eyes tire (which they do, because I am old), I can enlarge the font or change the background color. If I run across a particularly interesting illustration, I click a few buttons and—thanks to Wi-Fi—the illustration prints out on a printer upstairs near my desk. Later on, I may take some notes in the Kindle app I'm using to read this book and drop them, along with snippets of the associated text from the book, into a OneNote or Evernote notebook. Come to think of it, if I ever decide to try my hand at this, I may begin by using a CAD/CAM program to lay out a basic design.

I wonder if there's a word or phrase that describes the use of sophisticated technology to create primitive artifacts. Can't think of the term right now, but the most obvious example that comes to mind is nuclear war. 

Enjoy Every Sandwich

Back when I was the editor of Smart Computing Magazine, it was my pleasure to work with a talented tech writer named Alan Luber. Alan wrote columns, feature articles, hardware reviews.... You name it, and Alan could write it. And he wrote on word-count and on deadline. He was an editor's dream; we knew that if we had assigned Alan an article, it would be in on time and that it would be very, very clean.

Not everyone knew it, but Alan was fighting what would turn out to be a losing battle with cancer. And yet, in the last year of his life, he worked harder than ever, churning out quality copy for me and for other magazines; he wanted to leave a legacy, he said. And I suspect that work was something of an escape for him.

When he passed away on November 23rd, 2004, I was struck dumb; even though I knew by then that his death was inevitable, I was in shock. I had lost a respected colleague and a dear friend, and I ached for his family, his wife and his children especially.

Now, 13 years later, one of those children—the youngest, Mallory—has completed a labor of love in honor of her father. The Cancer Chronicles: A Story of Transformation and Triumph is an eBook collection of Alan's thoughts about his journey toward death and his reflections on a life well-lived. You should get this book. It's sad, but somehow uplifting, and flashes of Alan's dry humor stand out against the stark reality of his pain and his sure decline.

At the time, I wrote a column about Alan's death, which—with the kind permission of Sandhills Publishing—I will include in this post. Don't forget to check out The Cancer Chronicles; it'll be $5 well spent. (As I write this, in fact, the book is actually free, but I don't know how long that'll last.) We don't often get to see this clearly inside the heart and soul of someone about to die. When you read the book, you'll see that Alan faced death with a heart more peaceful than that with which most of us face life.