Join 📚 Kevin's Highlights
A batch of the best highlights from what Kevin's read, .
Here's something I've learned
over the past five years of blogging:
don't start by telling the audience
why you wrote a blog post.
Instead,
tell them why they should read it, and
then do your best to prove yourself right.
Technical Writing for Developers – Why You Should Have a Blog and How to Start One
Ankur Tyagi
As shocking as that might initially seem, we should not to be totally surprised.
Seven years of AI has taught us that deep learning is unpredictable, and not always human like.
“Adversarial attacks” like these have shown remarkable weakness, time and again, repeatedly establishing that what deep learning systems do just isn’t the same as what people do:
[](https://substackcdn.com/image/fetch/f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F8f1f1fed-7908-4cc0-a29b-d88005ebaa10_2000x794.png)
David Beats Go-Liath
Gary Marcus
A knowledge graph is made up of three main components:
nodes, edges, and labels.
Any *object*, *place*, or *person* can be a **node**.
An **edge** defines the *relationship* between the nodes.
For example,
a node could be a client, like IBM, and an agency like, Ogilvy.
An edge would be categorize the relationship as a customer relationship between IBM and Ogilvy.
A represents the subject, B represents the predicate, C represents the object
What is a knowledge graph?
ibm.com
...catch up on these, and many more highlights
Readwise