July 2020 1HaskellADay Problems and Solutions

• 2020-07-31: Well, that's random. Generating random numbers and sequences is today's #Haskell problem. Today's #haskell solution shows that I can (<*>) that monad, first go, without even looking it up or anything. So, yeah, I'm walking pretty tall right now. 
• 2020-07-30: Kate and Shoaib are going on vacation. Commander Adama in Star Wars tells us that for today's #haskell problem, we are to "Make it so, Number one." And: there they go! Shoaib and Kate, going on a vacay, havin' fun, and type-safely, at that, because of the #haskell solution 'n stuff. 
• 2020-07-29: "How many days until ...?" A date calculator for today's #haskell problem. When I say: "Compute the date," I'm not talking fig trees, here. The solution to today's #Haskell problem. 
  
• 2020-07-28: Today's #haskell problem involves passing arguments to and verifying results from an external application. 'frankenfurters.' That's what we're trying to sum here. 'frankenfurters.' 'Fault Tolerance'? We've got that with today's #haskell solution. 
• 2020-07-27: Today's #Haskell exercise makes us realize that ... "All, in all, you're just a ... nother brick in THE WALL. :/" A solution pour vous, s'il vous plaît. 
  
• 2020-07-24: Today's #haskell problem explores the result of processed images from, in this case, Amazon's Rekognition. Today's #haskell solution: BIRDz! ... Cardinals, in fact. 
  
• 2020-07-23: For today's #haskell problem, let's read in a JPG (o' FLAH'z!) and write it out as a TIFF ... for, you know, like: an image processing/classification exercise, at some later date. Ooh! TIFFY! TIFF saved from loaded JPEG image. 
  
• 2020-07-22: For today's #haskell problem we extract data from JSON returned from a REST endpoint. The #haskell solution is declarative/functional-composition goodness to parse data from JSON returned from a REST endpoint. 
• 2020-07-21: We ping a public API REST endpoint for today's #Haskell problem. For today's #haskell solution, simpleHttp in Network.HTTP.Conduit does the trick! 
• 2020-07-20: For today's #haskell problem we read a file that contains a JSON message and parse it. 
• 2020-07-17: Oops! Where has the time gone? That's today's ... I mean, YESTERDAY's, #haskell problem.
  
   
• 2020-07-16: And now, for something completely different: today's #haskell problem has us reading a file, parsing the data, and ranking the results. #haskell solution to which level is most recruit-efficient for a dark chest. 
• 2020-07-15: For today's #haskell problem, we pull what we've done so far all together and compute today's pairings, given historical context.  
• 2020-07-14: For today's #haskell problem, we pull what we've done so far all together and compute today's pairings, given historical context. 
• 2020-07-14: For today's #Haskell problem, we look at using our historical context of pairings to answer questions for future pairings. 
• 2020-07-13: Now that we've selected pairings for today, let's store those pairings into an historical context for today's #haskell problem. 
• 2020-07-08: Pairing and ... 'Mobbing' (?) ... okay, really??? is our game for today's #haskell problem. A solution to the simple pairing-problem.
• 2020-07-07: For today's #haskell problem, we lay a foundation for building a team-pairing app. This day's problem addresses a History-type to provide context to the pairing-algorithm. 
• 2020-07-06: For today's #haskell problem, we look at finding the spanning trees of a graph. 
  
• 2020-07-02: Today's #haskell exercise finds us (acyclic) pathing though a simpler, yet-not-fully connected, graph. 
  
• 2020-07-01: For today's #haskell problem we find cycles in graphs, ... MOTORcycles in graphs! AHA! AND MAKE MINE A DUCATI! ON FYE-YARRRR! 🔥 ... no ... wait ... Oh, well. #GraphTheory