What I’m thinking about today:
- I’d like to write a book about asking questions. I could interview a variety of professionals…maybe a journalist, therapist, data scientist, professor of some type, lawyer….ultimately the book would provide some type of framework for approaching and thinking about information.
- How to identify and account for bias in data. Create a site for publishing case studies?
- I should make it to the halfway point in my Udemy Java course on tomorrow (210 of 425 lectures & challenges completed).
- Do I want to tweet the different information sources that I run across in a day?
What I learned today:
Storytelling with data podcast– Alberto Cairo’s How Charts Lie:
– We form an opinion for emotional reasons, then gather data to affirm this (which is backwards).
– We are drawn to graphs that show something we already believe, and we’re less critical of these graphs.
– Books referenced that I’d like to look into: For argument’s sake, and Factfulness
– Cairo mentioned that there is a lot of research done on how charts are perceived, so I did a quick search and found The Encyclopedia of Human-Computer Interaction which has a chapter on Data Visualization for Human Perception
– Curse of Knowledge is a cognitive bias that occurs when an individual unknowingly assumes that the others have enough background to understand.
LinkedIn Learning – Learning Security Frameworks: Risk assessment tools are available from SIG (requires membership), CIS and NIST. The CIS site provides Cybersecurity best practices, benchmarks, and tools to help companies guard against cybersecurity threats.
Today in programming:
hashCode() is a method of the Object class which is present in all objects due to the inheritance of Object. hashCode() returns an integer that represents the internal memory of that object. https://en.wikipedia.org/wiki/Hash_functionhttps://stackabuse.com/javas-object-methods-hashcode/https://eclipsesource.com/blogs/2012/09/04/the-3-things-you-should-know-about-hashcode/
Reminder – why use an abstract class? These can be subclassed but cannot be instantiated. They should be used when…
- you want to share code among closely related classes
- Subclasses may hav e many common methods or fields, or require access modifiers other than public
- You want to declare non-static or non-final fields. (*I don’t understand this)
Use interfaces when…
- You expect unrelated classes would implement your interface…for example Comparable and Cloneable
- You want to specify behavior, but aren’t concerned about who implants that behavior
- You want to take advantage of multiple inheritance of type