Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Build a small program (any language, no big libraries) that makes data representation tangible: convert an integer between decimal, binary, hex, and octal in both directions; show a signed value in n-bit TWO'S COMPLEMENT for a chosen width (and detect overflow on add); and print the UTF-8 byte sequence (and code points) for an input string. Implement the conversions yourself rather than calling a built-in formatter, and include a few unit tests (e.g. 0.1 + 0.2 ≠ 0.3 demonstrated, −128 as 8-bit, an emoji that is 4 UTF-8 bytes).
Correct two-way conversion across decimal/binary/hex/octal, implemented by hand (positional math), not delegated to a library printf.
Signed n-bit encoding/decoding is correct incl. the asymmetric range and invert-plus-one; overflow on add is detected.
Distinguishes code points from bytes; UTF-8 byte counts are right (ASCII=1, many emoji=4); no 'one char = one byte' bug.
A few meaningful tests (float inexactness, edge widths); readable, well-named code.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A number-base & encoding explorer ## Goal Build a small program (any language, no big libraries) that makes data representation tangible: convert an integer between decimal, binary, hex, and octal in both directions; show a signed value in n-bit TWO'S COMPLEMENT for a chosen width (and detect overflow on add); and print the UTF-8 byte sequence (and code points) for an input string. Implement the conversions yourself rather than calling a built-in formatter, and include a few unit tests (e.g. 0.1 + 0.2 ≠ 0.3 demonstrated, −128 as 8-bit, an emoji that is 4 UTF-8 bytes). ## Acceptance criteria - [ ] Base conversion: Correct two-way conversion across decimal/binary/hex/octal, implemented by hand (positional math), not delegated to a library printf. - [ ] Two's complement: Signed n-bit encoding/decoding is correct incl. the asymmetric range and invert-plus-one; overflow on add is detected. - [ ] Unicode / UTF-8: Distinguishes code points from bytes; UTF-8 byte counts are right (ASCII=1, many emoji=4); no 'one char = one byte' bug. - [ ] Tests & clarity: A few meaningful tests (float inexactness, edge widths); readable, well-named code. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.