1. **PHP Vulnerabilities (PHP2Shell, CVE-2026-109618/109619)** - Critical RCE flaws leading to widespread patching, outages, and security discussions. 2. **AI and Large Language Models (LLMs)** - Tools like Claude, Cursor, and Qwen; debates on AI-generated code, security risks, and agentic workflows. 3. **Arduino Library Updates** - New/updated libraries: ESP-NOW MIDI, SuperDMZ, LottieMCU, FastLEDHub, JPEGDEC, AMY Synthesizer, etc. 4. **NixOS and Configuration Management** - Discussions on Nix configuration modularization, Git tracking, and debugging challenges. 5. **GitHub/GitLab Security & Workflow Issues** - Dependabot auto-merge flaws, repository migrations, and supply chain risks. 6. **Python Ecosystem Developments** - PyBeach 2026 talks, PEP-827, Python 3.15 updates, and performance optimizations.
Updated:
Preflight (1.1.0) for esp32 by James Cartwright
➡️ https://github.com/diydoohickeys/Preflight-Arduino
Captive-portal WiFi setup, web logger, and an OTA update page with rollback for ESP32 projects.
ESP32 library, coding, tech content
Anti-Patterns in Software Blogging, by @michael:
https://refactoringenglish.com/blog/anti-patterns-software-blogging/?ref=frontenddogma.com
Anti-patterns in software blogging
Embracing Playful Imperfection With the CSS “random()” Function, by @utilitybend (@smashingmag):
CSS random function front‑end tech
XC_GUI (1.1.4) for stm32/rp2040/esp32/samd by Gigasitron Xcross
➡️ https://github.com/Gigasitron-xcross/XC_GUI
Lightweight buffered graphics primitive library for embedded displays.
#ArduinoLibs #ArduinoLibraries #stm32Libraries #rp2040Libraries #esp32Libraries #samdLibraries
Embedded library release
When brilliant minds are unemployed and unsure if they still have a career we truly have fucked up. Also: fastest general ellipse algorithm ever.
It didn't make a single commit over the past 5h. Not quite sure what it is doing, but it looks like the task was too complex for it...
Lately I've been wondering how to handle security vulnerability reports for my (volunteer) projects. Specifically:
1. Do we really need to keep vulnerability reports confidential? If private, that means I am the only one who can fix it, and I might not have the time/interest. Some other important bugs are not reported privately, and many projects are not public-facing network servers. If the vulnerability was found via an LLM, anyone can throw an LLM at the codebase and find it too with little effort.
2. How much do I really need to care about CVEs? This is just time-consuming paperwork for me. I understand it might be important for security researcher recognition.
3. What happens if the security vulnerability isn't patched in a timely manner, or by the end of the embargo period? Should I feel bad? What if it affects the reputation of the software? I don't want this stuff to invade my life.
I very much care about making things right for users, but I don't know how to balance things out with a healthy maintainer role.
Discussing software security and vulnerability handling
8 CLI HTTP Clients to Test APIs and Download Files in Linux Read more here https://www.tecmint.com/command-line-http-clients-for-linux/
#linux #opensource #tecmint
Linux CLI HTTP clients guide
I experimented with getting Claude to port the @scverse anndata package to R and compared it to what we have done with anndataR. Overall, it was pretty easy and the results are not perfect but quite impressive.
Check out the blog post for more details https://lazappi.id.au/posts/2026-10-25-anndata-r-claude/.
Anndata R porting blog post.
5/5 Absolutely it is faster to create a more functional appearance of a prototype than it was just a year ago. Sure, those protos actually do work for some definition of 'work' - small scale, half-implemented but unverified edge cases, and so on. You may call this "agents in the middle". But any velocity you might win in this stage of development, will be paid by commensurate complications at other stages.
Prototype development trade‑offs discussion
4/5 But never mind that - let's assume you CAN test all the versions your proto team armed with Claude can spin up. Do you not think your competition will do exactly the same, and the market shifts to require more, not less effort early on? If you don't, you haven't been in the software business long, or you haven't really thought how the dynamics work.
Discussing AI prototyping impact
3/5 Not to mention that tests of ideas bring entirely different results when measured at conceptual, blueprint, paper proto, or polished level. And not in the way you might think. Polished looking protos divert attention to superficial details, tainting the results.
Discussion of prototype testing in software
2/5 Existence of 30 prototypes, even if perfectly executed, does not magically turn into comparative evidence their market acceptance and business potential. That still requires testing, and that testing always was the hard part. The concepts still need to be thoughtfully deconstructed into the meaningful components, because no one, not even Meta, has the audience to test all combinations and variations.
Discussion on AI prototype testing
6b. For some complex scenarios—such as testing behavior on a specific complex state to find an obscure bug—that may not be possible. Writing tests first really helps with this as it forces you to think about the behavior of your code and how you're going to test it before you write it.
Testing first encourages smaller, more modular units of code, which generally means better code. A good book for getting started with the "test first" approach is Test Driven Development by Example, by Kent Beck.
Discussion of test-driven development
uns hat um 3 uhr nachts das LKA wachgeklingelt und angeschrien es gab bei PHP eine sicherheitslücke und wir müssen das nun fixen während sie da stehen ??
New issue of #Perl Weekly:796 - Perl and PHP - https://perlweekly.com/archive/796.html
The Perl and Raku Foundation by the Numbers
Apache2::Request: Fixing the build
Why the PAGI spec is moving to Perl 5.24
Ex::Op: A drop-in replacement for Exporter
German Perl/Raku Workshop 2027
Everyday date and time handling in Perl with T
YAPC::Tokyo 2026
London Perl & Raku Workshop 2026
Punk: Perl MVC, compiled at boot
2026.41 Riscy Business
Trionic Finishing
The Weekly Challenge #396
[...]
Perl programming topics
CasioST75256 (1.2.0) by GrayKazu
➡️ https://github.com/tkhoi0821-svg/Casio-classwiz-880BTG-lib
Driver for the ST75256 192x63 LCD (+ icon row) of the fake Casio fx-880BTG: Unicode fonts (VI, TH, ZH) and icons, QR codes, WraithUI widgets with keyboard, haunted FX, MJPEG and C2V video.
Hardware library, code repository
Analyzed a project that we just delivered, successfully. Except we had higher expectations to what success looks like. Yep, AI.
We expected to come up with a significantly higher degree of automation than what we did. While we (devs) report that without the tooling we used it would have been 3--5x the effort, the others report 0.5x our effort doing it *differently* with their tools.
What fascinates me the most is the time when we run automation that should have been unattended, but ended up attending for 200 hours. We did something while the automation was running. And we accepted the automation run slower than any reasonable expectation should allow for.
Project analysis with AI automation tools
ivarvong/lantern: Animated, steppable code explainers. Zero-dependency TypeScript, SVG output, browser and Cloudflare Workers.
https://github.com/ivarvong/lantern
TypeScript tool for code explanations
Twelve years of distributed SQLite – Philip O'Toole
https://philipotoole.com/twelve-years-of-distributed-sqlite/
SQLite database blog post