alanb43/hearsay

Your own virtual sports insider, always up to date on your favorite players and teams.

I'm an April 2023 graduate in computer science + applied statistics from the University of Michigan. I've been learning to program for a couple of years, taking on various software engineering roles along the way (most recent highest):

• 🚚 Amazon, full-time
• 💜 PixieBrix
• 🔥 Amazon
• 🌱 Humana
• 💊 Acuitii

While you're here, check out a few projects I've pinned below. You can also:

• Contact / hire me: [email protected]
• Learn more about me: alanbergsneider.com

hearsay's Issues

Apply singleton pattern for all class instances used in main

Why?
To clean up & make the source code much more readable. Also will shorten the list of places in which bugs can occur.

How?
The singleton pattern should be applied to all of HearSay's custom modules (essentially *.py excluding main). This will

Anything else?
Python singleton reference

Fix profile management

For the live/deployed version of HearSay's back-end, profile management had to be removed (commented out) because it was only designed for local system user (single user) and was not a part of the project's MVP. To re-implement this (great!) feature, one should look into using cookies to store a user's profile data on their browser, and to make handling the creation of a profile an independent action that a single thread carries out for a user.

make HearSay spin new threads to handle requests

In light of the back-end server being live, it should probably be made to act as a real server, spinning threads (up to a threshold) to handle requests concurrently. One could make the argument for a load balancer being introduced, but for now a hard limit on the number of concurrent requests allowed would be fine.