Knot 3: Encryption, Race and Tunnels

More focus this week on finishing a big project, so less time for books or outside reading, but nevertheless some articles to recommend.

Articles

• Ursula Lindsey - “Funds Cut for Prominent Arabic Language Program” (Al-Fanar Media)

An extremely short-sighted decision. The CASA programme has been a really important source of support over its forty-nine years. This is a decision that affects American students of Arabic, but we shouldn’t forget that it’s symptomatic of how language studies are treated elsewhere.

• Rosalind Adams - “Intake: Locked On The Psych Ward” (Buzzfeed)

Anyone who still says Buzzfeed doesn’t do important reporting just isn’t reading. This piece looks at the way a for-profit system works to the disadvantage of patients’ welfare and the healthcare system in general. A must-read for an American audience, and for Europeans / Brits as a portent of what probably is headed our way.

• Bron Gondwana - “Why we don't offer PGP” (Fastmail Blog)

PGP has been much discussed (more than usual, at any rate) this past week. This post offers a useful overview of some of the things that PGP can help protect against, versus some of the places where trust in what it can do are misplaced. Pair this article with Bjarni Rúnar’s “Too Cool for PGP” to cover your bases.

• Annalee Newitz - “Evernote apologizes for its new privacy policy” (Ars Technica)

A useful corrective from Ars Technica (one of the best places to go for informed reporting on science and technology) about Evernote’s recent policy changes relating to privacy. The important point to take away from all this is that Evernote probably isn’t where you want to be storing your notes if you care about your privacy. Try DevonThink instead for a far saner approach to encryption and storage.

• Amal el-Mohtar - “'Iraq + 100' Is Painful, But Don't Look Away” (NPR)

This review of a new collection of stories seems (from the review, at any rate) like it is worth reading. Imaginative and creative responses to events on this scale are, I think, the kinds of things that will ultimately survive far longer than the political analysis and commentary that so far has dominated the discussion of what happened in Iraq. I look forward to reading this book.

• Ryan Holliday - “Want to Really Make America Great Again? Stop Reading the News.” (Observer)

You can ignore the focus on US politics and still take away the broader argument, that following the day-to-day news cycle is (for the broad majority of us) unnecessary and probably actually detrimental to our health and ability to do work that really matters (to us or others). A useful reminder.

• Laura Reiley - “Farm to Table: At Tampa Bay farm-to-table restaurants, you’re being fed fiction” (Tampa Bay Times)

A great piece of investigative work, Reiley shows how a lot of the promises of the farm-to-table movement in California are false claims. This piece is the first in a series that is worth reading in its entirety.

• Roger Cohen - “Broken Men in Paradise” (New York Times)

This is an important reminder of the realities of life for those refugees refused entry to Australia following harrowing journeys across the seas. Authorities in the places they are sent to operate with seemingly little restraint or care for their wellbeing.

• Ta-Nehisi Coates — “My President Was Black: A history of the first African American White House—and of what came next” (The Atlantic)

This piece seems to capture a moment. Based on several interviews with Obama as well as his usual command of the context that explains this moment, this is a (long) must-read.

• Gideon Lewis-Kraus - “The Great A.I. Awakening” (New York Times)

Important from perhaps a different angle, this is a long overview of the ways so-called artificial intelligence is poised to change our world. It views the transformation through the lens of developments in Google’s online translation service. It offers context and explanation to two different approaches to machine intelligence and the different algorithmic decisions being made. If you’re interested in technology and the ways that computers will continue to be embedded in our daily lives, you won’t want to miss this one.

Books

This week I read Lynne Kelly’s “The Memory Code: The Secrets of Stonehenge, Easter Island and Other Ancient Monuments” in preparation for an upcoming podcast episode interview. Dr Kelly makes a convincing case for how old archeological sites (like Stonehenge) were probably used as forms of memory aids to recall information important for local communities. The book is best accompanied by a glance at a truly fascinating series of memory experiments that she’s been working on. I also read Rebecca Solnit’s “Men Explain Things to Me”, a very useful and sobering reminder of the ways that society works against women, whether directly through violence or other perhaps less visible means.

Films / TV

I wrote yesterday about “Into Eternity” (trailer here), one of my favourite documentaries of the past year. It’s filmed with an idiosyncratic approach to detail and atmosphere. I am ignorant about where Finnish director Michael Madsen gets his influences from, but I certainly look forward to seeing more. Just today I saw another documentary, “13th”, which focuses on the ways that racial inequality has manifested itself in the United States, specifically in the prison system. This is a powerful statement, particularly for American viewers, I imagine, and it made me think about the ways that similar trends are to be found back in Europe.

The Two Books Every Intermediate Arabic Student Needs to Read

In the beginning, the study of Arabic is about coming to terms with how the language works. You start to grapple with the diglossia, with the verb system (roots everywhere!) and start working your way through one of the big textbooks that most programmes prescribe.

After a few months, you want to start communicating with people, but every attempt is met with some kind of difficulty or failure. Either you’re not speaking the right dialect, or you’re not attempting to speak using dialect at all. You study a bit more, and you’re finally able to communicate with your Lebanese or Tunisian friend, but the moment you come across someone speaking a different dialect variant you’re back at square one.

What’s the solution to this problem? Do students of Arabic have to learn every dialect? Thankfully, no, though you’ll want to get a basic familiarity in some of the main broad patterns that different dialect groups employ.

This is where the good people at Lingualism come in, and their two-volume Arabic Voices series. (Get Volume 1 and Volume 2 from Amazon here, or order direct from Lingualism).

These two books contain 57 monologues covering the whole Arab world and North Africa. You can learn about Qat from a Yemeni, identity from a Lebanese man, or what it’s like to date as a young Tunisian woman. To get a taste for the content of the material, everything is available for free on Lingualism’s YouTube channel. Here’s Wasem, for example, talking about the life of Arabs living in Israel:

The great thing about this book is that every monologue comes with a wide variety of exercises and supporting materials to help you get the most out of the language used.

You start off with some basic comprehension questions alongside some of the key vocabulary, then you dive into some of the specifics that are unique to that particular dialect. Here’s one of the exercises where you’re supposed to draw lines connecting the English to the Egyptian and to the Fusha / ‘Modern Standard’ translations.

View fullsize

I’m not super keen on textbooks that deal too much in translations, but if you know how to use them, this is a real goldmine. I’ll usually put one or two of what seem like key phrases or expressions into Anki to memorise. The exercises are followed by a full transcript in Arabic and English translation. Here’s one example:

View fullsize

Some of the monologues also include grammar notes at the end if something particularly interesting is worth noting. Here’s an example of that ‘focus’ material.

View fullsize

Once you’ve gone through all the exercises, listened to the video to figure out what the various new phrases might mean, you can start covering up the Arabic part of the transcript to see if you can reproduce parts of what was said on the basis of the English translation. This is hard work, but incredibly rewarding.

If you want to get a full overview for how the language that Arabs speak day-to-day, these two books are the resource for you. What’s more, the monologues are short enough that you can probably blaze through the content of both books in two to four months. I don’t know of any other one-stop-shop where you can gain familiarity with the linguistic variety of the Arab-speaking world, plus learn a thing or two about people’s lives and culture(s).

[Over the coming weeks I’ll be writing more about the different resources available to intermediate-level Arabic students. I’ve just finished writing an eBook and electronic resource for people at that stage in their learning. For more information and discount offers, sign up to the mailing list here. To enquire about one-on-one language coaching sessions, click here.]

Highlights + DevonThink = Pretty Great

I’m late to the Highlights party, but I’m glad I got here.

Like many readers of this blog, I get sent (and occasionally read) a lot of PDFs. In fact, I did a quick search in DevonThink, and I am informed that I have 52,244 PDFs in my library. These are a mix of reports, archived copies of websites, scanned-and-OCRed photos and a thousand-and-one things in between.

Thus far, my workflow has been to read PDFs on my Mac. Any notes I took while reading the file were written up manually in separate files. I would laboriously copy and paste whatever text snippet or quotation I wanted to preserve along with its page reference. These would be fed into DevonThink’s AI engine and magic would happen.

Now, post-Highlights-installation, my workflow is much less laborious. I can take highlights in-app, export all the quotations as separate text or HTML files and have have DevonThink go do its thing without all the intermediary hassle. If you’re  a professional researcher or writer using DevonThink as your notes database — and quite frankly, if not, why not? — the Highlights app will probably please you.

Knot 1: Solitary Confinement & Digital Security

This is the first of what I hope will be a regular feature on this blog. Knot will link to recent things that I’ve been reading. It will include short articles as well as books and other things on the internet.

Articles

• Martin Garbus — “America’s Invisible Inferno” (NYRB)

This NYRB review of ‘Hell Is A Very Small Place’ covers the use of solitary confinement in the American prison system. It ends with unearned optimism, but nevertheless is a useful reminder of the importance of the issue.

• Mary Catherine O’Connor — “The latest weapon in the fight against illegal fishing? Artificial intelligence” (The Guardian)

Interesting short piece on the use of machine learning combined with data science competition site, Kaggle, to try to improve the efficiency and accuracy of fishing inspections. Hardly a day passes when a new initiative like this is launched, merging data science and crowdsourced solutions. I look forward to being able to contribute (one day in the hopefully-not-so-distant future).

• Meeri Kim — “How a researcher used big data to beat her own ovarian cancer” (Washington Post)

More data science, though this is more at the N=1 edge of things than the previous fishery data story. The more data we are able to access and generate, the more there will be need for ways of analysing and processing these complex interactions. A lot of money is being invested in finding ways to automate this for non-technical users, though I imagine we’re still a little way away from that utopia.

• Check Point — “More Than 1 Million Google Accounts Breached by Gooligan” (CheckPoint Blog)

I’m not quite sure why this isn’t a bigger story. I’ve long believed that anything stored by Google (in particular, emails) will at some point be leaked in a hack or by some disgruntled employee. This latest hack is pretty close to that scenario, with the caveat that we don’t know what was taken. Takeaway: move away from the Google ecosystem where possible.

• Scott Gilbertson — “HTTPS is not a magic bullet for Web security” (Ars Technica)

This is a few months old but offers a useful overview on HTTPS technology, what it can help with (and what it is less useful for). The headline is actually a bit deceptive since the article seems to make a strong case for the use of HTTPS.

• Shane Parrish — "The Simple Plan To Read More” (Farnham Street / Personal Growth)

I’ve long ago taken this advice on board, but it’s a useful reminder. I enjoy reading, and I enjoy the diversity that comes from reading widely and broadly, so keeping up the pace and seeing it more as a habit to be done most days is, to my mind, the right way of looking at it.

Books

I read three books this past week. Jim Klopman’s Balance Is Power was my easy introduction to some of the science behind why it is useful to train balance in a focused way as a skill.

I finished the second volume in Elena Ferrante’s tetralogy, The Story of a New Name, though I didn’t enjoy it quite as much as the first. I suspect I’ll have to return to it in a few weeks after the dust has settled.

Finally, I devoured Paul Kalanathi’s When Breath Becomes Air, a beautifully written exploration of death, medicine, how we go through all these things as people, how illness affects not only the body but the mind and the spirit as well. It reminded me of Atul Gawande’s Being Mortal, which covered similar themes albeit with less of an intimately tragic outcome. I highly recommend giving When Breath Becomes Air a read.

The Inner Game: How a Perspective Shift Can Radically Improve Your Performance

I’ve recently become interested in mental models, or different types of lenses you can bring to view a particular situation or reality. We all have an immense flexibility in how we can view the world; sometimes changing our approach in this way can change how we experience our reality.

I found the process of realising and accepting this reality — that how we choose to respond to things changes how we experience them — incredibly empowering and liberating. It gives you options and choices in situations that may have seemed oppressive or challenging in the past. It opens you up to new approaches, new possibilities. I’ve written about my struggles with various parts of climbing, but one of the places I often return to is this idea that I can choose how I respond to that difficult. Similarly, I can reframe how I decide to view that reality: I can see it through the lens of fear, or I can view it through the lens of opportunity and growth. I can see it through my default hesitant-cum-reluctant perspective or I can try to imagine how someone else sees it (a friend, perhaps, who doesn’t struggle with the same mental blocks, or even someone much further along in the sport).

I recently read a fantastic book that introduces some of these ideas as they relate to the sport of tennis. The book, The Inner Game of Tennis: The Classic Guide to the Mental Side of Peak Performance, was written by W. Timothy Gallwey and was originally published in 1972. Back then, it made quite a splash (selling over a million copies to date) and the book is rightly well-read as a classic of sports psychology literature. Gallwey has since published a number of spin-off books applying his principles to other domains (work, stress, music, golf, skiing) but you needn’t be a tennis player at all to get a lot from the original version.

The core idea that Gallwey introduces is that the mind has “two selves”, Self 1 and Self 2. I’m not entirely sure about the full extent to which these overlap with Kahneman’s System 1 and System 2, but there is some common ground.

Self 1 (also known as the ‘teller’) is the voice in your head which tries to actively manage how you do certain things. It is responsible for efforts to ‘try hard’, and is often quite critical. Self 2, in contrast, is the ‘doer’, the part of you that (in the end) ends up doing things but that is sensitive to the attitude and comments made by Self 1. The book is about the relationship between these two voices, since Self 1 doesn’t trust Self 2 to be able to deliver. Gallwey argues that in order to be effective and do our best work (or play our best match of tennis), we need a better way of translating our knowledge into effective action, and thus a better way for the two selves to communicate and interact.

Some of the details of the book are specific to movement-based skills. I think that anyone doing any kind of sport would benefit from reading this book. Gallwey outlines four key skills that go into effective movement: - letting go of judgement — once you stop allowing self 1 to dictate the terms of the conversation, you can rely much more on the instinctual learning capacity of self 2. This also hooks into the idea of ’seeing clearly’, which pretty much immediately improves your ability to respond and react to the reality of the present moment. - creating images — visualising movement, really noticing what’s going on (when viewing others do it) and working from imitation and from feeling your way into the movements. - ‘letting it happen’ — getting out of the way. This has a lot to do with the first skill. You have to trust Self 2’s ability to deliver, and you just need to let it happen, or let whatever happens happen. The important thing here is the nonjudgemental observation of change and the results. - concentration — this is the final stage, since just ‘letting go’ is not quite enough. The relaxed, nonjudgemental mind needs focusing. For movement, this means focusing your observation and sensitivity to sensations in the body (for example) or an increased consciousness of the senses. (“Focus intensifies the light of consciousness”).

He ends the book by addressing the idea of games — games that people play, the meaning of competition, and the broader implications of the way we approach this ‘inner game’ (balancing self 1 and self 2) in our life. (I was really impressed how so many of the ideas presented presage current trends and predilections: the importance of mindfulness, the value of play, and so on).

If the first part of the book was less applicable to things outside the domain of movement skills and practical learning, the second half is much more relevant to the problems I think most of us face. There’s a certain amount of pop psychology that probably hasn’t lasted the test of time, but mostly it is really solid perspectives on: - finding games where the score doesn’t matter - the debate in Western society as to the value of competition as compared with cooperation. - issues that result when ‘success’ is equated to value and self-worth (which can in turn lead to various compulsions to succeed, or, paradoxically, to rebel)

Gallwey ends the book with the paradox that is at the core of the ‘inner game’, that in order to allow Self 2 the freedom to learn and act naturally, this requires a level of abandonment. So it is a matter of “caring, yet not caring […] effort, but effortless.” He ties it in to all sorts of other areas outside tennis that really convinced me as to the applicability beyond purely motor / movement skills.

There was a lot to unpack about this book, and I may return to some of the specific points in the future. For anyone working on their movement skills or finding ways to enjoy that part of their life, I’d put this on the list of essential books. For anyone else, maybe give the first few chapters a read; I think you’ll be surprised what Gallwey brings to the table.

Fundamentals Versus Hacks

I was talking to someone a couple of days ago who pushed back a little against some of my recent posts. In particular, she was resistant to the idea that there were special techniques or skills that could be learnt that might help with writing, studying and learning.

I obviously disagree with the premise that we can’t get better at the things we do in a domain like learning, but it encouraged me to define the core principles as something separate from the less important lessons.

I’m writing something on the specific question of software — i.e. do we really need to buy all this expensive software to be able to do great work — so I’ll set that part of the problem to one side for now. For the rest, I think it’s useful to make a distinction between fundamentals and ‘hacks’.

The idea of a hack or ‘lifehack’ has garnered a decent amount of criticism over the years, often for good reason. Whole sites exist to tell you small things you can change — little tweaks to the way you’re already doing things — that will supposedly free you up to do the important work. My experience is that these are mostly cosmetic changes, and that they don’t deliver 10x (or more) improvements. The only time when you should be looking for tweaks of that kind is if you’re already in the 99.9% bracket for what you do.

For whatever reason, people seem to prefer the idea of hacks to fundamentals. Perhaps because fundamentals are harder to change, more ossified and because to change a fundamental belief or practice is to question who you are on some level.

A preference for hacks is why people think that drinking some new type of tea or a particular kind of food is better for their ability to make decisions in the long run than simply making sure to get enough sleep.

I have read a lot in and around the productivity / health domain, and there’s a strong tendency towards these small ‘hack’-like tweaks. But what are the fundamentals? I think often a lot of that comes down to things we already know:

• get more sleep
• eat more vegetables
• move your body more
• prioritise the long-term over the short-term
• Find a way to do the ‘hard thing’ earlier in your day

Some other principles that I’ve found useful:

• Subtract first, then add — if you can find a way to simplify your current process (or whatever it is) by taking something away, I’ve found that that really helps. This can apply to big things (like the conflict in Afghanistan and the international involvement there — see this for more) as well as smaller things (your daily work schedule).
• Perfect the process; think less about results — I’ve noticed this most profoundly in my exercise and movement work over the past few years. Whenever I’ve focused too much on the hoped-for results of a particular routine or programme, I’ve had things go wrong (either injuries or setbacks of other kinds). When I stay focused on the process, trying to make each movement as good as I can, trying to stay mindful of where I am on a particular day vs where I want to be, then I find this really beneficial.

The fundamentals are low-hanging fruit that offer big returns, albeit in a slightly less sexy packaging. Hacks are shortcuts that offer minute incremental improvements, at the expense of your time and energy.

There is a time and place for tweaks and fine-tuning and smaller productivity wins, but unless you’re finding a way to sort out your fundamentals, you’re missing a great opportunity.

Skills Development: Foundations

I watched this video a few months ago, but thought it worth returning to since it covers a lot of really useful ground for anyone who has to learn new skills / develop etc. Which is to say, it's relevant to everyone on planet Earth.

Or just read these notes to get an overview of some useful things she talks about. (If you want to read a transcript, go here.)

“Allison Kaptur: Effective Learning for Programmers” — Notes from YouTube

We learn early on that Kaptur’s job at the Recurse Center was to help and support students grow and learn amidst the freedom that the programme there afforded them. This kind of unstructured environment can come as a shock if you’ve only been able to work in structured settings in the past (schools, universities, big companies etc). The unstructured freedom to which Kaptur refers around the 1:30 mark also happens to be a hallmark that defines self-study work.

“Growth Mindset”

• Kaptur introduces the work of sociologist Carol Dweck and the distinction she’s drawn between fixed mindsets and growth mindsets.
  • A fixed mindset “holds that intelligence is a trait that some people have in some fixed amount, and they can’t really affect how much of it they have.”
  • A growth mindset “says that intelligence is something that you can work on and something you can develop with effort.”
• Whether someone adopts a fixed or a growth mindset then can determine how they view various other aspects of work. With regards to ‘effort’, people who believe in fixed mindsets hold that “if you are good at something, then it should be easy”. (And, conversely, if you’re bad at something, then it should be hard.) People with a growth mindset believe that you need to work hard at something to become better at it.
• Kaptur mentions how Dweck’s work has also shown that people who are praised for their effort in the task being performed tend to get better results [slight simplification of what she said] than those who are praised for what they achieved. This is a fairly well-known and well-publicised aspect of Dweck’s work.
• Kaptur notes that having a fixed vs growth mindset is something which (it seems) can be changed. And the switch from fixed to growth mindset can sometimes happen with deceptively easy tactics.
  • Sometimes it’s as simple as being aware of the things you’re saying (e.g. “Oh, I could never learn physics”). Kaptur suggests when you say “I am…” or “Some people are just…”, these might be times to examine whether you’re stuck in a fixed mindset pattern.
• Four strategies to change a fixed mindset:
  • 1) “Reframe praise and success” — if someone praises you for something you said by saying “you’re so smart”, you can mentally (most of the time you will say this to yourself internally) reframe this as “yes, I did a great job on that project. I worked very hard and I used an effective strategy.”
  • 2) “Reframe failure” — this is basically the opposite of the first strategy. Listen to your self-talk when you fail at something. If you’re saying “I failed because I’m bad” or “maybe I’m not cut out for this kind of work”, then try reframing it by asking yourself what you learnt from this attempt and what strategies you could change or use next time you try something similar.
  • 3) “Celebrate challenges” — if you can find ways to frame places where you struggle as a victory or an accomplishment in and of itself, this will really help drive you into that growth mindset. Accordingly, when the going gets tough, celebrate the difficult as an opportunity for growth, development and learning.
  • 4) “Ask about processes” — asking “how did you do that” can often be really illuminating, and is better (when viewing someone else’s work, for example) than saying “of course they did x or y; they are a genius/wizard”.
• On Confidence & Imposter Syndrome
  • Dweck’s research shows that confidence doesn’t help you respond to challenges. A lot of advice counsels feeling more confident in response to difficulties in work etc, but the angle Dweck is explores is the idea that “if you’re doing something new, confidence about something old doesn’t help you with that.”
  • If you hold a fixed-mindset, any moment is basically a chance to prove whether or not you are a failure. “So running into challenges is particularly stressful in that context.”
  • The trick to getting past all of this (of course) is to adopt a growth mindset. (20:10)

Strategies

Dweck’s research also shows that those who really embody a ‘growth mindset’ are also focused on strategies (and not just outcomes).

• “Make It Stick” — Kaptur offers some useful tips that she gathered from this great book. You can read my review here, in which I also extract some of my favourite actionable points.
  • “Learning is an acquired skill” — the premise of the book
  • 1) “Effortful retrieval > rereading” — this can be something like self-tests administered through Anki, or it can just be writing a review of a book after you’ve read it. Or it could be trying to summarise a recently-mastered topic by teaching it to someone else.
  • 2) “Spaced practice > massed practice” — Kaptur references three main ways to space out practice — spaced / varied / and interleaved.
    • Spaced = spacing practice sessions out over time rather than bunching it all together in a single mega-session
    • Varied = find a way to vary the kinds of practice you’re getting so that you’re not getting falsely sure of your command of the topic.
    • Interleaved = shuffling the kinds of exercise / practice you’re doing so that it’s somewhat random is better than always sticking to the same order (or a predictable order).
  • 3) “Difficulty is (usually) desirable” — (with the related point that making errors is usually desirable). One difficulty that isn’t desirable, however, is anxiety around performance. This comes out of Dweck’s research.

This is all difficult — a consequence of the fact that all of these strategies are difficult is that people don’t do it. They don’t challenge their recall, they don’t push into the areas they don’t know and so on, even after they’ve been specifically instructed in the ways that these strategies are more effective.

Kaptur encourages us to find ways to make effortful retrieval part of our everyday lives and work. This may mean you have to:

1. use a flashcard programme to test you
2. take guesses
3. be systematic about how you attack your problems. She is speaking in the context of programming, so she talks about debugging but it works for most problems. Have a hypothesis about what’s going wrong, and then tackle each part systematically.

She also suggests we find ways to implement spaced practice. The harder you work to retrieve a fact from your memory, the better this is for your grasp of that fact, so in the end while it feels horrible to test yourself on recall of materials you don’t know so well, it’s actually better for you.

With a growth mindset, errors are something to be welcomed (because they imply that there’s some sort of a feedback loop going on, from which you can, in turn, learn). Thus finding ways to get more feedback (about your writing, your code, etc) is to be encouraged.

Coming Soon: The Taliban Reader

Hot off the press. Hurst Publishers (my publisher for My Life With the Taliban, An Enemy We Created and Poetry of the Taliban) just released their spring/summer catalogue. As always, some great titles in the works.

Felix and I have our own humble contribution to scholarship on the Afghan Taliban: The Taliban Reader: War, Islam and Politics In Their Own Words. I'll add a link here to somewhere online where you can pre-order, but the blurb runs as follows:

Who are the Taliban? Are they a militant movement? Are they religious scholars? The fact that these and other questions are still raised is testimony to the way the movement has been studied, often at arm’s length and with scant use of primary sources.

The Taliban Reader forges a new path, bringing together an extensive range of largely unseen sources in a guide to the Afghan Islamist movement from a unique insider perspective. Ideal for students, journalists and scholars alike, this book is the result of an unprecedented, decade-long effort to encourage the emergence of participant-centred accounts of Afghan history.

This ground-breaking collection, ranging from news articles and opinion pieces to online publications and poems transcribed by hand in the field, sets the stage for a recalibration of how we understand and study the Afghan Taliban. It challenges researchers to forge new norms in the documentation of conflict and provides insight into the future trajectory of political Islamism in South Asia and the Middle East.

I'm really excited to have this project (somewhat soon) available. As noted in the blurb, it's the product of years of work, not to mention collaboration with various friends and colleagues.

I'll be writing more about the book closer to the release date (and once it's actually finished and submitted to the publishers).

Sustainable Climbing: Three Book Reviews

Today, three quick and dirty reviews. I read these books back-to-back. They reinforce each other, despite their authors being unconnected in any practical sense.

The first, ‘Espresso Lessons’ is a short version of Arno Ilgner's classic ‘The Rock Warrior’s Way’:

“Things you don't think about when you're climbing. Arno Ilgner has been working and writing about fear, technique and falling in climbing for years. This book is a distillation of some key insights he's had. I imagine this is a book I'll be returning to as I progress in the sport, but for a beginner there were some really useful parts. The key section for me was the one on falling, and on different ways of approaching this reality that confronts everyone, no matter what variety of climbing you're doing.”

I really liked how this book was more geared towards the mental work / challenge of climbing rather than purely the physical side (which many others have covered).

Next, Alex Honnold’s ‘Alone on the Wall’. If you don’t know Honnold, you should check out this video:

I never get tired of watching that. It’s an astounding feat. The book itself is a summary of the first thirty years of his life, mainly focusing on his big-ticket climbing activities:

“Alex Honnold's reputation precedes him. If you don't know who he is, go visit youtube and have your mind blown. This book is obviously not going to do the same thing as his climbing experiences, and it's written in a weird format. He gets a chance to explain himself on a bunch of things, returning continually to this question of risk and reward (that others often challenge him on). I could probably have done without the co-author's contextualisation and extrapolations on top of what Alex himself wrote. Also, the publisher made a really weird choice (at least for the Kindle version) in having all of Alex's sections in italic, which is a little annoying since his words are the core of the book and you have to read them all in italic throughout.
“Those quibbles aside, Alex Honnold is clearly at the top of his game in the climbing world and he has some really interesting rationalisations and thoughts on risk and competence. He tends to downplay everything, so it's hard to judge some statements since he'll just say "that was ok" or "that was easy" when to others it was probably much more difficult etc.
“He also has a really interesting and thought-provoking position on being 'minimal', as well as his commitment to donate 1/3 or so of his earnings to charity and a eco-foundation that he set up.
“Fans of his climbing will find lots to enjoy in this book. Others, perhaps not so much; for you, check out Mountains of the Mind: A History of a Fascination or Into Thin Air: A Personal Account of the Mount Everest Disaster.”

The final book was Yvon Chouinard’s ‘Let My People Go Surfing: The Education of a Reluctant Businessman’. Chouinard is the founder of the Patagonia outdoor clothing and equipment company. This was a surprisingly thought-provoking read:

“ An incredibly inspiring and thought-provoking account of the intersection of business practices, sustainable environmental activism and wilderness exploration.
“I hadn’t heard of Yvon Chouinard, the founder of Patagonia, prior to reading this book, though I now see that he’s been recently profiled in the New Yorker and many other places over the years.
“The first third of the book is an autobiographical account of how the company, Patagonia, was started along with some of the key inflection points along the way. Alongside this is a longer attempt to explain the principles and philosophies that guide how the company does its business. This includes everything from design principles (aiming for a quality minimal design over something that is perhaps cheaper but will last less long, for example) to their management philosophy and environmental activism work.
“It is this latter part of the book that gives a lot of food for thought for anyone running a business. More and more is being written on the issues surrounding growth — and I’m probably revealing my ignorance of a huge literature going back decades, if not longer — and Patagonia and the practices and philosophies here offer a challenge of sorts to anyone doing business in the twenty-first century. I will be chewing on the things in this book for a long while.”

It has been days since I finished this book, yet I’m still mulling it over. That’s as good a testament to the power of ideas as any.

PhD Tools: Goodreads for Cross-Pollination

[This is part of a series on the tools I used to write my PhD. Check out the other parts here.]

During the period I was working most intensely on my PhD writeup, I read over 100 books. I put that number out there not as a confrontation, but as an illustration that reading is important to ensure you don't get lost in a small box of your own creation. Judging purely from my own experience and from sporadic conversations with a loose handful of fellow PhD candidates, this can be a real problem.

Reading widely and about issues and problems wholly unrelated to your field of study is, I believe, the hallmark of a curious mind. If I meet someone for the first time and I'm assessing their work, I'm far more likely to be interested in the last ten books they've read than many other data points. Even the fact that someone is taking time to read, and to read diversely, is an important indicator for me.

I think I can date my adoption of this books-and-ideas-for-cross-fertilisation to when I read Steven Johnson's book Where Good Ideas Come From. He makes a strong case for a more deliberate approach to how you develop and cultivate ideas in your thinking life. (The book is short and highly suggestive of specific approaches to work. I'd recommend it if this kind of thing interests you).

I've found that things that I don't track and monitor tend to fall beside the wayside. Hence Goodreads and Beeminder and a number of other tracking tools. Goodreads allows you to set how many books you want to read each year and then keeps a convenient little widget reminding your how far ahead or behind you are of your goal. If you want a bit more of a 'sting' for non-compliance, you can hook up Beeminder and you'll be kept honest that way.

Reading books on unrelated topics was something I would do in the afternoons or evenings after my Four Perfect Hours. The time would be mine and I could read without any sense of guilt or that I wasn't making progress on my PhD writeup. No, I'd done my work in the morning, so now I could read to my heart's content.

Encounters with books are encounters with other ideas, other minds. It refreshes your approach and your sense of perspective -- both so important for your PhD. Give it a try! See how you can add in some reading time to your daily routine. Even 30 minutes before bed each evening adds up in the end.

Starting the Spaced Repetition Foundation

When I first learned about the idea of spaced repetition, I felt like I'd discovered a magic trick or a secret of some kind. Here was a piece of research that could transform how quickly I learned new words (I was studying Pashto at the time) and how well I recalled them. On the other side of that elation, I felt a simultaneous frustration and sense of disappointment that this piece of pedagogy / educational science hadn't come up before in my schooling career. All those vocab cards I'd created for my BA degree in Arabic and Farsi! So much inefficiency! Not to mention all the things I had studied at primary and secondary school. Most of that specific knowledge remains but it is like the shadow of its original form. I've recently started studying Maths again and I'm painfully aware just how much I've forgotten.

Spaced repetition is a principle that advocates a specific series of intervals between reviews of a particular fact or 'thing' that you want to memorise. A German scholar called Herman Ebbinghaus discovered that there is a pattern to how most humans learn and forget materials, and he outlined a specific algorithm to ensure optimum recall and retention of whatever you are trying to learn. For that, we must be thankful for the (seemingly) boring experiments he had to go through to get to that piece of insight.

Anki is a piece of software that manages your study and recall of individual pieces of information. The spaced repetition algorithm or insight is at the core of how Anki works and helps you. I've used Anki to learn languages, to memorise smaller facts and useful pieces of information, to cement my understanding of broader concepts, among other things. It's pretty adaptable to whatever your specific learning needs are. This is why I've stuck with Anki over its competitors. (I've tried pretty much all of them, and continue to do so, but Anki remains the most customisable and useful IMHO).

Over the years, I've had the privilege to share Anki with others along my travels. Sometimes this has come in the context of language learning, other times like with the friend who wanted to learn all the names of all the bones in the human body.

In fact, Anki was the original bridge or glue that started my friendship with Matt Trevithick, Sources and Methods co-host and all-round busy person. I walked into his office in Kabul -- he was working at the American University of Afghanistan at the time -- and spied a huge stack of flashcards in a box in the corner. I pointed to them and he explained with great pride how he'd learnt them all. We talked through his process a bit and soon enough I was singing the praises of Anki and how much time he'd save and...and...

We've had many conversations over the years relating to language-learning, the different ways Anki can be used and our overwhelming and continuing sense of disbelief that the principles of spaced repetition aren't more widely adopted in the field of education. People who get deep into self-study eventually stumble on SRS, since you often try to find ways to get faster or better in the absence of a teacher telling you what to do. The Quantified Self movement has been instrumental in spreading the gospel of SRS, too, in their special sessions devoted to the topic in their yearly conference, or through the pride-of-place given to show-and-tell explanations of how SRS has allowed someone to learn Chinese, or hieroglyphics or so on. (Click here for the QS list of talks referencing SRS. I'd highly recommend dipping your toe into some of these talks. Most are extremely engaging.)

Bringing matters up to the present day, I have a bit more time and bandwidth for focus now that the PhD is finished and Matt and I had been talking about this sense that more people should be using SRS for a few years, so we have finally bitten the bullet and started something to try to make that happen.

The Spaced Repetition Foundation is our institutional first step to start to spread the lessons to a broader audience and to more varied contexts. Our mission statement reads:

"The Spaced Repetition Foundation, an independent, not-for-profit center, is dedicated to advancing the adoption of spaced repetition as a supplementary learning tool.

"Despite the scientifically proven ability of spaced repetition to vastly increase the retention of information in the brain as a supplemental learning tool, the use of this technique is, at present, largely restricted to select individuals and students for personal enhancement or academic achievement. To date, no single center exists to advocate for the increased adoption of this approach in educational settings at the macro level, to increase public awareness of this useful tool, and to serve as a focal point for interested individuals to come together and work on these issues. 

"Attempting to solve this problem, Natalie, Alex and Matt, long-time users of spaced-repetition applications, decided in the summer of 2016 to start the Spaced Repetition Foundation, which seeks to function as an independent advocate dedicated to increasing the adoption of spaced-repetition technology wherever learning is happening."

Note that we are not completely and exclusively technology-centric in our approach. At least part of the work involves outreach, involves testing use cases and scenarios, and if it really is to find a place in the broader world (away from electricity and flashy phones, perhaps) it must be adaptable to low-tech or no-tech approaches.

Going forward, we'll be spreading the word about the science behind spaced repetition (spoiler: it works), ways everyone can use some form of review-recall testing in their lives, and generally galvanising different communities to find ways to rethink their approaches to knowledge acquisition and long-term recall through spaced repetition. We have some specific first steps planned, but I'll hold off with those details until they are more pertinent.

I'm extremely glad, too, that we will get to work with Natalie McKnight, the other co-founder, who brings a wealth of institutional and practical educational experience beyond simply the solitary learner that Matt and I represent. Natalie is Professor of Humanities and Dean of the College of General Studies at Boston University. I'm excited to work together with her to expand the kinds of communities and settings we can reach.

If you have any interest in the work we're doing, please sign up for our newsletter here or if you are interested in learning more, please do get in touch. Full details are available on our website at http://www.spacedrepfoundation.org.

PhD Tools: DevonThink for File Storage and Discovery

[This is part of a series on the tools I used to write my PhD. Check out the other parts here.]

Discovering similar notes in one of my DevonThink databases

I first heard about DevonThink in the same breath as Tinderbox. They go together, though they serve different purposes. Some people want to make an either/or decision about which to use. I see them as sufficiently different to assess them on their own merits and as per your usage scenario.

As with all tools, you should come to the decision table with a set of features that you're looking for. Don't just shop around for new things for the sake of newness or for the sake of having a really great set of tools. These programmes are not cheap. Luckily almost all of them come with generous trial versions or periods, but I don't recommend 'newness' as a feature of any particular merit.

Devonthink (I use the Pro Office version) is a place to store your files and notes. It can, I think, take any file you can throw at it. It comes with software for processing PDFs into fully-searchable documents (OCR software, in other words) which is part of the reason why the license for the Pro Office version of the programme is so expensive.

If you're anything like me, you're drowning in PDF documents. They all come with helpful names like "afghanistan_final_report_02_16.pdf" and unless you have a rigorous file hierarchy and sorting system, you'll probably be unable to find one file or the other. And using the basic file hierarchy system for storage doesn't help you with situations like when you want to store the same file in multiple folders (i.e. what if a report is about Afghanistan and Tunisia). (DevonThink has a feature which allows you to store the files in multiple locations, but without saving two copies of the file. Any changes or annotations you make in one file will automatically be transferred to the other).

You might ask yourself why you would need DevonThink and Tinderbox (see this post for more). The short answer is that they store different kinds of files/data, and that DevonThink is less about thinking than about storage (to a certain extent) and discovery.

One of the key features of DevonThink Pro Office is its smart searching algorithms, its ability to suggest similar texts based on the contents of what you are looking at, etc. It does this by means of a proprietary algorithm, so I can't really tell you how it works, but just know that it does. It works best on smaller chunks of text. In this way, I was reading through a particular source from the 3 million-word-strong Taliban Sources Project database and then I clicked the "See also" button and it had found a source I would never otherwise have read on the same topic, even though it didn't even use one of the keywords I would have used to search for it. It uses semantic webs of words to figure this stuff out. Anyway, beyond a certain database size, this power becomes really useful. It can also archive websites, store anything including text, do in-text searches on e-books etc etc. (Read more on how I use DevonThink for research in general here.)

I also used it a little as an archive for substantive drafts / iterations of the writeup process. That's another important part of the process: making backups of many different kinds. I never found any use for them, but at least they were there (just in case).

If you're a data and document hoarder at heart, like me, you'll soon have a Devonthink database (or several databases, split up by topic) that is bigger than you can fully comprehend it, or remember what was inside the files. At that point, search becomes really important. Not just a straightforward search, but the ability to input 'fuzzy' terms (i.e. if you search for "Afghanistan" it'll also find instances where it's incorrectly spelt "Afgahistan"), and boolean language, into your query is really powerful/useful. DevonThink is an amazing search tool. The company that developed the database software also make something called DevonAgent, which is basically a power-user search tool for the internet. Google on steroids, if you will. Fully customisable, scriptable... you can really go crazy with this stuff. I use it, but my PhD wasn't really about searching things on the internet, so I didn't use it much for my research or writeup. But it's a great tool, too.

In short, DevonThink is a research database tool that will help you store and find the documents that relate to your research, and do smart things to help you find sources and texts that maybe you'd forgotten you'd saved. Highly recommended for anyone working with large numbers of documents.

On Learning New Skills, #showyourwork and other housekeeping

Newly released from life under the PhD regime, I have been exploring new interests and indulging my curiosity down new pathways. Last time I wrote, I explained how I had taken to studying sharks and various aspects of conservation and marine biology. There was a certain amount of training around higher-level concepts in that course: in particular, on the scientific method, ways to problem-solve and so on, but in general the emphasis was on the material rather than specific skills.

I think that learning new skills -- expanding the lenses you have through which to view the world, or giving yourself more options for a variety of perspectives -- is an important part of becoming more useful. To that end, language learning was always an important part of getting to know any subject or place (either the implicit language of a particular domain, or the explicit language of a people or country).

Recently, I've taken to trying to expand my numeric and digital literacy. I've always been technically literate, at least to the extent that I was able to solve my problems, fiddle with code a little and play around with technical tools and programmes for which I have no formal training. That said, there is a wide gulf between that position and a more confident data literacy, where I can interpret things through the lens(es) of statistics, use tools to analyse what is going on and so on. I've always felt like this was a core weakness in my ways of understanding the world, so I'm now trying to address or remedy that.

My first step is to address the gaping holes. These are a mix of mathematics, statistics, probability as well as things like computational languages that will allow me to engage in these disciplines with more than a basic-level understanding. There is a fair amount of debate as to whether the name is useful or not, but for now, I'll state that I'm training myself in 'data science'.

I learn these kinds of skills best through a practice- and feedback-rich environment, so I'm taking a project-based approach to my studies. Khan Academy (what a resource!) is my mentor for mathematics, and Udacity (whose courses I've taken in the past and been very impressed by) is helping with the Python/coding aspect. Each skill group I learn is followed by a mini-project that allows me to use the skills in an applied context.

All of this is by way of introduction to what I really wanted to talk about today, which is a recent problem that I encountered while completing my coursework. The details don't matter that much, so I won't get into them, but suffice it to say for now that I was trying to write a python function that calculated the number of days between one date and another date.

One feature of coding that I find frustrating is the way loops (bits of code that repeat for as long as certain conditions remain met/unmet) can be included within loops, and sometimes maybe another set as well within the loop-within-a-loop. I'm new to this stuff, so this level of recursion (is that even the right word? I'm pretty sure recursion is used for something else) makes my brain hurt when I try to think about it too much. But think about it I must.

So there I was, with some broken bit of code, no idea how to move forward. The answer to the problem was just one click away, but I didn't want to just see the answer. I wanted to learn the thing that was absent. I wanted to learn how to get from my state of confusion to a state of understanding.

This seems to be a common enough problem in my new studies that I thought it might be useful to describe. You can explain the solution, at which point you understand how that particular problem was solved, but how do you improve the likelihood that you'll be able to solve a different problem in the future? Does looking at the solution help? Does spending a week staring at a piece of paper, wishing the solution to magically appear, help?

In the end, what I'm trying to get better at is problem-solving. As far as I've been able to read so far (in books like Sebastian Gutierrez's fantastic Data Scientists at Work), this skill is valued far above any specific skills like competence in one programming or computational language vs another. The specific languages can all be learnt. Getting better at solving problems, interviewees seem to constantly imply, that is much harder.

Which is where I am, trying to solve hard (hard for me, at least) problems.

My solution involved thinking about the problem more deliberately. Udacity hosts an online forum where students can post bits of code, questions etc. There's usually someone who answers the question within 24 hours. The emphasis is on finding new ways to think about problems rather than just providing the answer. So, teaching you how to fish instead of giving you a fish. That old chestnut.

I posted a question. In writing out the question, I was forced to be more deliberate in how I thought out the problem. By specifying the exact point where I saw something going wrong, I was forced to be more sequential, more methodical. I started to see new pathways forward to progress with the problem. I would then go off and work a bit more until I hit another roadblock, at which point I'd post a follow-up question. Then a bit more insight would follow the process of writing up the problem. Then a bit more work, another roadblock. You get the idea. I think I submitted 4 different questions/writeups in as many hours. By the end, I had thought my way out of the problem. Nobody needed to reply to my query; I had solved it myself.

This is quite a simple insight, in many ways: writing things down, making them concrete... these are things that help with the process of thought. Thought, taken out of the mushy-tissue-filled black box that is our brains and put on paper, is something that benefits from being methodical. I'd long known (at least, theoretically or implicitly) that writing helps thought. Every time I've worked on an essay or on a book, the process has clarified my thought in ways that wouldn't have been possible had I just remained satisfied with 'thinking' about things.

There are a bunch of small project ideas I have and want to use as ways of practising my new / fledgeling skills. I have certain data sets from my time in Afghanistan that I'd like to work with. There are other interests that I'd like to stimulate by applying this new tool / set of tools.

#showyourwork

This brings me neatly to my second point. I finished a book by Austin Kleon recently and it revolves around similar-ish ideas. Kleon talks about the importance of sharing the process of work as well as the work itself. He explains a bunch of the reasons why this is a smart idea, and he discusses various ways that you can enact this as a guiding practice going forward.

It reminded me that the last major learning experience I went through (not including languages or personal growth) was when I started travelling in and learning about Afghanistan. I was writing lots back then, either in emails to a group of friends and family, or later in blog form or in articles written for free for local magazines. (In my work for AfghanWire, too, I drafted a mini-encyclopedia of sorts, with entries for the important pieces of context (people, places, events). Researching all of that was a huge task, but looking back I'm certain that I learnt a lot through the process.)

The same thing happened when I started studying sharks, as I explained last time. I used twitter as a way of connecting with scholars and people who had already spent years studying the discipline. I used my podcast, Sources & Methods, to connect to at least one group (the Gills Club --> see the podcast here) and to connect to talk about that new interest.

All of which is a roundabout way of saying that I will be blogging more. Most blogs will not be as long as this, or previous posts. In the past, I would only consider it worth blogging if I had taken a week or few to gather together all the relevant insights to a particular topic or issue, but I'm not sure that's reasonable any more (thanks to Kleon's book) and I want to benefit from the power that comes from writing through problems on a more regular basis.

Housekeeping

I mentioned that I'm done with the PhD. So now the rest of my life starts. I haven't decided on the next step just yet, and there still some loops that need tying off. I have some research/report-writing to finish, a novel written last year during a fit of PhD-procrastination to edit/rework, and more to be done with my Jordanian colloquial Arabic.

One somewhat important development is that I'm moving to Amman (Jordan) this coming week. I'm not sure how long I'll be there, but consider it my base from now on. If you're ever passing through town, please do drop me a line.

My final piece of news is that Felix and I have signed a contract to work on a new book for Hurst (title and all other details TBC) which will be an anthology of Taliban writings/statements. It'll cover the whole gamut of their experience from the 1980s up until the present day. We'll be drawing from the materials of the Taliban Sources Project as well as other sources we've gathered along the way in previous years. I'm quite excited about the project, and it'll be an amazing resource once out. The problem for a lot of research, as I've mentioned before, is that the primary sources aren't used half as much as they ought. We hope this project will offer a corrective in this respect.