Product Engineer/Architect navigating the AI revolution
I'm a working software engineer. Most of what I write comes from the same place: code is easy to generate now and just as easy to make unmaintainable, and the old engineering habits matter more for it, not less. prickles.org is where I collect those habits as short, specific tenets — guard clauses, screaming architecture, verifiable specs, and the rest. If something here is useful, that's where the full set lives.
Markdown supported · ⌘↵ to post
Oliver Zehentleitner
This gets even more interesting with coding agents.
A second copy is no longer just maintenance debt. It can become a second source of truth that an agent confidently follows after the original has changed.
I've seen the same rule copied into CLAUDE.md, AGENTS.md, tool-specific config and project docs. Keeping those synchronized is already hard for humans; agents just make the stale copy actionable.
So I increasingly think DRY applies to knowledge and instructions at least as much as it does to code: one canonical source, references everywhere else.