Revisit Previous Projects

Although I have (minimally) ""completed"" every project this far. I feel like I am skimming the surface constantly.

I want to go back to the previous projects from the Prep Month and Sprint 1.

And try to understand the feedback more and then improve them.
And any concepts I am struggling with book Office Hours meetings to help with this.

rough notes from Meeting with Daniel about this:

output and error handling - mostly done

cli files - spend time here with comments

file parsing - two big things: no matter what file you are given, a useful error (some places where it will panic) (or not give a useful message)

concurrency (spend most time here)

two things
- extension: making a computing cache
  - rather than putting a value
  - when you constructed it, to take a key and produce a value
  - only public method, is get, produces a value as a side effect
sample solutions, compare and contrast these four solutions, how are htye different better/worse
big things to think about, when we are dealing with concurrency, think hard about what things you can guarantee
one of the example tests in the sample solution

bazmurphy / immersive-go-course