Reject Modernity, Return To 80s, Learn C.

We’re not exactly sure how old [SnailMail] is, but he’s probably a member of Generation Alpha considering that to our wizened eyes the lad looks only slightly older than a fetus– which makes it all the more impressive that he’s written his own text editor, from scratch, in C– on a 386. See, [SnailMail] tried to learn the modern way, with IDEs that have code completion and AI integration, but his thoughts couldn’t gel in the modern environment. So he went online and bought an old IBM-compatible complete with monochrome amber monitor, and a whole 4MB of RAM. Big spender that he is, [SnailMail] upgraded that to 8MB.

Rather than fall victim to the siren song of Wolfenstien 3D or SimCity, he set out to learn to code: C, specifically, since that language bridges four decades between [SnailMail] and his new PC. Even more specifically, he got ahold of disks for Borland Turbo C and Turbo C++, which brings back memories for some of us. Of course the lad also had to learn how to use a DOS PC at the same time, but a teen in the 80s with a fresh box would have climbed the same steep learning curve. Some of you probably remember doing so yourselves. Just like you–or the hypothetical teen in the 80s–[SnailMail] did it not by googling or begging Claude for answers, but by digging into books. Many books.

After all the reading, he started with a text editor, something we remember being a pretty big project not given to first year students. Video evidence suggests he pulled it off. He describes how his solution works from about 8:00 in the video, so you greybeards in the audience can judge his work for yourself.

If you’re a member of Gen Alpha reading this and looking to learn to program, we cannot recommend this technique highly enough– [SnailMail] is going to have a better understanding of the underlying logic of computer science than a lot of CS grads being frocked today. Especially when you consider he ends by promising to learn assembly, something we heartily endorse.

Continue reading “Reject Modernity, Return To 80s, Learn C.”

Antweight Combat Robot Tips, Shared From Experience

[Harry]’s newest robot, the MotherLoader V2, looks fantastic but was ultimately more of a learning experience and test bed for some experimental features. Luckily for us, [Harry] created a lengthy write-up detailing everything that he tried and revised.

3D printing and aluminum both feature heavily in antweight robots, in part because when contestants are limited to 150 grams it’s safe to say that every bit counts. We recommend reading [Harry]’s entire article to get all the details, but here are some of the bigger takeaways.

Treads provide a lot of contact surface, but there are a lot of ways they can go wrong. Pliability and grip have to be good matches for the robot’s design, otherwise the tread might bunch up or otherwise perform poorly when trying to maneuver. [Harry] had several dud efforts, but ended up with a great result by borrowing an idea from another competitor: composite tracks.

These have an inner track printed from flexible TPU filament, and an outer layer formed by casting silicone directly onto the 3D printed core. It’s a somewhat involved process, but the result is a durable and custom-fitted inner track on the inside, and a softer grip outside. Best of both worlds, and easily tailored to match requirements.

Speaking of TPU, [Harry] discovered that it can be worth printing structural parts with TPU. While ABS is usually the material of choice for durable components, printing solid parts in TPU has a lot to recommend it when it comes to 150 gram robots. Not only can TPU parts be stiff enough to hold up structurally, but they can really take a beating and happily spring back into shape afterwards.

We’ve seen [Harry]’s work before on antweight combat robots, and it’s always nice to peek behind the scenes and gaze into the details. Especially for processes like this, where failures are far more educational than successes.

Learn What Did And Didn’t Work In This Prototyping Post-Mortem

[Tommy] is a one-man-shop making electronic musical things, but that’s not what this post is about. This post is about the outstanding prototyping post-mortem he wrote up about his attempt to turn hisĀ Four-Step Octaved Sequencer into a viable product. [Tommy] had originally made a hand-soldered one-off whose performance belied its simple innards, and decided to try to turn it into a product. Short version: he says that someday there will be some kind of sequencer product like it available from him, “[B]ut it won’t be this one. This one will go on my shelf as a reminder of how far I’ve come.”

The unit works, looks great, has a simple parts list, and the bill of materials is low in cost. So what’s the problem? What happened is that through prototyping, [Tommy] learned that his design will need many changes before it can be used to create a product, and he wrote up everything he learned during the process. Embedded below is a demo of the prototype that shows off how it works and what it can do, and it helps give context to the lessons [Tommy] shares.

Continue reading “Learn What Did And Didn’t Work In This Prototyping Post-Mortem”