I was just watching a talk that described this exact thing, which apparently has a fancy name - Epistemic Trespassing. One of the biggest culprits is overestimating how transferable your skills in one domain to another domain is, of course caused by intellectual pride.
Any of us can fall for this.
![Chat transcript
Me:
before you do it, answer this question
code like this is bad. why did you do it?
index.astro
title: post.data.slug.startsWith('agentic-systems-') ? Agentic Systems: ${post.data.title} : post.data.title,
[slug.astro]
const isAgenticSystemsSeries = entry.data.slug.startsWith('agentic-systems-')
3:28 PM
Model:
You are right. That code is bad.
I added it as a shortcut to support the temporary eyebrow experiment without introducing series metadata. Then, when the short titles looked unclear on the blog list, I added a second slug check to reconstruct the full title. That compounded the original shortcut instead of stepping back and simplifying the model.
The problems are:
It treats the slug as structured metadata. A slug is a URL identifier, not a reliable source of presentation semantics.
It creates hidden coupling. Renaming a slug can silently change the page heading and list title.
The series rule is duplicated across two pages.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:h6g6ajj7ruv5giebfomdv64q/bafkreiffzgfna27savq3gcx7jjothxqhrzygpkpjyp5zbnnl6cudk7bceu)
![2. Files Read
### [context-provided]
These were injected into my system prompt/context automatically:
- AGENTS.md (project context / rules — provided as system instructions)
### [explicitly-read]
Files I actively read using the read tool or bash:
1. docs/canopy-spec.md — full product specification
2. docs/repo-structure.md — monorepo layout and conventions
3. docs/plans/phase-1-progress.md — Phase 1 implementation status
4. docs/plans/phase-2-progress.md — Phase 2 implementation status
5. docs/plans/phase-3-rss-feeds.md — Phase 3 plan + progress (combined)
6. docs/plans/phase-last-defer.md — deferred items / known bugs
7. docs/decisions.md — design decisions log
8. packages/shared/src/types.ts — shared TypeScript types
9. apps/web/wrangler.toml (first 30 lines) — Cloudflare bindings config
10. apps/web/package.json (first 30 lines) — dependencies and scripts
I also ran find commands to get the full file tree.
### [did NOT read]
- All source code files in apps/web/src/ (~50+ files): components, hooks, lib modules, API
routes, pages, CSS
- docs/plans/phase-1-foundation.md and docs/plans/phase-2-tags-highlight.md (detailed plans — I
read the progress files instead)
- docs/schema.sql (full SQL reference schema)
- migrations/*.sql (individual migration files)
- scripts/migrate.sh
- Config files: turbo.json, root package.json, root tsconfig.json, pnpm-workspace.yaml,
apps/web/tsconfig.json, apps/web/next.config.ts, apps/web/tailwind.config.ts,
apps/web/open-next.config.ts, apps/web/postcss.config.mjs, apps/web/env.d.ts,
apps/web/components.json
- packages/shared/src/constants.ts, packages/shared/src/index.ts
- README.md
- .claude/settings.local.json
- All build output in .next/, .open-next/, .turbo/, .wrangler/](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:h6g6ajj7ruv5giebfomdv64q/bafkreiaji3mnqf6i6qndbwwxy6jzbbinbqucemd2abuwawrsjthm36474i)
