docs(readme): reframe stack as judgment, not inventory#23
Merged
Conversation
…nale Reframe the stack section as judgment, not inventory. Each tool gets one line stating the constraint it answered and the alternative rejected. Closes the gap between "I used X" (inventory) and "I chose X over Y for this reason" (judgment) — the latter is what senior reviewers look for. Adds a "What I would change with hindsight" paragraph identifying which parts of the integration stack are heavier than the product needed (Mongo + worker queue), so the README reflects what the load test results actually showed rather than the stack as-built. No content removed; framing change only.
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.
Summary
README change only. Replaces the one-line tech-stack list with a "Stack & why" section where every tool gets one line stating the constraint it answered and the alternative rejected. Adds a closing "What I would change with hindsight" paragraph identifying the parts of the integration stack that load testing showed were heavier than the product needed.
No content removed. No code changes. No infra changes.
The
v1.0-portfoliotag stays pinned to the previous main SHA per the repo-freeze plan; this commit lands onmainas the post-freeze framing fix.Test plan