Monday, January 4, 2016

December 2015 1HaskellADay Problems and Solutions

December 2015

  • December 30th, 2015: For today's #haskell problem we convert valid airport IATA codes to ints and back And a Happy New Year solution: Safe travels should you be Haskelling by air!
  • December 28th, 2015: So, remember ADVENT? What happens when your INV becomes full? Today's #haskell problem looks at that
  • December 23rd, 2015: Warm and fuzzy December, so we have a warm and fuzzy #haskell problem for today
  • December 21st, 2015: For today's #haskell problem we are to deduce stock splits using LOGIC and SCIENCE
  • December 18th, 2015: Today's #haskell problem... 'may' be thematic with that 'Star ...' what was the name of that movie? Gosh! Star ... something! eh, whatevs: just let the Wookie win (always the best policy) 
  • December 17th, 2015: For today's #haskell problem we look at reporting out periodically on an investment and, BONUS! charting it! And we've charted our AAPL investment growth, too! 
  • December 16th, 2015: For (coming onto) today's #haskell problem we demask the masked data to unmaskify it, yo! And then the solution unmasked that masked data! (that's convenient.)
  • December 15th, 2015: So yesterday we masked some rows, but what happened to the masking dictionary? Today's #haskell problem we save it Ah! So that's where that cipher went!
  • December 14th, 2015: We look at a way of masking data for today's #haskell problem And the solution gives us some lovely masked rows
  • December 11th, 2015: Today's #haskell problem asks: WHAT DOES THE TRANSFORMED JSON SAY! (okay, that was weaksauce)
  • December 10th, 2015: For today's #Haskell problem we try to find relevancy in our daily lives ...well, in #JSON, which is the same thing.
  • December 9th, 2015: Today's #haskell problem asks you to read in some rows of #JSON We'll be looking into this data set through the week "Watcha readin'?" "JSON." "Cool! ... No, ... wait."
  • December 8th, 2015: My main man, magic Mike (m^5 to his friends) said: "You're doing it wrong."Do it right for today's #haskell problem A first stab at the solution, not taking into account splits, is posted at And the split-adjusted solution here: ~3700%-gain. It's time for me to sing the "You're the Top"-song to @MacNN_Mike
  • December 7th, 2015: In today's #haskell problem we cry «On y va!» and have at it! En garde, you pesky investment problem, you! The solution shows Dr. Evil does NOT get ONE MILLION DOLLARS! Nor piranhas with laser beams on their heads, either.
  • December 4th, 2015: We write a web-proxy to help out poor, little Ajax go cross domain for today's #haskell problem
  • December 3rd, 2015: We meet the Ip-man for today's #haskell problem. Hiya! Today's solution shares a little-known fact AND ALSO uses <$> as well! Is there a weekly limit on these thingies?
  • December 2nd, 2015: Synthetic data generation for today's #haskell problem NOT ONLY did we write a Synthetic data generator in a day but we learned all 50 states AND used <$> and <*> – BONUS!
  • December 1st, 2015: In today's #haskell problem, we see @geophf lose his cool. No... wait... That's not news now, is it. (RID analysis). Unwordin' down-low on the arrr-eye-dee, LIKE A GANGSTA!

No comments: