Overcomplicating Recursion

As I study recursion and begin applying it in my homework, I notice some similarities, or at least tenuous connections between recursion steps and troubleshooting.

IT support should work on the basis of elimination of a class of issues at a time, until you drill down to the root issue.  I recommend reading DevOps Troubleshooting by Kyle Rankin for more on this subject.

Recursion looks to eliminate a choice, usually between two options, until it returns your root cause, or base case.  

I can't comprehend this List

More accurate, would be to say I don't like listening comprehension at the moment.  I'd rather write more verbose code than use it. Which means I need to push myself to use it more and get better with it.  

Right now the issue lays in knowing how to connect certain variables and their respective positions.  I'm sure my upcoming assignments will have need of it and that's frightening.  Oh well, til tomorrow. 

Never Unpickle Unknown Data

Title is from a recent lecture.  But a good piece of advice when learning anything programming/technology.  Implicit trust of objects and code is an even scarier proposition with all the garbage auto-complete code that is out there right now.  

Let's go to Rio

Came across a saved medium article that talked about a framework called Rio.  It's all python, giving the ability to write full web apps in python.  Unlike Flask, no HTML/CSS or JavaScript needed.  I'm thinking of trying it out to develop more python skills without needing to detour for the html/css stuff.  

Ideation Abounds

Found an interesting book I had saved.  140 simple python programs.  Gave me an idea for my portfolio site. Might make it a randomizer button that loads one of the simple programs side by side within the code.