I build mdedit.io — a no-account Markdown editor with live preview, collaboration and AI assistance I’m looking for feedback on the public beta of mdedit.io: https://mdedit.io Repository: https://github.com/MatthiasHertel21/mdedit mdedit.io is a browser-based Markdown editor focused on writing, structuring, previewing, sharing and exporting longer Markdown documents. It does not require an accou
When you build a PowerShell project from multiple files, the natural structure is clear: enums first, then classes, then functions. Each group has its own place, and as long as dependencies only flow in one direction, that structure works perfectly. But sometimes a function depends on a class, and that class calls the function. There is no longer a clean boundary between the two groups — they need
The drift problem nobody told you about If you have used Claude Code, Cursor, Aider, or any other AI coding agent across more than two projects, you have felt this: You start project A. You copy the .agents/ folder (or CLAUDE.md, or .cursorrules) from your last project. You tweak two things. Done. You start project B six weeks later. You copy from project A. You tweak three things this time. Now
Cross-posted from the Stigmem blog. Today we're releasing stigmem v1.0: A stable, open-source specification and reference implementation for a federated knowledge fabric for AI agents. Stigmem = Stigmergy + Memory. Stigmergy (Greek stigma — mark; ergon — work) is the coordination mechanism you see in ant colonies and termite mounds: agents don't communicate directly with each other. Instead, they
More rules should mean better output. That's the intuition. I spent weeks building a comprehensive CLAUDE.md — 200 lines covering naming conventions, security rules, error handling, architectural patterns, import ordering, type safety requirements, and more. I was proud of it. I'd thought through every scenario. Then I scored the output. 79.0 / 100. My carefully crafted documentation was actively
The drift problem Every project that ships a translated README has the same lifecycle: Someone writes README.md in English. A contributor opens a PR with README.zh.md. Great. Three months later, English has six new sections. Chinese has the original. A second translator opens README.es.md. Spanish gets translated from… which version? The current README.md? Or README.zh.md, by accident, because t
§0 — Hook The work-pool schema that runs the paragraf project names three work types: spec, package, and issue-bucket. Only two of the three have a defined The first article introduced a methodology that produced a working library — Two parallel improvements happened in the one week that followed. The first was The second improvement was a sprint. Two new color-related packages shipped under The
The previous three posts covered how events flow from the SDK to the UI, how the timeline renders, and how tool cards visualize. This final post looks at SwiftWork's infrastructure — how data is stored, how state is restored, how Markdown is rendered, how code is highlighted, and how API keys are managed. These components are independent, but all essential to making the app usable. SwiftWork uses