advice candidate goes to: this-edition E explorer
Learning to hack is still how you learn how things work: draw the line where the attacker is
Name the threat agent, the vector and how sophisticated it is; a ladder from your own mistakes up to states; the bookmarklet trick; to hack means to solve problems.
Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).
Where it comes from
- Who are you protecting against? Draw the security line where the attacker is, not above it the ladder (newsroom)
- Fix the page yourself the bookmarklet (newsroom)
- Hacking Portugal, 2016 to hack means to solve problems (newsroom)
What it answers in the 2018 book
- Learn to Hack answered outline, Life Patterns
- Security creates better developers answered outline, Security
- Threat Modeling answered outline, Security
Where it goes
Chapter Controlling your agent: RiskMandate, part Build it without a server (drafting); topic Security for the agent era: least code, supply chain, secrets, learning to hack.
Other ideas proposed for the same chapter: Mandate, reach and the gap: hope versus enforcement, Code is a liability; the future is the smallest code that does the job, The secret goes from the drop into the tool, never into the chat, Security experience is what lets you ship with known gaps: list them, match them to the reader, say what would change the call.
Node idea:learn-to-hack in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.