xj9

now that I'm the ripe old age of 35, I can confirm what I've always believed: many of the symptoms of "old age" are actually the result of a sedentary lifestyle without the padding inherent in youth. a little exercise and daily stretches will make you feel "younger" aka somewhat more healthy.

Huh so I guess I'm 🤔 trying to blend erlang/otp with clojure and python flavored ruby

That's a fucked up elixir

It needs types, but I'm picking my battles for now

another vibecoding experiment: mqtt-senses

I'll be doing a write-up about the experience soon. This is part of my project to explain how AI engineering works and what it takes to get quality code from slop. The final goal is to build an LLM server with a full voice and reasoning stack to explain how it all works and, finally, to measure how a gamer-tier GPU stacks up to cloud-scale AI for realistic applications.

My goal isn't to normalize the use of AI, but to demonstrate what is realistically possible using these tools. Not only that, but to show that there's a difference between asking a tool to do a job for you and using a tool to complete a task. Obviously, delegating your thinking to AI is harmful, but that doesn't mean that AI cannot be used productively. Sure, maybe AI accelerates laziness, but it can also accelerate other things.

Obviously, we will also be discussing the implications of AI under Capitalism.

a couple of fun gems from this project: I found a slightly more complete port of hardwood for chicken 5. I'm using hardwood for all my concurrency needs. Though it should be noted that deepseek v4 flash is pretty bad at writing well-formed concurrent code even within the erlang-style actor model. I'm using a handful of eggs that I've been playing with as part of 2682. Namely clojurian and callable-data-structures. I think more work is needed to make data structures that are as ergonomic as clojure using scheme primitives, but its been interesting to see all the permutations that just a couple of small macros can tidy up.

@rubixhelix@kolektiva.social @valkyrie@wandering.shop depending on the workload, maybe. with software problems, often times you need a certain amount of efficiency just to be viable. I do like the idea of task federation as a building block, but at a large scale it would probably only be good at solving problems that need massively parallel processing; a la folding@home. anything involving IO will probably not work outside of a fast LAN, and that's only if 1Gbps÷nodes is fast relative to the work.

@rubixhelix@kolektiva.social @valkyrie@wandering.shop I agree, I'm only suggesting that there are lot of cases where "it works" depends on having an optimal solution. You typically need both.