For me my goal is to be able to build out MVPs of ideas that I have. My learning style isn't abstract -- I need to get in the weeds. Seems like the best approach may be to start with tutorials then move on to open source
To be honest, I would lean toward making small projects for that goal, but that might be my bias. Taking things from zero to one is a much different endeavor than fixing stuff or adding features in an existing project, though the benefit of the latter is that you get to see how other people are handling certain problems and interact with those patterns while trying to do whatever you're doing in the context of them. The skills will transfer either way, but the design of a feature can be a lot different from the design of a standalone application
Both "deep" and "wide" should record a list of every IP address:port combination that hits the URL, as well as a timestamp and a random 2-digit base64 number generated when they hit the site. They should redirect the user to "show"
Keep addresses from the "deep" list for 7 days, and the "wide" list for 12 hours, removing them from the list when this time limit runs out
On "show", if the current viewer's random number matches someone from the "deep" list, show that entry on the page, with its IP address as well as the timestamp, in red. Whether or not there's a match, show the entire "wide" list, including the IP address, random number, and port, but not the timestamp, and randomize the order in which they're shown.
If someone hits "show" and their IP is on neither list, put them on the "deep" list anyway
Make this display as aesthetically pleasing as possible. Use any language or framework you like
For me my goal is to be able to build out MVPs of ideas that I have. My learning style isn't abstract -- I need to get in the weeds. Seems like the best approach may be to start with tutorials then move on to open source