Horrendous Mess Of Wires

When do you post your projects? When they’re done? When they’re to the basic prototype stage? Or all along the way, from their very conception? All of these have their merits, and their champions.

In the post-all-along-the-way corner, we have Hackaday’s own [Arya Voronova], who outlines the many ways that you can start documenting your project before it’s even a fully fledged project. She calls these tidbits “breadcrumbs”, and it strikes me as being a lot like keeping a logbook, but doing it in public. The advantages? Instead of just you, everyone on the Internet can see what you’re up to. This means they can offer help, give you parts recommendations, and find that incorrect pinout that one pair of eyes would have missed. It takes a lot of courage to post your unfinished business for all to see, but ironically, that’s the stage of the project where you stand to gain the most from the exposure.

On the opposite end of the spectrum are the folks who document their projects at the very end. We see a ton of these on Hackaday.io and in people’s personal blogs. It’s a great service to the community, frankly, because at that point, you’re already done with the project. This is the point where the reward, for you, is at its minimum, but it’s also the point where you feel least inhibited about sharing if you’re one of those people who are afraid of showing your work off half-done. The risk here, if you’re like me, is that you’re already on to the next project when one is “done”, and going back over it to make notes seems superfluous. Those of you who do it regardless, we salute you!

And then there’s the middle ground. When you’re about one third of the way done, you realize that you might have something half workable, and you start taking a photo or two, or maybe even typing words into a computer. Your git logs start to contain more than just “fixed more stuff” for each check-in, because what if someone else actually reads this? Maybe you’re to the point where you’ve just made the nice box to put it in, and you’re not sure if you’ll ever go back and untangle that rat’s nest, so you take a couple of pictures of the innards before you hot glue it down.

I’m a little ashamed I’m probably on the “post only when it’s done” end of things than is healthy, mostly because I don’t have the aforementioned strength of will to go back. What about you?

Do Bounties Hurt FOSS?

As with many things in life, motivation is everything. This also applies to the development of software, which is a field that has become immensely important over the past decades. Within a commercial context, the motivation  to write software is primarily financial, in that a company’s products are developed by individuals who are being financially compensated for their time. This is often different with Free and Open Source Software (FOSS) projects, where the motivation to develop the software is in many cases derived more out of passion and sometimes a wildly successful hobby rather than any financial incentives.

Yet what if financial incentives are added by those who have a vested interest in seeing certain features added or changed in a FOSS project? While with a commercial project it’s clear (or should be) that the paying customers are the ones whose needs are to be met, with a volunteer-based FOSS project the addition of financial incentives make for a much more fuzzy system. This is where FOSS projects like the Zig programming language have put down their foot, calling FOSS bounties ‘damaging’.

Continue reading “Do Bounties Hurt FOSS?”

Confluence Of Nerdery

You might find yourself, dear Hackaday reader, attracted to some pretty strange corners of the tech world. Who knows when that knowledge of stenography, ancient retrocomputing, and floppy disk internals will all combine to get someone falsely accused out of jail? Go read this story and come on back, but the short version is that [Bloop Museum] helped recover some 40+ year old court evidence off of some floppies to right an old wrong.

If you looked at the combination of extremely geeky topics, you’d say it’s unlikely to find anyone well versed in any one of them, and you’d say that the chances of anyone knowing enough in each these fringe domains to be helpful is exceedingly low. But I’m absolutely sure that the folks at [Bloop Museum] had some more to throw into the mix if they were called for. Or better yet, they might know exactly the right geeks to call in.

And that’s the other heartwarming part of the story. When [Bloop Museum] didn’t know everything about old stenography formats, they knew the right people to reach out to – the Plover open stenography project. Who is going to know more? Nobody! Together, the nerd community is an unstoppable resource.

So remember, when you’re hanging out with your geek friends, to keep a running catalog of everyone’s interests. Because you never know when you’re going to need an expert in re-gilding frames, or relocating bee hives, or restoring 1930’s radio sets. Or decoding obscure data formats to get someone out of jail.

Hackaday Halloween

We’re running the 2023 Halloween Hackfest and it’s your chance to document your Halloween projects, and win fame, fortune, or at least one of three $150 DigiKey gift certificates, plus some Arduino schwag courtesy of the contest’s sponsors! You’ve got until the end of October, so get on it!

What Is Killing Cursive? Ballpoints. Probably.

I get it — you hate writing by hand. But have you ever considered why that is? Is it because typing is easier, faster, and more convenient here in 2023? Maybe so. All of those notwithstanding, I honestly think there’s an older reason: it’s because of the rise of ballpoint pens. And I’m not alone.

Bear with me here. Maybe you think you hate writing because you were forced to do it in school. While that may very well be, depending on your age, you probably used a regular wood-case pencil before graduating to the ballpoint pen, never experiencing the joys of the fountain pen. Well, it’s never too late.

Continue reading “What Is Killing Cursive? Ballpoints. Probably.”

Inspiration

While we were debating about whether it even makes any sense to reboot RadioShack, or indeed any brick-and-mortar electronics store in the modern era, Dan Maloney and I stumbled on what probably is the real source of all of our greybeard nostalgia for the store chain: inspiration.

For both of us, the appeal of a store like RadioShack was going through the place and thinking of what you’d do with all of those parts. Looking at the back of the beefiest MOSFET in the joint, you’d think about all the current you could pass with it. Or what you’d do with all of those piezo buzzers. And if you didn’t know yet what electronics project you wanted to make, there were things like the Forrest Mims notebooks to inspire you. There you’d find a way to turn the humble LED into a light sensor, whether you needed to or not. I wonder how many packs of assorted LEDs that book sold?!

Dan got his first hands on with a computer in RadioShack as well, because they let folks try them right there. If you didn’t know what you wanted a computer for, and that was the big question of the early microcomputer era, you could head into the store yourself and find out. Seeing, and playing with, Demon Dancer inspired.

A lot of this role is taken over by hackerspaces these days, and even more is taken by the Internet itself, of course. We have no shortage of inspiration – just read a day’s worth of Hackaday if you don’t believe me. So is there any room left for RadioShack’s inspirational role? Maybe not. But if that’s the cost of living in a world where we have access to more great ideas than we’ll ever have time to execute, then so be it!

Agreeing By Disagreeing

While we were working on the podcast this week, Al Williams and I got into a debate about the utility of logic analyzers. (It’s Hackaday, after all.) He said they’re almost useless these days, and I maintained that they’re more useful than ever. When we got down to it, however, we were actually completely in agreement – it turns out that when we said “logic analyzer” we each had different machines, and use cases, in mind.

Al has a serious engineering background and a long career in his pocket. When he says “logic analyzer”, he’s thinking of a beast with a million probes that you could hook up to each and every data and address line in what would now be called a “retrocomputer”, giving you this god-like perspective on the entire system state. (Sounds yummy!) But now that modern CPUs have 64-bits, everything’s high-speed serial, and they’re all deeply integrated on the same chip anyway, such a monster machine is nearly useless.

Meanwhile, I’m a self-taught hacker type. When I say “logic analyzer”, I’m thinking maybe 8 or 16 signals, and I’m thinking of debugging the communications between a microcontroller, an IMU, or maybe a QSPI flash chip. Heck, sometimes I’ll even break out a couple pins on the micro for state. And with the proliferation of easy and cheap modules, plus the need to debug and reverse commodity electronics, these logic analyzers have never been more useful.

So in the end, it was a simple misunderstanding – a result of our different backgrounds. His logic analyzers were extinct or out of my price range, and totally off my radar. And he thinks of my logic analyzer as a “simple serial analyzer”. (Ouch! But since when are 8 signals “serial”?)

And in the end, we both absolutely agreed on the fact that great open-source software has made the modern logic analyzers as useful as they are, and the lack thereof is also partially responsible for the demise of the old beasts. Well, that and he needs a lab cart then to carry around what I can slip in my pocket today. Take that!

To Give Is Better Than To Receive

Better to give a talk at a hacker event, that is. Or in your hackerspace, or even just to a bunch of fellow nerds whenever you can. When you give the talk, don’t be afraid to make it too “easy” to understand. Making a tough topic comprehensible is often the sign that you really understand it, after all, and it’s also a fantastic service to the audience. And also don’t be afraid that your talk isn’t “hard core” enough, because with a diverse enough crowd, there will absolutely be folks for whom it’s still entirely new, and they’ll be thankful.

These were the conclusions I got from talking to a whole range of people at Chaos Communication Camp the weekend before last, and it’s one of the great opportunities when you go to an event like this. At Camp, there were a number of simultaneous stages, and with so many talks that new ones are still being released. That meant that everyone had their chance to say their bit, and many many did.

And that’s great. Because it’s obvious that getting the work done, or diving deep into a particular topic, is part of the hacker experience, but it’s also equally important to share what you’ve gained with the rest of the community. The principle of spreading the knowledge is a cornerstone of our culture, and getting people up to talk about what they’ve learned is the manifestation of this cultural value. If you know something, say something!

Of course, when you’re not at a conference, you could be writing up your hacks and sending them in to the tips line (hint, hint!). That’ll work too.