Bowling Ball Layout Visualizer and Plunko V2.
A working project board for the apps, tools, sports technology systems, testing labs, and engineering builds I am actively developing, upgrading, researching, or preparing.
Bowling Ball Layout Visualizer and Plunko V2.
Started-but-paused builds and future systems.
QA automation, AWS/API workflows, 3D web apps, computer vision, sports technology, analytics, and embedded systems.
Purpose: This page tracks projects before they become finished portfolio entries.
In Progress: Current work is focused on the Bowling Ball Layout Visualizer and Plunko V2.
Planned Work: The Price Tracker and Speed & Rev Calculator are started but on hold; planned work includes maintenance logging, Power BI analytics, and the RDRestore master's build starting in the Fall.
A client-side 3D web app that renders a bowling ball's drilling layout and converts a layout entered in one notation (Dual Angle, VLS, or 2LS) into every other system, with the ball drawn in 3D. Built on a dependency-free geometry engine covered by a property-based test suite for round-trip, handedness, and cross-system agreement.
An in-progress upgrade to Plunko: seeded generation, shareable runs, improved shot prediction, better save recovery, long-term stats, and game QA test cases are already done. Remaining focus is upgraded art and UI polish.
A bowling ball catalog and price tracking system: a searchable ball database, retailer and manufacturer sources, a Node and Express API with Prisma and PostgreSQL, scheduled scraping with confidence-scored matching, and planned Discord commands and alerts. Started, currently on hold.
A video-based sports-tech tool that estimates ball speed and rev rate from a clip, rejecting videos where the needed landmarks aren't measurable. Runs entirely in the browser: reads video frames, uses computer-vision detection to track the ball, and calculates speed and rev rate from fixed lane distances. Started, currently on hold.
An MS Computer Engineering build for a rotating, partially submerged, temperature-controlled bowling ball de-oiling system: a Raspberry Pi, display, float switch, temperature sensor, motorized cradle, warm water, and safety-oriented control logic. Currently planning, starting in the Fall.
Fill → Heat → Rotate → Monitor → Wipe
A planned bowling-center maintenance tool that translates mechanic call logging into a helpdesk-style ticket system: issue type, lane, severity, status, downtime, resolution, and recurring warnings.
A planned bowling performance dashboard focused on KPIs, trends, ball usage, spare conversion, patterns, centers, and reporting workflows, using structured Pin-Sighter-style data for dashboard practice, data cleaning, KPI modeling, Power Query, SQL, and visual storytelling.