The site is called Hackaday, and has been for 21 years. But it was only for maybe the first half-year that it was literally a hack a day. By the 2010s, we were putting out four or more per day, and in the later 20-teens, we settled into our current cadence of eight hacks per day, plus some original pieces over the top. That’s a lot of hacks per day! (But “Eight-to-Ten-Hacks-a-Day” just isn’t as catchy.)

With that many posts daily, we also tend to reach out to a broader array of interests. Quite simply, not every hack is necessarily going to be just exactly what you are looking for, but we wouldn’t be writing it up if we didn’t think that someone was looking for it. Maybe you don’t like CAN bus hacks, but you’re into biohacking, or retrocomputing. Our broad group of writers helps to make sure that we’ll get you covered sooner or later.

What’s still surprising to me, though, is that a couple of times per week, there is a hack that is actually relevant to a particular project that I’m currently working on. It’s one thing to learn something new every day, and I’d bet that I do, but it’s entirely another to learn something new and relevant.

So I shouldn’t have been shocked when Tom and I were going over the week’s hacks on the podcast, and he picked an investigation of injecting spray foam into 3D prints. I liked that one too, but for me it was just “learn something new”. Tom has been working on an underwater ROV, and it perfectly scratched an itch that he has – how to keep the top of the vehicle more buoyant, while keeping the whole thing waterproof.

That kind of experience is why I’ve been reading Hackaday for 21 years now, and it’s all of our hope that you get some of that too from time to time. There is a lot of “new” on the Internet, and that’s a wonderful thing. But the combination of new and relevant just can’t be beat! So if you’ve got anything you want to hear more about, let us know.

It’s that time of year when we eat perhaps a little too much food, and have maybe just a few too many sips of red wine. But it’s also when we think about what we’ve been grateful for over the past year. And here at Hackaday, that’s you all: the people out there making the crazy projects that we get the pleasure of writing about, and those of you just reading along. After all, we’re just the hackers in the middle. You are all Hackaday.

And it’s also the time of year, at least in this hemisphere, when the days get far too short for their own good and the weather gets frankly less than pleasant. That means more time indoors, and if we play our cards right, more time in the lab. Supercon is over and Hackaday Europe is still far enough in the future. Time for a good project along with all of the festive duties.

So here we sit, while the weather outside is frightful, wishing you all a pleasant start to the holiday season. May your parts bin overflow and your projects-to-do-list never empty!

One of our newer writers, [Tyler August], recently wrote a love letter to plasma TV technology. Sitting between the ubiquitous LCD and the vanishing CRT, the plasma TV had its moment in the sun, but never became quite as popular as either of the other display techs, for all sorts of reasons. By all means, go read his article if you’re interested in the details. I’ll freely admit that it had me thinking that I needed a plasma TV.

I don’t, of course. But why do I, and probably a bunch of you out there, like old and/or odd tech? Take [Tyler]’s plasma fetish, for instance, or many people’s love for VFD or nixie tube displays. At Supercon, a number of people had hit up Apex Electronics, a local surplus store, and came away with some sweet old LED character displays. And I’ll admit to having two handfuls of these displays in my to-hack-on drawer that I bought surplus a decade ago because they’re so cute.

It’s not nostalgia. [Tyler] never had a plasma growing up, and those LED displays were already obsolete before the gang of folks who had bought them were even born. And it’s not simply that it’s old junk – the objects of our desire were mostly all reasonably fancy tech back in their day. And I think that’s part of the key.

My theory is that, as time and tech progresses, we see these truly amazing new developments become commonplace, and get forgotten by virtue of their ever-presence. For a while, having a glowing character display in your car stereo would have been truly futuristic, and then when the VFD went mainstream, it kind of faded into our ambient technological background noise. But now that we all have high-res entertainment consoles in our cars, which are frankly basically just a cheap tablet computer (see what I did there?), the VFD becomes an object of wonder again because it’s rare.

Which is not to say that LCD displays are anything short of amazing. Count up the rows and columns of pixels, and multiply by three for RGB, and that’s how many nanoscale ITO traces there are on the screen of even the cheapest display these days. But we take it for granted because we are surrounded by cheap screens.

I think we like older, odder tech because we see it more easily for the wonder that it is because it’s no longer commonplace. But that doesn’t mean that our current “boring” tech is any less impressive. Maybe the moral of the story is to try to approach and appreciate what we’ve got now with new eyes. Pretend you’re coming in from the future and finding this “old” gear. Maybe try to figure out how it must have worked.

I was looking over the week’s posts on Hackaday – it’s part of my job after all – and this gem caught my eye: a post about how to make your own RP2040 development board from scratch. And I’ll admit that my first thought was “why would you ever want to do that?” (Not a very Hackaday-appropriate question, honestly.) The end result will certainly cost more than just buying a Pi Pico off the shelf!

Then it hit me: this isn’t a project per se, but rather [Kai] was using it as an test run to learn the PCB-production toolchain. And for that, replicating a Pico board is perfect, because the schematics are easily available. While I definitely think that a project like this is a bit complicated for a first PCB project – I’d recommend making something fun like an SAO – the advantage of making something slightly more involved is that you run into all of the accompanying problems learning experiences. What a marvelous post-complete-beginner finger exercise!

And then it hit me again. [Kai]’s documentation of everything learned during the project was absolutely brilliant. It’s part KiCAD tutorial, part journal about all the hurdles of getting a PCB made, and just chock-full of helpful tips along the way. The quality of the write-up turns it from being just a personal project into something that can help other people who are in exactly the same boat, and I’m guessing that’s a number of you out there.

In the end, this was a perfect Hackaday project. Yes, it was “too simple” for those who have made their 30th PCB design. (Although I’d bet you could still pick up a KiCAD tip or two.) And yes, it doesn’t make economic sense to replicate mass-market devices in one-off. And of course, it doesn’t need that fun art on the board either. But wrap all these up together, and you get a superbly documented guide to a useful project that would walk you through 95% of what you’ll need to make more elaborate projects later on. Superb!

Surely you do “finger exercises” too. Why not write them up, and share the learning? And send them our way – we know just the audience who will want to read it.