I found TensorFlow initially confusing but then quite comfortable. It’s odd how after programming in a language like Python for a while, it becomes confusing that you have to declare “placeholders” (variables) and constants up-front, then initialize them.
The American Red Cross is running computers with an obsolete and unsupported operating system, and using them to collect HIPAA protected personal health and other information! If a Russian or North Korean hacker can break your system because you’re using 16 year-old software that hasn’t been supported for two years, then you as an organization have failed.
I left last week’s PyData Meetup with more questions than answers. Questions like “why does that neural net I just wrote perform the way it does?” So, with a couple of weeks left until the next project is due, I decided to go back and revisit the second half of the neural networks topic before moving forward.
Tonight I joined the first Southern California PyData meetup. It featured two speakers discussing how to better understand the predictions made by machine-learning models, and why it might be important to do so. I was impressed by the capabilities of the packages demonstrated and the likely importance of having such capabilities as we move forward with deep learning-based automation that could cause catastrophic results if it fails in unexpected ways.
There is little here that I could not learn on my own. But I find that it’s useful to learn along with others, and the structure that programs like this provide can be useful, so long as it isn’t too expensive. For myself, the structure and ability to discuss issues and problems with others were the key things that made this summer’s effort worth the $600.
The basic idea is to set some goals, share them with anybody who is watching the #SoDS17 tag on twitter, then provide updates by twitter, with more detail in another location. I’ll be using this blog for that purpose