A Flipper Zero would be the modern equivalent, I suppose. I like the idea of being able to turn off devices in a certain radius - but I don’t like the idea of everyone having one. Having ultimate power over the wireless noise in my immediate vicinity - awesome .. but seeing someone empty their pockets at the airport and a Flipper Zero in the inspection box - not so fun.
It’s going to be a wild and woolly future, the more these kinds of shenanigans become relevant.
RF remotes are harder to hack together but similar principle. Whether IR or RF, the codes are common across all devices of the same model/protocol.
Sure enough, after a while the neighbour learnt their TV only worked if they kept the volume down in the evening.
Can't see the video from this location, so may be just restarting stuff in it.
[0] https://hackaday.com/2018/04/20/laser-projector-ditches-galv...
The screens are each a bar of micro LEDs. Each eye has a mirror that oscillates every frame to smear the LED bar across your field of view.
If you've ever seen those bike wheel displays, where the light-up spokes make a pattern when the wheel spins - it's that, but as a VR headset.
For further background, they were developed from an earlier system called the "Private Eye" - still a few references to them on the web e.g. [0]. I've built a circuit to drive one from a Pi Zero - amazing gadgets for 90's tech.
Right, kind of like an LLM skimming and missing the core points :)
OP didn't ask for "Anything you've vibe-coded" but explicitly asked for code written with LLMs that is high quality and structurally sound, and "creates more value than it creates technical debt". That's why I felt like reviewing the code in the first place, and why I gave the feedback.
I understand now that maybe it felt like my impromptu code review came out of nowhere, but I thought you were actually trying to give OP a accurate sample, so sorry if it felt like it came out of nowhere :)
I don't think anyone says it's not possible to get the LLM to write code. The problems OP has with them is that the code they write starts out good but then quickly devolves when the LLMs get stuck in the weird ruts they have.
I have no doubt that a C developer with sufficient knowledge of dBus, bluetooth, the HRM profile and linux could have written the C code in a day. Adding the HTTP server again would be easy if the developer also had experience of that (n.b. there was a minor compiler error when I tried it on another system due to a slightly different version of libmicrohttpd). Adding the API would be straighforward (but tedious) and similiarly the web page (the web page was an one-shot after Claude wrote the API, vis. "Create a web page to display a real time plot with history using the API").
So overall I'd answer that that human developers would could have pulled that off in a day are few and far between (and likely to cost a lot more than $25 plus a day of my time).
And do I think the code is good enough? Yes, more than good enough. I could take it and run with it, against that because it ended up 100% AI-generated I feel a bit like leaving it as a monument to "pure AI".
After all, I never intended to release it - it was this thread that made my throw it up on Github as an example for the OP.
Just thought I'd clarify as I've seen prompts like this and people thinking this is the actual motivation from the "inside the LLM" or whatever, which is a bit far away from the truth.
In https://github.com/lowrescoder/BlueHeart/blob/68ab2387a0c44e... for example, it doesn't actually do SSE at all, instead it queues up a complete HTTP response each time, returns once and then closes the stream, so basically a normal HTTP endpoint, "labeled" as a SSE one. SSE is mentioned a bunch of times in the docs, and the files/types/functions are labeled as such, but that doesn't seem to be what's going on internally, from what I could understand. Happy to stand corrected though!
As a personal bit of development last weekend. I can see inconsistences myself, some of which result from scope creep during development (starting with the idea of a text-only app and then grafting on the web side) - it literally only started because I wanted a working example of bluetooth and dBus in C, the rest of it just joined the ride.
As for the SSE, no expert on that myself, however if you watch the messages in the browser console it appears to push updates with sporadic notes about using polling instead.