- cross-posted to:
- homeassistant@lemmy.world
- cross-posted to:
- homeassistant@lemmy.world
Sounds interesting, if it’s all locally hosted it might actually be a good-
I leaned heavily on Codex throughout the build.
Aaaaand I’m out.
I get the argument about quick and easy development turnaround, but I just can’t trust anything vibecoded, let alone models from that company.
Ever considered reading the code it produces?
I haven’t seen this particular code, but I’ve had the pleasure of working with AI-generated code before. There was a single line that I ended up using in my manually written version, the rest of it was just hard to read and maintain. The advice for editing that code I got from the person who sent it was to just feed it to the model and ask it to make those changes.
I don’t want to outsource my brain and I find it untrustworthy to see someone advocate for it.
Then just write it yourself, problem solved.
Of course, that’s what I do. That’s what I recommend everyone should do, or get someone to do for them. My point is that I’m sceptical of the type of person to endorse the opposite.
I just can’t trust anything vibecoded
This is bespoke software that has not been shared publicly. You don’t have to trust it, because the only person who will ever use it is Simon Green.
The article’s not really about the software, it’s about the capabilities of UWB radios. Don’t skip out on the article just because of a passing mention of vibecoding.
I was more thinking about the mentality and ethics behind using it and considering it worth mentioning, not so much whether I personally would get to use it. That was poor phrasing on my part, sorry. What I meant is that it implies a certain mindset that I find deeply untrustworthy.
I did read the rest of the article. It’s interesting, no doubt.
Six trash cans is insane.

