blog: Onboarding an Engineer vs. Onboarding an Agent - #4100
Draft
benfrank241 wants to merge 1 commit into
Draft
Conversation
Uses a process every team already understands to explain what an agent without memory is missing. Separates what onboarding actually transfers: the code, the conventions, the decisions, and the dead ends. An agent gets the first for free and essentially none of the rest, because those live in git history, pull request threads, and people's heads. The asymmetry the post is built on: an agent reads a codebase faster than any human and is the only member of the team who cannot learn anything that is not in the code, because for it every day is Monday. Names the two compensations honestly. Writing it down produces a document that goes stale silently. Re-explaining every session is something we would treat as a management failure if we did it to a person. Ends on where the analogy breaks: agent memory is more literal than human memory, and an agent has no social sense of a codebase. The goal is not a synthetic colleague. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AE4NCnCKXUzNDF3N9FaQja
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uses a process every team already understands to explain what an agent without memory is missing.
What onboarding actually transfers, separated out: the code, the conventions, the decisions, and the dead ends. An agent gets the first for free and essentially none of the other three, because those live in git history, pull request threads, and people's heads.
The asymmetry the post is built on: an agent reads a codebase faster than any human, and is also the only member of the team who can never learn anything that isn't in the code. For an agent without memory, every day is Monday.
Names the two compensations honestly. Writing it down produces a document that goes stale silently. Re-explaining every session is the thing we'd treat as a management failure if we did it to a person — if a new hire needed the same explanation every morning, you wouldn't blame them.
Where the analogy breaks, which the post says plainly: agent memory is more literal than human memory, and an agent has no social sense of a codebase. The goal isn't a synthetic colleague; it's to stop making the fastest reader on the team start from nothing every morning.
Composite 87.7/100, specificity 100, readability 97. All cross-links verified live.
Draft — for review, not merge.
🤖 Generated with Claude Code
https://claude.ai/code/session_01AE4NCnCKXUzNDF3N9FaQja