What did you do this past week?
My team finished phase one of the IDB project. After looking over some tutorials of apiary.io, it was actually fairly easy and straightforward to use. To match the information on our UML models, the NBA API we originally decided to use was insufficient, so we decided to use an additional API to grab venue information from Wikipedia. Luckily for us, there’s really only one call for that, and then it’s a matter of parsing the data that comes back.
What’s in your way?
I feel like I could have done a more thorough job documenting the API for my team. Phase two of the IDB project is going to be published soon, and I can only imagine it being more complicated than the first phase.
What will you do next week?
Since apiary is only used to document our APIs, I supposed we’re going to have to use another tool to implement them. I think now we have to consider the parsing of the data we get using our APIs and how to store it in a database.
What’s my experience of the class?
In class, we discussed a type checker for Python, mypy. It makes Python functions and methods looks like they were written in another language! It definitely helps with readability, and is good practice to label your inputs and outputs anyways.
What’s my pick-of-the-week or tip-of-the-week?
If you have ever wanted to learn the Swift programming language, you can do it through on your phone! Swifty is an iPhone/iPad app where you can practice the language (from basic syntax to writing classes and closures) in short bursts, whenever you have a bit of free time.