Yes, I think so. Electronics prototyping is so accessible now, and there's such a deluge of inspirational projects out there to learn from. YouTube is a gold mine, and I'll leave links to a few channels I follow, below.
If you get an Arduino or Esp32 microcontroller (maybe in one of those starter-kits with various sensors), some breadboards, assorted jumper-cables and a kit with electronic components (resistors, caps) you'll be good to go. A device like a wall clock most likely won't require soldering, since it won't be jostled or moved around much.
If you already have Home Assistant running, I think it should be simple. Most of the time you can buy devices with pins already soldered and it's just the matter of connecting them together. AIs are pretty good with ESPHome configs. You can even take a picture so that they can help you identify the correct pins. Some coding may be required for drawing things on the display though.
> Has anyone find a useful way to to something with Claws without massive security risk?
Not really, no. I guess the amount of integrations is what people are raving about or something?
I think one of the first thing I did when I got access to codex, was to write a harness that lets me fire off jobs via a webui on a remote access, and made it possible for codex to edit and restart it's own process, and send notifications via Telegram. Was a fun experiment, still use it from time to time, but it's not a working environment, just a fun prototype.
I gave openclaw a try some days ago, and besides that the setup wrote config files that had syntax errors, it couldn't run in a local container and the terminology is really confusing ("lan-only mode" really means "bind to all found interfaces" for some stupid reason), the only "benefit" I could see would be the big amount of integrations it comes with by default.
But it seems like such a vibeslopped approach, as there is a errors and nonsense all over the UI and implementation, that I don't think it'll manageable even in the short-term, it seems to already have fallen over it's own spaghetti architecture. I'm kind of shocked OpenAI hired the person behind it, but they also probably see something we from the outside cannot even see, as they surely weren't hired because of how openclaw was implemented.
Well for the OpenAi part, there was another HN thread on it where several people pointed out it was a marketing move more than a technical one.
If Anthropic is able to spend millions for TV commercial to attract laypeople, OpenAi can certainly do the same to gain traction from dev/hacky folks i guess.
One thing i've done so far -not with claws- is to create several n8n workflows like: reading an email, creating a draft + label, connecting to my backend or CRM, etc which allow me to control all that from Claude or Claude Code if needed.
It's been a nice productivity boost but I do accept/review all changes beforehand. I guess the reviewing is what makes it different from openclaws
The question is: what type of mac mini.
If you go for something with 64G + +16 cores, it's probably more than most laptop so you can run much bigger models without impacting your job laptop.
If the idea is to have a few claws instances running non stop and scrapping every bit of the web, emails, etc, it would probably cost quite a lot of money.
But if still feels safer to not have openAI access all my emails directly no?
Very nice, thanks! It’s great to be able to play with viz!
For a deeper tutorial, I highly recommend PyTorch for Deep Learning Professional Certificate on deeplearning.ai — probably one of the best mooc I’ve seen so far
Wow thanks for sharing!
Could you explain how you made the specs?
Did you already know pretty much everything you wanted to cover before hand? Was one CC session enough to go through it?
In my experience, trying to make a plan/specs that really match what I want often ends in a struggle with Claude trying to regress to the mean.
Also it’s so easy to write code that I always have tons of ideas I end up implementing that diverge from the original plan…
- It was definitely not one CC session. In fact, this spec is a spin-off of several other specs on several other branches/projects.
- I've actually experienced quite the opposite: I suggest an idea for the spec and Claude says "great idea!" Then I change my mind and go in the opposite direction: "great idea!" again. Once in a while, I have to argue with Claude to get my idea implemented (like adding dependencies to parse into a proper AST instead of regex.)
- One tip: it's very useful to explain the "why" to Claude vs the "what." In fact, if you just explain the why/problem without a specific solution, Claude's suggestions may surprise you!
Mermaid diagrams are even better because you don't waste characters on the visual representation but rather the relationships between them. It's the difference between
graph TD
User -->|Enters Credentials| Frontend[React App]
Frontend -->|POST /auth| API[NodeJS Service]
API -->|Query| DB[(PostgreSQL)]
API --x|Invalid| Frontend
DB -->|User Object| API
API -->|JWT| Frontend
Mermaid diagrams automatically render on Markdown and IDE chat windows as in VSCode or Cursor. So you get the best of both worlds, a graph you can look at a ND manipulate with the mouse but also in a format LLMs can read.
reply