fubarx

• Catch 22
• Hitchhiker's Guide to the Galaxy (series)

Where you rotate so far right you end up at the left.

ESPN video of her story: https://youtu.be/U6CoScOIK_I

Back in college, a local doughnut shop would open at 3am to start making the run for the day. If you were stoned or pulling an all-nighter, it was worth the 15m walk. They would sell you fresh, warm doughnuts out the back.

Nowadays, a lot of places do the fresh doughnut thing. But it's not the same, getting it at 3am.

https://www.espressif.com/en/news/ESP32-S3-BOX-3

There's a model with a more expensive dock, or one without. The one without worked fine. But it had to be the Box 3 not Box 2. It worked pretty well and you could create custom images to indicate whether it was listening, thinking, etc.

Instructions here: https://www.home-assistant.io/voice_control/s3_box_voice_assistant/

The box isn't powerful enough to run an LLM itself. It's just good enough as an audio conduit. You can either use their cloud integration with ChatGPT, or now, Anthropic Claude. But if you had a powerful Home Assistant server, say an Nvidia Jetson or a PC with a beefy Nvidia GPU, you could run local models like Llama and have better privacy.

This is from earlier this year. I imagine they've advanced more since then.

Their LLM integration is super cool. I messed with it for a previous job. Way better than Alexa or Google Home.

One Docker env variable and one line of code. Not a heavy lift, really. And next time I shell into the container I don't need to remind everyone to activate the venv.

Creating a venv in Docker just for the hell of it is like creating a symlink to something that never changes or moves.

NEW, automated children's bicycle. Guaranteed to teach the little tyke how to ride! *

• ^Comes with training wheels, and adult monitor standing by at all times.^

I can think of only two reasons to have a venv inside a container:

• If you're running third-party services inside a container, pinned to different Python versions.

• If you do local development without docker and scripts that have to activate the venv from inside the script. If you move the scripts inside the container, now you don't have a venv. But then it's easy to just check an environment variable and skip, if inside Docker.

For most applications, it seems like an unnecessary extra step.

I've been using ChatGPT, specialized ones on Huggingface, and a bunch of local ones using ollama. A colleague who is into this deep says Claude is giving him best results.

Thing is, depends on the task. For coding, I've found all suck. ChatGPT gets you up to a point, then puts out completely wrong stuff. Gemini, Microsoft, and CodeWhisperer put out half-baked rubbish. If you don't already know the domain, it will be frustrating finding the bugs.

For images, I've tried DALL-E for placeholder graphics. Problem is, if you change a single prompt element to refine the output, it will generate completely different images with no way to go back. Same with Adobe generators. Folks have recommended Stability for related images. Will be trying that next.

Most LLMs are just barely acceptable. Good for casual messing around, but I wouldn't bet the business on any of them. Once the novelty wears off, and the CFOs tally up the costs, my prediction is a lot of these are going away.