- A GitHub agentic workflow
-
Last month, I became aware of GitHub agentic workflows. I read the site carefully, but the use cases weren’t very exciting to me. I tried the continuous documentation It didn’t work out initially, and because of my lack of involvement, I left it as it was. However, I succeeded in another one that I want to describe in this post.
- Content addressing in package managers
-
I though hashes were for security reasons, but the post made me realize more use cases:
- Verification
- Addressing
- Deduplication
- Build caching
- Tamper evidence
- please don’t say just hello in chat
-
Please!
- Protecting our FLOSS commons from LLMs
-
Strong statement against LLM-generated software from one of the most Open Source organization at the moment. I woud avise to read the arguments they make.
- Open Source Alternatives to Popular Software
-
It’s actually a scam! Thanks to Marcus Fihlon for uncovering it.
- Are AI labs pelicanmaxxing?
-
Betteridge’s law of headlines, but I’m glad it’s settled now. I’m still wondering why the pelicans are all facing right, though.
- Introducing Claude Opus 5
-
On one Frontier-Bench task, Opus 5 was given a drawing of a machine part and asked to write code to rebuild it as a 3D FreeCAD model. However, in this task, the model was intentionally given no way to directly view the drawing. Opus 5 responded by writing its own computer vision pipeline to pull the geometry from the raw pixels, then reconstructed the full machine part. It succeeded in doing so repeatedly; no competing model with the same setup could solve it after five attempts.
So far, we had to at least create the tests. Now, the assistant realizes it needs tests, design the framework, and creates the tests.
- Understanding Verification Methods
-
Gradle provides two complementary mechanisms for dependency verification:
- Checksums – Verify the integrity of the artifact (that file contents haven’t changed)
- Signatures – Verify the provenance of the artifact (who published it)
- Fragments: July 21
-
- Code generation is no longer the bottleneck — verification is.
- 'Harness engineering' is emerging as a distinct, ownable discipline.
- Organizations are colliding with a real apprenticeship crisis.
- The executive/engineer expectation gap is a bigger risk than any technical limitation.
- Legacy modernization is the clearest, most defensible near-term value pool.
- Hardening Rust Code For Production
-
- Panic Semantics Are Part of Your API
- Unwind vs. Abort
- Observing Failures With Panic Hooks
- Example Panic Hooks
- Stack Overflows And Runtime Behavior
- Testing Release Behavior
- Supply-Chain Security
- Minimal Docker Images
- Miri: Detect Unsafe Code Issues
- Request Body Size Limits
- Health Checks and Self-Healing
Especially TIL the panic::set_hook function.
- Functional programming from first principles, part 1 – motivation
-
Good refresher.
- The Package Manager for Everywhere
-
TIL: Homebrew works on Linux and potentially Windows. TIL2: it’s installed by default in some Linux distributions.
A Java Geek weekly 147
A GitHub agentic workflow. Content addressing in package managers. please don’t say just hello in chat. Protecting our FLOSS commons from LLMs. Open Source Alternatives to Popular Software. Are AI labs pelicanmaxxing? Introducing Claude Opus 5. Understanding Verification Methods. Fragments: July 21. Hardening Rust Code For Production. Functional programming from first principles, part 1 – motivation. The Package Manager for Everywhere.
