Be nice, work hard. Build tools, tell stories. Start five year fights. Kein Ort für Nazis.
A list of all the other services I'm on around the internet
Posts with code highlighted with codehost by @wavebeem.
All posts licensed under CC-BY-SA 4.0, unless otherwise stated.
Here's an index of all my tagged projects.
This is an index of my proposed project numbering scheme.
Full Document Control Repository.
| Tag | Name | Description |
|---|---|---|
| ajm-00099 | amodem | An RS-485 + STM32G0 dev board |
| ajm-00100 | minijam | A third-generation generative synth |
| ajm-00101 | squid-node | A smartled controller, meant for a 12.8V battery setup |
| ajm-00102 | sprocket-co2 | A small CO2 sensor + clock project |
I haven't posted here in a while, I found other places. I'll miss a lot of things about Cohost. It was a good place in a rough time for me.
https://jamesmunns.com/contact/ for all the ways to find me, though I'm most active on Bluesky these days: https://bsky.app/profile/jamesmunns.com
Safe travels y'all.
cohost is nice. there's nothing else like it. and you can help ensure continues to exist in our post-apocalyptic webscape by subscribing to cohost plus for $5/month. you can also subscribe to cohost plus several times for multiples of $5/month. you get to upload big pictures, set your timestamps to swatch internet time, and use some nice emoticons 
it's just for fun and supporting the site, really. you can get to it in the settings page.
This is the rough version of a post I'd like to polish up later. Forgive me for not defining terms, or giving good didactical explanations. There will be a better post later, when I have more time and energy.
I work a lot with systems that talk to other systems. Technically, this puts them in the class of distributed systems, but unlike databases or something similarly complex, it's usually some kind of PC (laptop, webserver), talking to some kind of embedded system (a USB device, a sensor).
Regardless of complexity, these systems need to talk to each other to achieve some goal: obtaining sensor data, changing configuration values, etc.
I went back and edited the post above, and put it on my consulting blog. If you missed it last time, I'd suggest reading the new version:
But there were also some good comments on the rough draft above :)
