Ryan Ross

B.S. Computer Engineering

Declared: Mathematics minor · Physics minor · Robotics Undergraduate Certificate

Graduated cum laude · GPA 4.4 weighted

Autonomous daily scheduling engine

• Wrote to a live personal calendar with zero unwanted events since launch, by keeping every scheduling decision in deterministic tested Python and letting the language model only word facts already computed.
• Kept class, sleep and the two days before a deadline unmovable, and surfaced every missed commitment as an explicit move, cut or cram decision instead of sliding it silently.
• Built 1,408 automated tests across 48 modules and 15 retained scenario batches, by recording every expected outcome before the run and treating disagreement as a defect in the code.
• Achieved unattended 07:00 execution with no session open, by running the engine from Task Scheduler and delivering through a Telegram bot after the obvious channel could not fire headless.

Spaced-repetition learning platform · learncogito.com

• Shipped 52 interactive courses in four days with SM-2 spaced repetition and a progress dashboard, by templating one course structure and replacing its contents.
• Consolidated 32 divergent copies of one stylesheet into a single shared sheet, found by auditing my own shipped source five weeks after launch.
• Reduced hosting cost to zero while serving 8.3 MB of course content, by shipping static pages with no framework, build step or server, and keeping learner progress in browser storage.

Print workbook on the algebra and trigonometry behind Calculus I

• Published and sold a 185-page, 33-lesson workbook on the algebra and trigonometry underlying Calculus I, by working every problem myself with no notes and rewriting each lesson that failed that pass.
• Cut author-only content leakage to zero across every release, by building a pipeline that turns a personal study course into a sellable book and fails if private material survives.
• Closed a live exposure serving the paid workbook at a guessable public URL, by moving the file outside the deployed directory and adding a build assertion that fails if it reappears.

• Fixed a one-sentence acceptance criterion before starting each of 61 build phases, and retired one phase rather than reword a criterion a later decision had made unsatisfiable.
• Recorded 129 architectural decisions with their reasoning and rejected alternatives, by treating any hard-to-reverse choice as unfinished until the alternatives it beat are written down.
• Maintained 361 source-grounded reference pages where every claim carries its citation, by building tooling that verifies each citation exists and samples whether the source supports the claim.