Lore blog: engineering knowledge in the AI era

Practical writing on how engineering teams manage knowledge, measure velocity, and navigate the AI era.

Lore vs. Claudebin: sharing a Claude Code session as a URL. Claudebin pastes a single Claude Code session to a public URL. Lore captures your team's Claude Code, Codex, and Cowork sessions as searchable, private-by-default, forkable threads. Here is the difference and when each fits.
AI made you faster. It made your team slower.. 91% of engineers use AI coding tools. Their teammates can see none of the reasoning. Here's why shared AI session context is the real team productivity problem in 2026.
Your Team Is in Claude All Day. Where Does That Thinking Go?. Your team's best thinking is happening inside Claude Code sessions. Lore captures it, shares it, and makes sure no one builds the same dead end twice.
AI engineering knowledge management: a guide for 2026. AI coding agents moved your team's reasoning out of docs and into closed terminal sessions. This guide explains what AI engineering knowledge management is, why the old playbook broke, and how to fix it in 2026.
The reasoning behind your code exists. Your team just can't find it.. AI coding tools are capturing your team's engineering reasoning in real time. The problem isn't that context is disappearing. It's that nobody can find it.
The best ways to share a Claude Code session (2026). A practical, honest rundown of every way to share a Claude Code session in 2026, from screenshots and copy-paste to terminal recordings and Lore, with the trade-offs of each.
How to fork a Claude Code or Codex session. Forking lets you pick up where someone else's AI coding session left off. Here's how to fork a Claude Code or Codex session with Lore, what a fork actually carries forward, and when to use it.
How to onboard engineers in the AI era. Onboarding broke when the reasoning behind your codebase moved into AI coding sessions. Here's how to onboard new engineers in 2026 by handing them the sessions, not weeks of Slack archaeology.
Lore vs. Braintrust: what each does and when to use which. Lore and Braintrust both get filed under "AI observability," but they solve different problems. Lore captures your team's AI coding sessions; Braintrust evaluates the LLM features you ship. Here's how to choose.
Lore vs. LangSmith: what each does and when to use which. Lore and LangSmith both touch "AI" and "observability," but they watch different things. LangSmith observes the agents inside your product; Lore captures the coding sessions your team runs to build it. Here's how to choose.
Lore vs. ShareGPT: sharing AI chats vs. sharing coding sessions. ShareGPT shares a ChatGPT conversation as a static snapshot. Lore captures and shares the coding-agent sessions your team runs in Claude Code, Codex, and Cursor. Here's the difference and when each fits.
How to save your favorite prompts from Claude Code and Codex. Your best prompts are buried in scrollback. Here's how to save and reuse your favorite prompts from Claude Code and Codex with Lore, so the prompt that finally worked is one click away.
I Gave Up Solo Building to Join Tanagram.. 6 months of building alone taught me what I was missing. Here's what happened when I stopped working in the stands and got back on the field.
'AI teams merge 98% more PRs.' What that's doing to your code.. AI tools merge PRs 98% faster but introduce quality debt. Learn why traditional velocity metrics fail and 4 better KPIs to measure true engineering productivity.
Prompt tracking vs. AI session sharing: what to use when. "Prompt tracking" means two different things in 2026. A practical guide to telling them apart, and choosing the right tool for the one you actually need.
How to share a Claude Code session with your team. A practical guide to sharing a Claude Code thread with teammates, what gets exported, what stays private, and how to fit it into PR review, RCA, and onboarding.
AI made me a faster engineer. It didn't make us a better team.. 70% of developers say AI helped their personal productivity. Only 17% say it improved team collaboration. That's the most under-discussed gap in 2026 engineering, and it's about to compound.
Managing Tribal Knowledge for Engineers: A Practical Guide. Every engineering team has knowledge that lives only in people's heads. Here's why that's gotten worse in the AI era, and what to actually do about it.