Vibing, AI Style

This week, the hackerverse was full of “vibe coding”. If you’re not caught up on your AI buzzwords, this is the catchy name coined by [Andrej Karpathy] that refers to basically just YOLOing it with AI coding assistants. It’s the AI-fueled version of typing in what you want to StackOverflow and picking the top answers. Only, with the current state of LLMs, it’ll probably work after a while of iterating back and forth with the machine.

It’s a tempting vision, and it probably works for a lot of simple applications, in popular languages, or generally where the ground is already well trodden. And where the stakes are low, as [Al Williams] pointed out while we were talking about vibing on the podcast. Can you imagine vibe-coded ATM software that probably gives you the right amount of money? Vibe-coding automotive ECU software?

While vibe coding seems very liberating and hands-off, it really just changes the burden of doing the coding yourself into making sure that the LLM is giving you what you want, and when it doesn’t, refining your prompts until it does. It’s more like editing and auditing code than authoring it. And while we have no doubt that a stellar programmer like [Karpathy] can verify that he’s getting what he wants, write the correct unit tests, and so on, we’re not sure it’s the panacea that is being proclaimed for folks who don’t already know how to code.

Vibe coding should probably be reserved for people who already are expert coders, and for trivial projects. Just the way you wouldn’t let grade-school kids use calculators until they’ve mastered the basics of math by themselves, you shouldn’t let junior programmers vibe code: It simultaneously demands too much knowledge to corral the LLM, while side-stepping any of the learning that would come from doing it yourself.

And then there’s the security side of vibe coding, which opens up a whole attack surface. If the LLM isn’t up to industry standards on simple things like input sanitization, your vibed code probably shouldn’t be anywhere near the Internet.

So should you be vibing? Sure! If you feel competent overseeing what [Dan] described as “the worst summer intern ever”, and the states are low, then it’s absolutely a fun way to kick the tires and see what the tools are capable of. Just go into it all with reasonable expectations.

Hackaday Podcast Episode 317: Quantum Diamonds, Citizen Science, And Cobol To AI

When Hackaday editors Elliot Williams and Al Williams need a break from writing posts, they hop on the podcast and talk about their favorite stories of the past week. Want to know what they were talking about? Listen in below and find out!

In an unusual twist, a listener sent in the sound for this week’s What’s This Sound competition, so it turns out Elliot and Al were both stumped for a change. See if you can do better, and you might just score a Hackaday Podcast T-shirt.

On the hacking front, the guys talked about what they hope to see as entries in the pet hacking contest, quantum diamonds (no kidding), spectrometers, and several science projects.

There was talk of a tiny robot, a space mouse—the computer kind, not a flying rodent—and even an old-fashioned photophone that let Alexander Graham Bell use the sun like a string on a paper cup telephone.

Things really heat up at the end, when there is talk about computer programming ranging from COBOL to Vibe programming. In case you’ve missed it, vibe coding is basically delegating your work to the AI, but do you really want to? Maybe, if your job is to convert all that old COBOL code.

Want to read along? The links are below. Be sure to leave your robot plans, COBOL war stories, and AI-generated Vibe limerics in the comments!

As always, the human-generated Hackaday Podcast is available as a DRM-free MP3 download.

Continue reading “Hackaday Podcast Episode 317: Quantum Diamonds, Citizen Science, And Cobol To AI”

This Week In Security: No More CVEs, 4chan, And Recall Returns

The sky is falling. Or more specifically, it was about to fall, according to the security community this week. The MITRE Corporation came within a hair’s breadth of running out of its contract to maintain the CVE database. And admittedly, it would be a bad thing if we suddenly lost updates to the central CVE database. What’s particularly interesting is how we knew about this possibility at all. An April 15 letter sent to the CVE board warned that the specific contract that funds MITRE’s CVE and CWE work was due to expire on the 16th. This was not an official release, and it’s not clear exactly how this document was leaked.

Many people made political hay out of the apparent imminent carnage. And while there’s always an element of political maneuvering when it comes to contract renewal, it’s worth noting that it’s not unheard of for MITRE’s CVE funding to go down to the wire like this. We don’t know how many times we’ve been in this position in years past. Regardless, MITRE has spun out another non-profit, The CVE Foundation, specifically to see to the continuation of the CVE database. And at the last possible moment, CISA has announced that it has invoked an option in the existing contract, funding MITRE’s CVE work for another 11 months.

Continue reading “This Week In Security: No More CVEs, 4chan, And Recall Returns”

FLOSS Weekly Episode 829: This Machine Kills Vogons

This week, Jonathan Bennett chats with Herbert Wolverson and Frantisek Borsik about LibreQOS, Bufferbloat, and Dave Taht’s legacy. How did Dave figure out that Bufferbloat was the problem? And how did LibreQOS change the world? Watch to find out!

Continue reading “FLOSS Weekly Episode 829: This Machine Kills Vogons”

Announcing The Hackaday Pet Hacks Contest

A dog may be man’s best friend, but many of us live with cats, fish, iguanas, or even wilder animals. And naturally, we like to share our hacks with our pets. Whether it’s a robot ball-thrower, a hamster wheel that’s integrated into your smart home system, or even just an automatic feeder for when you’re not home, we want to see what kind of projects that your animal friends have inspired you to pull off.

The three top choices will take home $150 gift certificates from DigiKey, the contest’s sponsor, so that you can make even more pet-centric projects. You have until May 27th to get your project up on Hackaday.io, and get it entered into Pet Hacks.

Continue reading “Announcing The Hackaday Pet Hacks Contest”

Illustrated Kristina with an IBM Model M keyboard floating between her hands.

Keebin’ With Kristina: The One With John Lennon’s Typewriter

The Clawtype, a one-handed number with a handy strap and a good-sized display.
Image by [akavel] via GitHub
Reader [akavel] was kind enough to notify me about Clawtype, which is a custom wearable chorded keyboard/mouse combo based on the Chordite by [John W. McKown].

First of all, I love the brass rails — they give it that lovely circuit sculpture vibe. This bad boy was written in Rust and currently runs on a SparkFun ProMicro RP2040 board. For the mouse portion of the program, there’s an MPU6050 gyro/accelerometer.

[akavel]’s intent was to pair it with XR glasses, which sounds like a great combination to me. While typing is still a bit slow, [akavel] is improving at a noticeable pace and does some vim coding during hobby time.

In the future, [akavel] plans to try a BLE version, maybe even running off a single AA Ni-MH cell, and probably using an nRF52840. As for the 3D-printed shape, that was designed and printed by [akavel]’s dear friend [Cunfusu], who has made the files available over at Printables. Be sure to check it out in the brief demo video after the break.

Continue reading “Keebin’ With Kristina: The One With John Lennon’s Typewriter”

Linux Fu: Stopping A Runaway

The best kind of Hackaday posts are the ones where there was some insurmountable problem with an elegant solution devised through deep analysis of the problem and creativity. This is not one of those posts. I’m sure you are familiar with bit rot. You know, something works for a long time and then, for no apparent reason, stops working. Well, that has been biting me, and lacking the time for the creative, elegant solution, I decided to attack it with a virtual chainsaw.

It all started with a 2022 Linux Fu about using autokey.

The Problem

I use autokey to give me emacs-style keystrokes in Web browsers and certain other programs. It intercepts keystrokes and translates them into other keystrokes. The problem is, the current Linux community hates autokey. Well, that’s not strictly true. They just love Wayland more. One reason I won’t switch from X11 is that I haven’t found a way to do something like I do with autokey. But since most of the powers-that-be have decided that X11 is bad and Wayland is good, X11 development is starting to show cracks.

In particular, autokey isn’t in the normal repositories for my distro anymore (KDE Neon). Of course, I’ve installed the latest version myself. I’m perfectly capable of doing that or even building from source. But lately, I’ve noticed my computer hangs, especially after sleeping for a long time. Also, after a long time, I notice that autokey just quits working. It is running but not working and I have to restart it. The memory consumption seems high when this happens. Continue reading “Linux Fu: Stopping A Runaway”