Just started on the #sketchnotes for 's upcoming course 'Web Security Essentials'
About to learn how to protect cookies from phishermen, and ward off flying swarms of cursor arrows. π£πͺπͺπͺπ£
Conversation
Also tiny tip for starting a #sketchnote - I like laying down a loose set of layout guides to build the structure inside.
These are fairly abstract but I try to create a balanced set of big and small areas.
Helps align things into distinct sections.
2
36
Working more on the web security sketchnotes.
The blue underlay is my lazy rough version - mostly to plan the composition and make sure itβs all going to fit.
Then I do final lines and neater lettering over the top
These are still in progress - now learning about CSRF and XSS π
2
6
34
for me the sketchnote is the blue one, wip, the place to learn and reflect and the finished one is an illustration. Both valuable
ping
2
2
1
Completely agree β I call my finished ones "illustrated notes," or "illustrated explanations."
But sometimes revert to the term "sketchnotes" since it's such a common concept in the dev community. And find people get confused by the term "illustrated notes" without seeing them.
Agreed, if you relate to Tiago's view of taking notes and the paper he shared earlier and see sketchnotes as a special kind of notes it makes sense to favor a wip form. Convo I had earlier with hence mention
.. next question 1/2
1
2
2/2 If we learn, we capture using sketches. How to support subsequent reflection, summarisation, deeper understanding on the same media (or not). It's an open question
cf link to paper for twitter.com/fortelabs/stat
Describes a process mostly for textual notes
Quote Tweet
New free post on the Praxis blog:
How To Take Smart Notes: 10 Principles to Revolutionize Your Note-Taking and Writing
praxis.fortelabs.co/how-to-take-sm
My summary of the most important ideas from the best book on note-taking I've read, How To Take Smart Notes by @soenke_ahrens
1
2
Show replies



