
Optimizing course planning when UofT couldn’t
#webdev #tools
I created ECE Pathmaker for 1500+ ECE students because Magellan was too slow: ecepathmaker.com
Engineering challenges
- Redesigning existing university software to be more intuitive and responsive (core interactions from 30s to 0.4s)
- Using a directed acyclic graph to track prerequisites, allowing for real-time validation (compared to saving and waiting 30s)
- Applying data structures and writing algorithms to parse, save, and display the changing user data
- Working with dndkit library APIs, and coming up with workarounds when finding limitations in card element interactions
Tech Stack
Optimizing course planning when UofT couldn’t
#webdev #tools
I created ECE Pathmaker for 1500+ ECE students because Magellan was too slow: ecepathmaker.com
Engineering challenges
- Redesigning existing university software to be more intuitive and responsive (core interactions from 30s to 0.4s)
- Using a directed acyclic graph to track prerequisites, allowing for real-time validation (compared to saving and waiting 30s)
- Applying data structures and writing algorithms to parse, save, and display the changing user data
- Working with dndkit library APIs, and coming up with workarounds when finding limitations in card element interactions

Optimizing course planning when UofT couldn’t
#webdev #tools
I created ECE Pathmaker for 1500+ ECE students because Magellan was too slow: ecepathmaker.com
Engineering challenges
- Redesigning existing university software to be more intuitive and responsive (core interactions from 30s to 0.4s)
- Using a directed acyclic graph to track prerequisites, allowing for real-time validation (compared to saving and waiting 30s)
- Applying data structures and writing algorithms to parse, save, and display the changing user data
- Working with dndkit library APIs, and coming up with workarounds when finding limitations in card element interactions



