Do You Dream In Color?

According to the Sapir–Whorf hypothesis, our language influences how we think and experience the world. That’s easy to imagine. Certainly our symbolism of mathematics influences how we calculate. Can you imagine doing moderately complex math with Roman numerals or without zero or negative numbers? But recently I was reminded that technological media also influences our perception of reality, and I have a Hackaday post to thank for it.

The post in question was about color TV. When I was a kid, most people had black and white TVs, although there were color sets. Even if you had a color set, many shows and movies were in black and white. Back then, many people still shot black and white film in their cameras, too, for many reasons. To make matters worse, I grew up in a small town, reading books from the local library that were ten or twenty years behind the times.

At some point, I read a statistic that said that most people dream in black and white. You may find this surprising, as I’ll bet you dream in color. It turns out, how people dream may have changed over the years and still and motion photography may be the reason.

The Post

In the post, I posed a question I’ve thought about many times: Did people dream in black and white before the advent of photography? It was kind of an off-hand remark to open the post, but many people reacted to it in the comments. They seemed surprised that I would ask that because, of course, everyone dreams in color.

I asked a few people I knew who also seemed very surprised that I would assume anyone ever dreams in color. But I was sure I had been told that sometime in the past. Time to hit the Internet and find out if that was incorrect or a false memory or something else. Turns out, it was indeed something else.

The Science

Charlie Chaplin’s “Modern Times

A scientific paper from 2008 held the answer. It turns out that science started asking questions like this in the early 1900s. Up through the 1940s, people overwhelmingly reported dreaming in black and white, at least most of the time. Color dreams were in the minority, although not unheard of.

Then something changed. Studies that occurred in the 1960s and later, show exactly the opposite. People almost always dream in color and rarely in black and white. Of course, that correlates well with the rise of color photos, movies, and television. What’s more is, while there is no scientific evidence gathering about earlier times, there is a suspicious lack of, for example, a Shakespeare quote about “The gray world of slumber…” or anything else that would hint that the writer was dreaming in black and white.

Interpretation

Judging from the paper, it seems clear that most people agree that color media played a role in this surprising finding. What they can’t agree on is why. It does seem unlikely that your dreams really change based on your media consumption. But it is possible that your recollection changes. This is particularly true since the way researchers acquired data changed over that time period, too. But even if the data doesn’t show that you dreamed in black and white, it did show that you remembered dreaming in black and white.

For that matter, it isn’t clear that anyone understands how you experience dreams visually, anyway. It isn’t like the back of your eyelids are little movie screens. You don’t actually see anything in a dream, you only remember seeing it.

The Question

If something as simple as black-and-white movies and TV can change how we perceive dreams, you have to wonder how much tech is changing our reality experience in other ways. Do we live differently because we have cell phones? Or the Internet? Will virtual reality alter our dream lives? It would be interesting to fast-forward a century and see what historians say about our time and how strangely we perceive reality today.

Against Elitism

A while back we got an anonymous complaint that Hackaday was “elitist”, and that got me thinking. We do write up the hacks that we find the coolest, and that could lead to a preponderance of gonzo projects, or a feeling that something “isn’t good enough for Hackaday”. But I really want to push back against that notion, because I believe it’s just plain wrong.

One of the most important jobs of a Hackaday writer is to find the best parts of a project and bring that to the fore, and I’d like to show you what I mean by example. Take this post from two weeks ago that was nominally about rescuing a broken beloved keyboard by replacing its brain with a modern microcontroller. On its surface, this should be easy – figure out the matrix pinout and wire it up. Flash in a keyboard firmware and you’re done.

Of course we all love a good hardware-rescue story, and other owners of busted Sculpt keyboards will be happy to see it. But there’s something here for the rest of us too! To figure out the keyboard matrix, it would take a lot of probing at a flat-flex cable, so [TechBeret] made a sweet breakout board that pulled all the signals off of the flat-flex and terminated them in nicely labelled wires. Let this be your reminder that making a test rig / jig can make these kind of complicated problems simpler.

Checking the fit with a 3D printed PCB

Once the pinout was figured out, and a working prototype made, it was time to order a neat PCB and box it up. The other great trick was the use of 3D-printed mockups of the PCBs to make sure that they fit inside the case, the holes were all in the right places, and that the flat-flex lay flat. With how easily PCB design software will spit out a 3D model these days, you absolutely should take the ten minutes to verify the physical layout of each revision before sending out your Gerbers.

So was this a 1337 hack? Maybe not. But was it worth reading for these two sweet tidbits, regardless of whether you’re doing a keyboard hack? Absolutely! And that’s exactly the kind of opportunity that elitists shut themselves off from, and it’s the negative aspect of elitism what we try to fight against here at Hackaday.

In A Twist, Humans Take Jobs From AI

Back in the 1970s, Rockwell had an ad that proudly proclaimed: “The best electronic brains are still human.” They weren’t wrong. Computers are great and amazing, but — for now — seemingly simple tasks for humans are out of reach for computers. That’s changing, of course, but computers are still not good at tasks that require a little judgment. Suppose you have a website where people can post things for sale, including pictures. Good luck finding a computer that can reliably reject items that appear to be illegal or from a business instead of an individual. Most people could easily do that with a far greater success rate than a computer. Even more so than a reasonable-sized computer.

Earlier this month, we reported on Amazon stepping away from the “just walk out” shopping approach. You know, where you just grab what you want and walk out and they bill your credit card without a checkout line. As part of the shutdown, they revealed that 70% of the transactions required some human intervention which means that a team of 1,000 people were behind the amazing technology.

Humans in the Loop

That’s nothing new. Amazon even has a service called Mechanical Turk that lets you connect with people willing to earn a penny a picture, for example, to identify a picture as pornographic or “not a car” or any other task you really need a human to do. While some workers make up to $6 an hour handling tasks, the average worker makes a mere $2 an hour, according to reports. (See the video below to see how little you can make!) The name comes from an infamous 200-year-old chess-playing “robot.” It played chess as well as a human because it was really a human hiding inside of it.

Continue reading “In A Twist, Humans Take Jobs From AI”

One Project At A Time, Or A Dozen?

We got a bunch of great food for thought in this week’s ask-us-anything on the Hackaday Podcast, and we all chewed happily. Some of my favorite answers came out of the question about how many projects we all take on at once. Without an exception, the answer was “many”. And while not every one of the projects that we currently have started will eventually reach the finish line, that’s entirely different from saying that none of them ever do. On the contrary, Tom Nardi made the case for having a number of irons simultaneously in the fire.

We all get stuck from time to time. That’s just the nature of the beast. The question is whether you knuckle down and try to brute-force power your way through the difficulty, or whether you work around it. A lot of the time, and this was Dan Maloney’s biggest bugaboo, you lack the particular part or component that you had in mind to get the job done. In that situation, sometimes you just have to wait. And what are you going to do while waiting? Work on Project B! (But take good notes of the state of Project A, because that makes it a lot easier to get back into the swing of things when the parts do arrive.)

Al and I both weighed in on the side of necessity, though. Sometimes, no matter how many attractive other projects you’ve got piled up, one just needs to get out the door first. My recent example was our coffee roaster. Before I start a big overhaul, I usually roast a couple days’ worth of the evil bean. And then the clock starts ticking. No roasting equals two unhappy adults in this household, so it’s really not an option. Time pressure like that helps focus the mind on the top-priority project.

But I’m also with Tom. It’s a tremendous luxury to have a handful of projects in process, and be able to hack on one simply because you’re inspired, or in love with the project at that moment. And when the muse calls, the parts arrive, or you finally figure out what was blocking you on Project A, then you can always get back to it.

In Defense Of Anthropomorphizing Technology

Last week I was sitting in a waiting room when the news came across my phone that Ingenuity, the helicopter that NASA put on Mars three years ago, would fly no more. The news hit me hard, and I moaned when I saw the headline; my wife, sitting next to me, thought for sure that my utterance meant someone had died. While she wasn’t quite right, she wasn’t wrong either, at least in my mind.

As soon as I got back to my desk I wrote up a short article on the end of Ingenuity‘s tenure as the only off-Earth flying machine — we like to have our readers hear news like this from Hackaday first if at all possible. To my surprise, a fair number of the comments that the article generated seemed to decry the anthropomorphization of technology in general and Ingenuity in particular, with undue harshness directed at what some deemed the overly emotional response by some of the NASA/JPL team members.

Granted, some of the goodbyes in that video are a little cringe, but still, as someone who seems to easily and eagerly form attachments to technology, the disdain for an emotional response to the loss of Ingenuity perplexed me. That got me thinking about what role anthropomorphization might play in our relationship with technology, and see if there’s maybe a reason — or at least a plausible excuse — for my emotional response to the demise of a machine.

Continue reading “In Defense Of Anthropomorphizing Technology”

You Can’t Make What You Can’t Measure

What’s the most-used tool on your bench? For me, it’s probably a multimeter, although that’s maybe a tie with my oscilloscope. Maybe after that, the soldering iron and wire strippers, or my favorite forceps. Calipers must rate in there somewhere too, but maybe a little further down. Still, the top place, and half of my desert-island top-10, go to measuring gear.

That’s because any debugging, investigation, or experimentation always starts with getting some visibility on the problem. And the less visible the physical quantity, the more necessary to tool. For circuits, that means figuring out where all the voltages lie, and you obviously can’t just guess there. A couple months ago, I was doing some epoxy and fiberglass work, and needed to draw a 1/2 atmosphere vacuum. That’s not the kind of quantity you can just eyeball. You need the right measurement tool.

A few weeks ago, I wrote about my disappointment in receiving a fan that wouldn’t push my coffee beans around in the homemade roaster. How could I have avoided this debacle? By figuring out the pressure differential needed and buying a fan that’s appropriately rated. But I lacked pressure and flow meters.

Now that I think about it, I could have scavenged the pressure meter from the fiberglassing rig, and given that a go, but with the cheap cost of sensors and amplifiers, I’ll probably just purpose-build something. I’m still not sure how I’ll measure the flow; maybe I’ll just cheese out and buy a cheap wind-speed meter.

When people think of tools, they mostly think of the “doers”: the wrenches and the hammers of this world. But today, let’s all raise a calibrated 350 ml glass to the “measurers”. Without you, we’d be wandering around in the dark.

Degrees Of Freedom, But For Whom?

Opening up this week’s podcast, I told Kristina about my saga repairing our German toilet valve. I’m American, and although I’ve lived here over a decade, it’s still surprising how things can be subtly different from how they worked back home.

But what was amazing about this device was that it had a provision for fine adjustment, and to some extent relied on this adjustment to function. Short version: a lever mechanism provides mechanical advantage to push a stopper against the end of a pipe to block the water flow, and getting the throw of this mechanism properly adjusted so that the floater put maximum pressure against the pipe required fine-tuning with a screw. But it also required understanding the entire mechanism to adjust it.

Which makes me wonder how many plumbers out there actually take the time to get that right. Are there explicit instructions in the manual? Does every German plumber learn this in school? I was entirely happy to have found the adjustment screw after I spent 15 minutes trying to understand the mechanism, because it did just the trick. But is this everyone’s experience?

I often think about this when writing code, or making projects that other people are likely to use. Who is the audience? Is it people who are willing to take the time to understand the system? Then you can offer them a screw to turn, and they’ll appreciate it. But if it’s an audience that just doesn’t want to be bothered, the extra complexity is just as likely to cause confusion and frustration.