Share Your Projects: Imperfectionism

Everyone has a standard for publishing projects, and they can get pretty controversial. We see a lot of people complain about hacks embedded in YouTube videos, social media threads, Discord servers, Facebook posts, IRC channels, different degrees of open-sourcing, licenses, searchability, and monetization. I personally have my own share of frustrations with a number of these factors.

It’s common to believe that hacking as a culture doesn’t thrive until a certain set of conditions is met, and everyone has their own set of conditions in mind. My own dealbreaker, as you might’ve seen, is open-sourcing of code and hardware alike – I think that’s a sufficiently large barrier for hacking being repeatable, and repeatability is a big part of how hacking culture spreads.

This kind of belief is often self-limiting. Many people believe that their code or PCB source file is not a good contribution to hacking culture unless it meets a certain cleanliness or completeness standard. This is understandable, and I do that, too.

Today, I’d like to argue against my own view, and show how imperfect publishing helps build hacking culture despite its imperfections. Let’s talk about open-source in context of 3D printing.

Continue reading “Share Your Projects: Imperfectionism”

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.

How Do They Do That?

Last week’s Chaos Communication Camp is kinda a big deal: 6,000 hackers all out in a field all need power, food, drink, networking, and of course, sewage in the middle of nowhere. Oh yeah, plus video services on multiple simultaneous stages, custom phone infrastructure, a postal service, and even a diesel train. How is that even possible to run with only volunteers? How do they even know how to run something this scale?

My wife asked me this question while we were driving up to Berlin, and the answer is of course the same as it is to “Excuse me, can you tell me how to get to Carnegie Hall?” Practice.

But it’s not just practice. It’s also passing down the lessons learned to the next generation, making procedures that are not 100% dependent on the people doing the jobs, but can be passed on to the next volunteer willing to pick up the torch.

And then I was interviewing [Jens Ohlig] and [Mitch Altman] about the early days of the second wave hackerspaces in America for the podcast. (Some great interviews – go check it out!) The central story there is essentially the same: the critical missing ingredient that lead to the blossoming of US hackerspaces was simply a set of instructions and design principles – drawing on the experience of established hackerspaces.

Sharing information is a fundamental cornerstone of the hacker ethic, and it gives the next hacker a leg up. Contributes to the global hive mind. And it makes things possible that would otherwise seem impossible. Pushing the hacker state-of-the-art is what Hackaday is all about, and we’re used to thinking of it in terms of a particular microcontroller library, but seeing how the same sharing makes impossible logistics possible was inspirational. Don’t be afraid to start small and iterate – and take good notes.

Finding The Right Hack Is Half The Battle

Sometimes you just get lucky. I had a project on my list for a long time, and it was one that I had been putting off for a few months now because I loathed one part of what it entailed — sensitive, high-accuracy analog measurement. And then, out of the blue I stumbled on exactly the right trick, and my problems vanished in thin air. Thanks, Internet of Hackers!

The project in question is a low-vacuum regulator for “bagging” fiberglass layups. What I needed was some way to read a pressure sensor and turn on and off a vacuum pump accordingly. The industry-standard vacuum gauges are neat devices, essentially a tiny little strain gauge on a membrane between the vacuum side and the atmosphere side, in a package the size of a dime. (That it’s a strain gauge is foreshadowing, but I didn’t know that at the time.) I bought one for $15 ages ago, and it sat on my desk, awaiting its analog circuitry.

See, the MPX2100 runs on 12 V and puts out a signal around 40 mV on top of a 6 V offset. That voltage level is inconvenient for modern 3.3 V microcontroller ADCs, and the resolution would get clobbered by the 6 V signal if I just put a voltage divider on it. This meant whipping together some kind of instrument amplifier circuit to null out the 6 V and amplify the 40 mV for the ADC. The circuits I found online all called for 1% resistors in values I didn’t have, and mildly special op-amps. No fun, for me at least. So there it sat.