I went to BSides Portland. Learned new things. Gained new insights. Lots to think about. While I am thinking instead of writing, enjoy My Mom’s favorite fox puppet.
Read an article about Dark Web written by Doug Schadel and Neil Wertheimer, published in AARP Bulletin September 2018, pages 10 to 18.
I have been paying attention to what is written and said about Cybersecurity and Infosec. I learned best practices from years of doing research work that included keeping integrity, privacy, safety and security of data. I went to DEFCON this year. I enjoyed reading this article. The article clearly explains what things are and how they work. Like TOR, who developed it and that it stands for Onion Router. The authors do a good job of explaining what of your information is being bought and sold ,something called fullz profiles. The article concludes with the advice of freezing your credit, closely monitor all accounts and using a password manager. Follow this good advice.
Origami Design Secrets, Mathematical Methods for an Ancient Art by Robert Lang 2003
Roses, Origami & Math by Toshikazu Kawasaki 1998
The Art and Wonder of Origami by Kunuhiko Kasahara 2004
Unit Origami, multidimensional transformation by Tomoko Fuse 1990
I taught origami and math as a Talented and Gifted Students class.
I folded these units at Computation and Cupcakes hosted by Women Who Code.This fall I will teach this class to Women Who Code.
Recently I gave star unit origami to someone who said I could never make something so complicated. I can show you how to make something complicated.
Fold a single square piece of paper into the unit.
Take folded units six to make a cube, 12 to make a star.
Each unit has to be exactly the same. Consistent units are just as important as consistent labels on data.
Math concepts covered will include symmetry, transformations, group theory, number theory, fractions and geometric solids. While folding paper think about complex concepts that are important in big data, tensorflow, neural networks, machine learning and cryptography.
I write cooking recipes for publication. Documentation is a lot like writing recipes. Recipes are for all types of cooks, beginners and experts. Most of the documentation I find is sparse, lacking details, written for the person who wrote the code. It is hard to write directions for people who don’t know how to use or do the coding. I have been trying to expand the documentation for some Docker containers and I can’t find a new user that can tell me what is missing. I hear everything is find from experts.
Suggestions for requirements for documentation from recipes submission requirements.
Title, something instead of documentation.
Tell us about your recipe. Needs to be a little more than it is a Docker container.
Ingredients. Let people know what is needed. Software, libraries, how much memory needed. Give people an idea if they even can do the task with what system they have. Do not send people to the grocery store for a missing ingredient or to borrow a cup of sugar from a neighbor. This is really important for when people come to a half day workshop only to find out they can’t participate.
Prep method, for recipes what is needed is stove top, oven, grill, blender. What are we doing? Baking? Spinning up a web server, database. Be clearer are we frying or blending?
After clearly stating what we are doing, write out the directions. Include prep and cook time. For example it takes three hours to code this. Build time is half a day. Recipes state what occasion Holiday they are for. Also what category. Github tags make this easy, use them. Course Breakfast, lunch, Dinner. Quantity served. From these ideas Think the documentation thru to more useful documentation. Stack Overflow should not be your only documentation.
On git hub hackoregon/data-science-pet-containers are very useful Docker containers. Tools included are PostgreSQL, PostGIS, Anaconda and Rstudio. Add data and you are all set for exploring and developing. If you have any problems file an issue on git-hub. I am looking for what is missing from the directions.
Written by Sara Wachter-Boettcher, Technically Wrong is the best popular press book written about miss-classification and algorithms.
The chapters in the book cover common issues and problems that should not be happening.
From Chapter 10, Technically Dangerous
Software is designed and coded by people not representing the general population …” The narrower those people’s perspective’s are, the more they design and code like themselves and shrug off any responsibility for outcome, the more inequality, insensitivity and hate can thrive ”
People die from classification errors.
Small choices matter.
Infer an R package for tidyverse friendly statistical inference is now on CRAN. Happy to see this package made onto CRAN. It is a different way to look at inference. Great addition to the tool box.
What if you have a lot of old data files in SPSS form and you do not have SPSS software. You are in luck if you have Rstudio. Current versions of Rstudio load SPSS data files without needing a special library for the task. There are libraries for this task.
To load SPSS data:
Open RStudio, on menu bar choose File, scroll to Import Data set, choose from SPSS.
A window opens to load the data.
Enter file name or url into file/url box.
Preview data in preview window. If it looks okay push the import button. And the data is loaded into Rstudio ready for use.
This is a very useful feature of RStudio.
Written by Ryan J. Winter, A Crash Course in Statistics published by Sage Publications, 2018 is an easy to read, short, concise book. It is just the right book when you want a quick overview of what you have forgotten about Statistics. The code in the book is SPSS available at the book’s web-site at study.sagepub.com/winter .
Covers descriptive Statistics, Chi-Square, t-Test, and ANOVA.
The book can be used as a text-book as it has quizzes at the end of each chapter.
If you do not have SPSS Rstudio will load the SPSS data files ready to use.
It is February again. I have lots of back log to complete. Book reviews and interesting topics.