Repository navigation
Rewrite README in a more natural voice - #2
Merged
Merged
Conversation
Drops the AI-flavored decoration: emoji headers, em-dashes, "portfolio-grade", "showcase", "polished", section dividers between every heading. Reframes the intro around how the project actually started (Java prototype for class, then rewritten) so the tone reads like a developer note rather than marketing. Also adds a "Notes on a few decisions" section with the small tradeoffs I had to actually think about: why hand-rolled JSON, why HttpURLConnection over OkHttp, why ServiceLocator over Hilt, why salted SHA-256 instead of a KDF, why exportSchema is off. These are the things I'd talk through in an interview, so they belong in the README. Content-wise, the feature list, architecture diagram, tech stack, project layout, test inventory, roadmap, and download section are all preserved. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
SultanZhalifa
added a commit
that referenced
this pull request
Oct 12, 2026
SultanZhalifa
added a commit
that referenced
this pull request
Oct 12, 2026
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.
Drops the AI-flavored decoration: emoji headers, em-dashes, "portfolio-grade", "showcase", "polished", section dividers between every heading. Reframes the intro around how the project actually started (Java prototype for class, then rewritten) so the tone reads like a developer note rather than marketing.
Also adds a "Notes on a few decisions" section with the small tradeoffs I had to actually think about: why hand-rolled JSON, why HttpURLConnection over OkHttp, why ServiceLocator over Hilt, why salted SHA-256 instead of a KDF, why exportSchema is off. These are the things I'd talk through in an interview, so they belong in the README.
Content-wise, the feature list, architecture diagram, tech stack, project layout, test inventory, roadmap, and download section are all preserved.