Different ways of knowing

    The Book of Life from the School of Life is an ever-expanding treasure trove of wisdom. In this entry, entitled Knowing Things Intellectually vs. Knowing Them Emotionally the focus is on different ways of how we ‘know’ things:

    An intellectual understanding of the past, though not wrong, won’t by itself be effective in the sense of being able to release us from the true intensity of our neurotic symptoms. For this, we have to edge our way towards a far more close-up, detailed, visceral appreciation of where we have come from and what we have suffered. We need to strive for what we can call an emotional understanding of the past – as opposed to a top-down, abbreviated intellectual one.
    I've no idea about my own intellectual abilities, although I guess I do have a terminal degree. What I do know is that I've spoken with many smart people who, like me, have found it difficult to deal with emotions such as anxiety. There's definitely a difference between 'knowing' as in 'knowing what's wrong with you' and 'knowing how to fix it'.
    Psychotherapy has long recognised this distinction. It knows that thinking is hugely important – but on its own, within the therapeutic process itself, it is not the key to fixing our psychological problems.

    […]

    Therapy builds on the idea of a return to live feelings. It’s only when we’re properly in touch with feelings that we can correct them with the help of our more mature faculties – and thereby address the real troubles of our adult lives.

    The article has threaded through it the example of having an abusive relationship as a child. Thankfully, I didn’t experience that, but it does make a great suggestion that finding the source of one’s anxiety and fully experiencing the emotion at its core might be helpful.

    And it is on the basis of this kind of hard-won emotional knowledge, not its more painless intellectual kind, that we may one day, with a fair wind, discover a measure of relief for some of the troubles within.
    Source: The Book of Life

    Beginning and middle

    “Don’t compare your beginning to someone else’s middle."

    (Jon Acuff)

    Slack's bait-and-switch?

    I remember the early days of Twitter. It was great, as there were many different clients, both native apps and web-based ones. There was lots of innovation in the ecosystem and, in fact, the ‘pull-to-refresh’ feature that’s now baked into every social app on a touchscreen device was first created for a third-party Twitter client.

    Twitter then, of course, once it had reached critical mass and mainstream adoption, killed off that third party ecosystem to ‘own the experience’. It looks like Slack, the messaging app for teams, is doing something similar by turning off support for IRC and XMPP gateways:

    As Slack has evolved over the years, we’ve built features and capabilities — like Shared Channels, Threads, and emoji reactions (to name a few) — that the IRC and XMPP gateways aren’t able to handle. Our priority is to provide a secure and high-quality experience across all platforms, and so the time has come to close the gateways.
    A number of people weren't happy about this, notably those who rely on the superior accessibility features available through IRC and XMPP. A software developer and consultant by the name of JC Brand takes Slack to task:
    We all know the real reason Slack has closed off their gateways. Their business model dictates that they should.

    Slack’s business model is to record everything said in a workspace and then to sell you access to their record of your conversations.

    They’re a typical walled garden, information silo or Siren Server

    So they have to close everything off, to make sure that people can’t extract their conversations out of the silo.

    We saw it with Google, who built Gtalk on XMPP and even federated with other XMPP servers, only to later stop federation and XMPP support in favour of trying to herd the digital cattle into the Google+ enclosure.

    Facebook, who also built their chat app on XMPP at first allowed 3rd party XMPP clients to connect and then later dropped interoperability.

    Twitter, although not using or supporting XMPP, had a vibrant 3rd party client ecosystem which they killed off once they felt big enough.

    Slack, like so many others before them, pretend to care about interoperability, opening up just so slightly, so that they can lure in people with the promise of “openness”, before eventually closing the gate once they’ve achieved sufficient size and lock-in.

    I’m definitely on the side of open source people/projects here, but it’s worth noting that the author uses the post to promote the solution he’s been developing. And why not?

    There’s a comment below the post which makes, I think, a good point:

    I'm betting this decision wasn't made by the same folks who were at Slack (or Facebook, Google, etc) and thought adding support for the open protocols was a good thing. I bet the decision is a product of time over any attempt to trick anyone. Over time people change roles, leave, and slowly new leadership emerges. Outside pressures (market growth, investors) require a change in priority and the org shifts away from supporting things that had low adoption and ongoing maintenance cost.

    So I don’t think it’s as malicious as the author implies (Bait and Switch) as that requires some nefarious planning and foresight. I think it’s more likely to be business/product evolution, which still sucks for adopters and the free net, but not as maleficent. Just, unfortunately, the nature of early tech businesses maturing into Just Another Business.

    Indeed.

    Source: Opkode

    The security guide as literary genre

    I stumbled across this conference presentation from back in January by Jeffrey Monro, “a doctoral student in English at the University of Maryland, College Park, where [he studies] the textual and material histories of media technologies”.

    It’s a short, but very interesting one, taking a step back from the current state of play to ask what we’re actually doing as a society.

    Over the past year, in an unsurprising response to a host of new geopolitical realities, we’ve seen a cottage industry of security recommendations pop up in venues as varied as The New York TimesVice, and even Teen Vogue. Together, these recommendations form a standard suite of answers to some of the most messy questions of our digital lives. “How do I stop advertisers from surveilling me?” “How do I protect my internet history from the highest bidder?” And “how do I protect my privacy in the face of an invasive or authoritarian government?”
    It's all very well having a plethora of guides to secure ourselves against digital adversaries, but this isn't something that we need to really think about in a physical setting within the developed world. When I pop down to the shops, I don't think about the route I take in case someone robs me at gunpoint.

    So Monro is thinking about these security guides as a kind of ‘literary genre’:

    I’m less interested in whether or not these tools are effective as such. Rather, I want to ask how these tools in particular orient us toward digital space, engage imaginaries of privacy and security, and structure relationships between users, hackers, governments, infrastructures, or machines themselves? In short: what are we asking for when we construe security as a browser plugin?
    There's a wider issue here about the pace of digital interactions, security theatre, and most of us getting news from an industry hyper-focused on online advertising. A recent article in the New York Times was thought-provoking in that sense, comparing what it's like going back to (or in some cases, getting for the first time) all of your news from print media.

    We live in a digital world where everyone’s seemingly agitated and angry, all of the time:

    The increasing popularity of these guides evinces a watchful anxiety permeating even the most benign of online interactions, a paranoia that emerges from an epistemological collapse of the categories of “private” and “public.” These guides offer a way through the wilderness, techniques by which users can harden that private/public boundary.
    The problem with this 'genre' of security guide, says Monro, is that even the good ones from groups like EFF (of which I'm a member) make you feel like locking down everything. The problem with that, of course, is that it's very limiting.
    Communication, by its very nature, demands some dimension of insecurity, some material vector for possible attack. Communication is always already a vulnerable act. The perfectly secure machine, as Chun notes, would be unusable: it would cease to be a computer at all. We can then only ever approach security asymptotically, always leaving avenues for attack, for it is precisely through those avenues that communication occurs.
    I'm a great believer in serendipity, but the problem with that from a technical point of view is that it increases my attack surface. It's a source of tension that I actually feel most days.
    There is no room, or at least less room, in a world of locked-down browsers, encrypted messaging apps, and verified communication for qualities like serendipity or chance encounters. Certainly in a world chock-full with bad actors, I am not arguing for less security, particularly for those of us most vulnerable to attack online... But I have to wonder how our intensive speculative energies, so far directed toward all possibility for attack, might be put to use in imagining a digital world that sees vulnerability as a value.
    At the end of the day, this kind of article serves to show just how different our online, digital environment is from our physical reality. It's a fascinating sideways look, looking at the security guide as a 'genre'. A recommended read in its entirety — and I really like the look of his blog!

    Source: Jeffrey Moro

    Do the thing

    “Do the thing you think you cannot do."

    (Eleanor Roosevelt)

    Memento mori

    As I’ve mentioned before on Thought Shrapnel, next to my bed I have a memento mori, an object that reminds me that one day I will die.

    My friend Ian O’Byrne had some sad news last week: his grandmother died. However, in an absolutely fantastic and very well-written post he wrote in the aftermath, he mentioned how meditating regularly on death, and having a memento mori has really helped him to live his life to the fullest.

    I believe that it is reminders like this one that we desperately need in our own lives. It seems like a normal practice that may of us would rather ignore death, or do everything to avoid and pretend is not true. It may be the root of ego that causes us to run away from anything that reminds us of this reality. As a safety mechanism, we build this comfortable narrative that avoids this tough subject.

    We also at times simply refuse to look at life as it is. We’re scared to meditate and reflect on the fact that we are all going to die. Just the fact that I wrote this post, and you’re reading it may strike you as a bit dark and macabre.

    With all of our technological, surgical, and pharmaceutical inventions and devices, we expect, almost demand, to live a long life, live it in good health and look good doing it. We live in denial that we will die. But, previous civilizations were acutely aware of their own mortality. Memento mori was the philosophy of reflecting on your own death as a form of spiritual improvement, and rejecting earthly vanities.

    So having a memento mori isn't morbid, it's actually a symbol that you're looking to maximise your time here on earth. When I used a Mac, I had a skull icon at the top of the dock on the left-hand side of my screen.

    Ian suggests some alternatives:

    There are multiple ways to include this process of memento mori in your life. For some, it is as simple as including artwork and symbols in your home and daily interactions. These may be symbols of mortality which encourage reflection on the meaning and fleetingness of life. In my home we have skulls in various pieces of art and sculptures that help serve as a reminder.

    I had opportunity last week to revisit Buster Benson's 2013 influential post Live Like a Hydra. In it, he references an experiment he called If I Lived 100 Times whereby he modelled life expectancy data for someone his age. It's interesting reading and certainly makes you think. How many books will you read before you die? How many new countries will you travel to? It makes you think.

    Back to Ian’s article and he turns to the Stoic philosopher Epictetus for some advice:

    Memento mori is an opportunity, should you take it, to reflect on the invigorating and humbling aspects of life. By no means am I an expert on this. I still struggle daily with understanding my role and mission in life. In these struggles, I also need to remember that I may not wake up tomorrow. As stated by Epictetus, “Keep death and exile before your eyes each day, along with everything that seems terrible— by doing so, you’ll never have a base thought nor will you have excessive desire.” These opportunities to reflect and meditate provide an opportunity to create and enjoy the life you want.

    Wise words indeed.

    Source: W. Ian O’Byrne

    Microcast #005

    [audio src=“http://188.166.96.48/wp-content/uploads/2018/03/episode-005.mp3”][/audio]

    Thinking through an approach to building Project MoodleNet that came to me this weekend, using Google search, Amazon filtering, and the Pinterest browser button as mental models.

    Links:

    Issue #295: A wee problem...

    The latest issue of the newsletter hit inboxes earlier today!

    💥 Read

    🔗 Subscribe

    Living an antifragile life

    Nassim Nicholas Taleb’s new book is out, which made me think about his previous work, Antifragile (which I enjoyed greatly).

    As Shane Parrish quotes in a 2014 article on the subject, Taleb defines antifragility in the following way:

    Some things benefit from shocks; they thrive and grow when exposed to volatility, randomness, disorder, and stressors and love adventure, risk, and uncertainty. Yet, in spite of the ubiquity of the phenomenon, there is no word for the exact opposite of fragile. Let us call it antifragile. Antifragility is beyond resilience or robustness. The resilient resists shocks and stays the same; the antifragile gets better. This property is behind everything that has changed with time: evolution, culture, ideas, revolutions, political systems, technological innovation, cultural and economic success, corporate survival, good recipes (say, chicken soup or steak tartare with a drop of cognac), the rise of cities, cultures, legal systems, equatorial forests, bacterial resistance … even our own existence as a species on this planet.
    This definition, and the examples Taleb pointed to in his book helped me understand the world a bit better. It's easy to point to entitled people and see how they manage to get richer no matter what happens. But I think we all know people (and in fact companies, organisations, and communities) that are just set up for success. The notion of them being 'antifragile' helps describe that.

    Parrish quotes Buster Benson who boils Taleb’s book down to one general, underlying principle:

    Play the long game, keep your options open and avoid total failure while trying lots of different things and maintaining an open mind.
    More specifically, Benson notes Taleb's 10 principles of antifragility:
    1. Stick to simple rules
    2. Build in redundancy and layers (no single point of failure)
    3. Resist the urge to suppress randomness
    4. Make sure that you have your soul in the game
    5. Experiment and tinker — take lots of small risks
    6. Avoid risks that, if lost, would wipe you out completely
    7. Don’t get consumed by data
    8. Keep your options open
    9. Focus more on avoiding things that don’t work than trying to find out what does work
    10. Respect the old — look for habits and rules that have been around for a long time
    Some great suggestions here, and I'm very much looking forward to reading Taleb's new book. As a bonus, in putting together this post I discovered that, after jobs at Twitter, Slack, and Amazon, Buster Benson is writing a book. He's looking for 100 supporters at $1 a month so I didn't even think twice and pledged!

    Source: Farnam Street

    The end/beginning

    “Often when you think you’re at the end of something, you’re at the beginning of something else."

    (Fred Rogers)

    Archives of Radical Philosophy

    A quick one to note that the entire archive (1972-2018) of Radical Philosophy is now online. It describes itself as a “UK-based journal of socialist and feminist philosophy” and there’s articles in there from Pierre Bourdieu, Judith Butler, and Richard Rorty.

    If nothing else, these essays and many others should upend facile notions of leftist academic philosophy as dominated by “postmodern” denials of truth, morality, freedom, and Enlightenment thought, as doctrinaire Stalinism, or little more than thought policing through dogmatic political correctness. For every argument in the pages of Radical Philosophy that might confirm certain readers' biases, there are dozens more that will challenge their assumptions, bearing out Foucault’s observation that “philosophy cannot be an endless scrutiny of its own propositions.”
    That's my bedtime reading sorted for the foreseeable, then...

    Source: Open Culture

    Do the tools you use matter?

    An interesting post from Austin Kleon on whether tools matter. It was prompted by the image accompanying this post, which met with some objections when he shared it with others:

    On my Instagram, a follower was very upset with the above cartoon, saying it was “mean” and “hurtful” and not smart and ungrateful to my fans, and that I should try to “remember what it was like to be a beginner.”
    He defends his position, partly by telling stories, but also by stating:
    There are actually very good reasons for not wanting to teach young artists. There are good reasons for not answering a question like, “What brand of pen do you use?” or questions about process at all.

    If you are just starting off and I tell you exactly how I work, right down to the brand of pen and notebook, I am, in a some small sense, robbing you of the experience of finding your own materials and your own way of working.

    It’s been interesting seeing Bryan Mathers' journey over the last five years. I’ve seen him go from using basic apps which work ‘just fine’ to reaching the limits of those and having to upgrade to more powerful stuff. That’s a voyage of discovery, but along the way it’s absolutely useful to find out what other people use.

    Kleon points out that we can do better than tool-related questions:

    So, yes, the tools matter, but again, it’s all about what you are trying to achieve. So a question like, “What brand of pen do you use?” is not as good as “How do you get that thick line quality?” or “How do you dodge Writer’s Block?”
    I'm a fan of a great site called Uses This (formerly 'The Setup') which asks a range of people the hardware and software they use to get stuff done. The interviews are always structured around the same four questions, but the best responses are ones that take the idea and run with it a bit.

    Note to self: update the version of this I did back in 2011.

    Source: Austin Kleon

    Is your smartphone a very real part of who you are?

    I really enjoy Aeon’s articles, and probably should think about becoming a paying subscriber. They make me think.

    This one is about your identity and how much of it is bound up with your smartphone:

    After all, your smartphone is much more than just a phone. It can tell a more intimate story about you than your best friend. No other piece of hardware in history, not even your brain, contains the quality or quantity of information held on your phone: it ‘knows’ whom you speak to, when you speak to them, what you said, where you have been, your purchases, photos, biometric data, even your notes to yourself – and all this dating back years.
    I did some work on mind, brain, and personal identity as part of my undergraduate studies in Philosophy. I'm certainly sympathetic to the argument that things outside our body can become part of who we are:
    Andy Clark and David Chalmers... argued in ‘The Extended Mind’ (1998) that technology is actually part of us. According to traditional cognitive science, ‘thinking’ is a process of symbol manipulation or neural computation, which gets carried out by the brain. Clark and Chalmers broadly accept this computational theory of mind, but claim that tools can become seamlessly integrated into how we think. Objects such as smartphones or notepads are often just as functionally essential to our cognition as the synapses firing in our heads. They augment and extend our minds by increasing our cognitive power and freeing up internal resources.
    So if you've always got your smartphone with you, it's possible to outsource things to it. For example, you don't have to remember so many things, you just need to know how to retrieve them. In the age of voice assistants, that becomes ever-easier.

    This is known as the ‘extended mind thesis’.

    This line of reasoning leads to some potentially radical conclusions. Some philosophers have argued that when we die, our digital devices should be handled as remains: if your smartphone is a part of who you are, then perhaps it should be treated more like your corpse than your couch. Similarly, one might argue that trashing someone’s smartphone should be seen as a form of ‘extended’ assault, equivalent to a blow to the head, rather than just destruction of property. If your memories are erased because someone attacks you with a club, a court would have no trouble characterising the episode as a violent incident. So if someone breaks your smartphone and wipes its contents, perhaps the perpetrator should be punished as they would be if they had caused a head trauma.
    These are certainly questions I'm interested in. I've seen some predictions that Philosphy graduates are going to be earning more than Computer Science graduates in a decade's time. I can see why (and I certainly hope so!)

    Source: Aeon

    Microcast #004

    [audio src=“http://188.166.96.48/wp-content/uploads/2018/03/microcast-004.mp3”][/audio]
    Is it really a ‘skills gap’ that we should be talking about? What’s the real problem here?

    Links:

    Masterpieces

    “Masterpieces are not single and solitary births; they are the outcome of many years of thinking in common, of thinking by the body of the people, so that the experience of the mass is behind the single voice.”

    (Virginia Woolf)

    Microcast #003

    [audio src=“http://188.166.96.48/wp-content/uploads/2018/03/microcast-003.mp3”][/audio]
    What technologies are going to be used with Project MoodleNet?

    Links:

    30,000 hours of sleep

    “Those who research world-class performance focus only on what students do in the gym or track or practice room. Everyone focuses on the most obvious, measurable forms of work and tries to make these more effective and more productive. They don’t ask whether there are other ways to improve performance, and improve your life.

    This is how we’ve come to believe that world-class performance comes after 10,000 hours of practice. But that’s wrong. It comes after 10,000 hours of practice, 12,500 hours of deliberate rest, and 30,000 hours of sleep.”

    (Alex Soojung-Kim Pang)

    Teaching kids about computers and coding

    Not only is Hacker News a great place to find the latest news about tech-related stuff, it’s also got some interesting ‘Ask HN’ threads sourcing recommendations from the community.

    This particular one starts with a user posing the question:

    Ask HN: How do you teach you kids about computers and coding?

    Please share what tools & approaches you use - it may Scratch, Python, any kids specific like Linux distros, Raspberry Pi or recent products like Lego Boost… Or your experiences with them.. thanks.

    Like sites such as Reddit and Stack Overflow, responses are voted up based on their usefulness. The most-upvoted response was this one:

    My daughter is almost 5 and she picked up Scratch Jr in ten minutes. I am writing my suggestions mostly from the context of a younger child.

    I approached it this way, I bought a book on Scratch Jr so I could get up to speed on it. I walked her through a few of the basics, and then I just let her take over after that.

    One other programming related activity we have done is the Learning Resources Code & Go Robot Mouse Activity. She has a lot of fun with this as you have a small mouse you program with simple directions to navigate a maze to find the cheese. It uses a set of cards to help then grasp the steps needed. I switch to not using the cards after a while. We now just step the mouse through the maze manually adding steps as we go.

    One other activity to consider is the robot turtles board game. This teaches some basic logic concepts needed in programming.

    For an older child, I did help my nephew to learn programming in Python when he was a freshman in high school. I took the approach of having him type in games from the free Python book. I have always though this was a good approach for older kids to get the familiar with the syntax.

    Something else I would consider would be a robot that can be programmer with Scratch. While I have not done this yet, I think for kid seeing the physical results of programming via a robot is a powerful way to capture interest.

    But I think my favourite response is this one:

    What age range are we talking about? For most kids aged 6-12 writing code is too abstract to start with. For my kids, I started making really simple projects with a Makey Makey. After that, I taught them the basics with Scratch, since there are tons of fun tutorials for kids. Right now, I'm building a Raspberry Pi-powered robot with my 10yo (basically it's a poor man's Lego Mindstorm).

    The key is fun. The focus is much more on ‘building something together’ than ‘I’ll learn you how to code’. I’m pretty sure that if I were to press them into learning how to code it will only put them off. Sometimes we go for weeks without building on the robot, and all of the sudden she will ask me to work on it with her again.

    My son is sailing through his Computer Science classes at school because of some webmaking and ‘coding’ stuff we did when he was younger. He’s seldom interested, however, if I want to break out the Raspberry Pi and have a play.

    At the end of the day, it’s meeting them where they’re at. If they show an interest, run with it!

    Source: Hacker News

    Microcast #002

    Building a bridge

    “I learned that a long walk and calm conversation are an incredible combination if you want to build a bridge.”

    (Seth Godin)

← Newer Posts Older Posts →