Allow me to introduce #MLL coding, the counterpart to #LLM vibe coding. MLL (Manual Labor of Love) coding allows one to spend more time doing a thing, and lets one get better, faster, and 100% understood code.

On plane #3 to home from IETF 125. I am exhausted. Shenzhen was nice. It is a clean, friendly city and very affordable.

IETF 125 in Shenzhen

I had an interesting conversation during the IETF hackathon with people getting heavily into coding with AI. To get AI to work for serious projects, they need to write down a lot of assumptions and other information, the observation being that they are now documenting things they should have written down for their junior engineers but didn't... but now that the AI needs this information, they are doing it.

Which, from an economic standpoint, is totally backwards assuming that a junior engineer costs a lot more than an AI.

@emacdona Buried in the web client UI when run locally is a "Reset Node DB" feature. This morning I ran that on my Slot 20 (DC) node and it cleared out all the nodes that were apparently left over from when it was on slot 9. I'll wait and see what it picks up, but so far no nodes found. But I think that might be a morning thing because even on slot 9 I see that many of the nodes have not been heard from for awhile.

Schools shouldn't be training centers for proprietary software.
https://www.korte.co/gyon
#Education #opensource

@emacdona Yeah, the channel thing is a bit confusing.

@emacdona Do people actually use these things to communicate? I see a lot of nodes but zero messages.

@emacdona I put the second unit on slot 20, and I am definitely picking up some nodes. But I obviously don't understand this stuff. Some of the same node appear on both slots. I thought slot = frequency, so I am not sure how some of the nodes are on multiple frequencies.

@emacdona I am using that stubby thing that came with the kit but have a longer one which I will put on there. And yes, all indoors.

@emacdona Yes. Slot 9. It is pretty amazing because there are a ton of nodes once you hit the beltway, but inside the beltway there aren't that many. Maybe they are on slot 20.

Adventures in Meshtastic

I’ve always wanted to play around with LoRa and Meshtastic to see what it can do. Thanks to a little prodding by @emacdona I bought a pair of cheap, Heltec kits.

I seriously have no idea what I am doing here, but managed to futz my way through flashing one of the devices. I let it run over night and woke up to 128 nodes discovered. Pretty interesting.

@emacdona If you have looked into note taking and syncing services, you might get bookmarks as a part of that.

If you think that that orchestrated AIs creating Pull Requests is a problem, wait until they start trying to be LinkedIn influencers.

Phillip Hallam-Baker has defined the term "Superficial Intelligence" (SI), which better describes the artificial intelligence we are currently experiencing.

https://mailarchive.ietf.org/arch/msg/ietf/HuQyJJHCF0y9Lrr543WQah63MQs/

I maintain pypandoc — 14M downloads/month, used by Adobe, Google, Microsoft, Apple, OpenAI and many more.

I just overhauled my sponsorship pages. If you or your company depend on open source infrastructure (you do), here's how to help keep it maintained:

💛 https://github.com/sponsors/JessicaTegner

Open source has a free-rider problem. You can be part of the solution.

#OpenSource #Python #FOSS #FundOpenSource

Today we had a fire alarm in the office. A colleague wrote to a Slack channel 'Fire alarm in the office building', to start a thread if somebody knows any details. We have AI assistant Glean integrated into the Slack, and it answered privately to her: "today's siren is just a scheduled test and you do not need to leave your workplace". It was not a test or a drill, it was a real fire alarm. Someday, AI will kill us.

@hugovk Awesome! Yes, thanks. I cannot explain why I did not see that before.

Apparently I was not supposed to eat all the Girl Scout cookies. Some of these house rules are downright complicated.

I am noticing bot accounts hitting GitHub repos and approving (not merging, but approving) PRs. The GitHub docs on how to stop non-collaborators from doing this are difficult to understand. So far I have resorted to old-fashioned branch protection. Has anybody with a divining rod figured out the #github permissions to specifically address this issue?