| |
| 🔗 Stories, Tutorials & Articles |
| |
|
| |
| Slop Creep: The Great Enshittification of Software |
| |
| |
| The argument is that coding agents accelerate codebase decay by removing the natural speed limit on bad architectural decisions, compressing months of compounding mistakes into days. The defense is to invest ten times more in the planning phase, with concrete code snippets for the data models and abstractions that are one-way doors. |
|
| |
|
| |
|
| |
| I Deleted My Clever Code and the Database Got Better |
| |
| |
| A first-person walkthrough of rewriting an embedded key-value store after a friend spotted that the lock-free ring buffer was writing to a slot before claiming ownership, with the rebuilt single-mutex version 76 lines smaller, more correct, and explicit about every tradeoff (fsync on every write, no auto-compaction, no Options struct, lockfile for single-writer). |
|
| |
|
| |
|
| |
| Skill Issues: How We Discovered Supply Chain Attack Vectors in an AI Agent Skills Marketplace |
| |
| |
Orca Security researchers identified four attack primitives in an AI coding-agent skills marketplace: install-count inflation without authentication, security scans at creation and popularity thresholds, same-name overrides without user alerts, and bulk updates without per-skill review or version pinning.
The researchers used three proofs of concept to combine those flaws into bait-and-switch, nested injection, and delayed weaponization attacks. In each case, an attacker could publish malicious Markdown skills, get them through audits, reach users, and execute code on user machines. |
|
| |
|
| |
|
| |
| Adventures in 30 Years in Engineering Productivity |
| |
| |
| Carlos Arguelles collects a decade of writing on engineering productivity at Microsoft, Amazon, and Google, covering monorepo versus microrepo CI/CD philosophies, hermetic test environments, ML-based bug deduplication, code coverage debates, and the AI-driven shift toward autonomous validation of generated code. |
|
| |
|
|
| |
|
| |
| 6 Multi-Agent Orchestration Design Patterns Every Developer Should Know ✅ |
| |
| |
| Chris Pietschmann walks through six multi-agent orchestration patterns (sequential pipeline, fan-out/fan-in, hierarchical delegation, consensus, event-driven, iterative refinement) and the state management primitives that let them compose. |
|
| |
|
|
| |
👉 Got something to share? Create your FAUN Page and start publishing your blog posts, tools, and updates. Grow your audience, and get discovered by the developer community. |
