Common Sense Refactoring of a Messy React Component | Alex Kondov
One thing I've learned from all the consulting I've done is that rewrites rarely lead to anything good. Almost in all cases, when you have an application runnin
Modular Nest Dresser - Stackable | Thuma
Discover the Nest dresser from Thuma. This modular dresser provides easy customization for any space with stackability and a sleek, modern design.
Proposal Assembly 2026: ToU extension to prohibit LLM-extrusions
Here is the proposed addition for the ToU that @Gusted and I agreed on post-assembly for the upcoming membership vote. 🙏 The discussion for this proposal is available for Codeberg e. V. members in the forum: https://forum.codeberg.org/d/139-resolutions-for-assembly-on-codeberg-taking-a-stand-a...
Concept Attractors in LLMs and their Applications
Empirically, we see that for prompts pip_{i}, pjp_{j} in each concept 𝒞\mathcal{C}, there exists a layer ll where:
sugarcube
Design tokens, generated CSS, and optional components. Build front ends on strong, reusable foundations.
The Bitter Lesson of LLM Extensions
From ChatGPT Plugins to Agent Skills, a look at how we've been trying (and failing) to extend LLMs for the last three years.
For me flake-parts is the best way to manage Nix flakes
28 votes, 29 comments. Raw flakes get messy fast with repeated forAllSystems boilerplate and nested attributes everywhere. flake-parts uses a module…
Don’t classify. Hallucinate!
A useful pattern for LLM classification at scale is to let it hallucinate plausible, fake entities. Then resolve to real ones.
Tonight I integrated an LLM into every part of the request/response life-cycle of the the browser to see what I could do. aifoc.us/interception/ It was a lot of fun, in the demo linked I can rewrite a web page as before it's rendered by the browser to give me just a summary of the contents.
interception
aifoc.us
