Pioneering Visual Logic for USC
Before visual scheduling became a pattern in modern tools, it had to be designed first:mapping time into space and making it computationally readable.
Context
In 2005, building a dynamic scheduling system in a browser was not a standard problem. It was an early experiment in visualizing time as structure rather than form.
Breakthrough
It didn't happen in front of a screen - it happened somewhere between Vermont and Beverly, in LA traffic.
While riding a bus to USC - line 217 - it finally hit me: I wasn't looking at a schedule, I was looking at a coordinate system pretending to be a calendar.
After that, it stopped pretending.
It became a calendar.
Solution
Time stopped being abstract. It became spatial.
- Time mapped directly into a visual grid
- Pixel-based event positioning
- Collision detection as scheduling validation
- Spatial rules replacing traditional logic flows
Outcome
A visual scheduling model implemented before this approach became mainstream in calendar tools.
The result wasn't a UI feature. It was a different way of representing time in software.
- Layered slider system simulating grid behavior
- State-based navigation logic tied to position
- SASS-driven layout variants (left/right/top/bottom shifts)
- Responsive grid from 3840px down to 280px
- Real-time active tile tracking
- Data-group based multi-slot rendering logic
This approach predates mainstream visual scheduling tools like Google Calendar — though I'm still not ruling out they might have been subconsciously inspired.
$ I don't just write code.
$ I engineer logic for ideas that don't yet have a solution