Form factor

Over the past few weeks, I have varied up my computing habits a bit.  For a laptop, I have been using a Pixelbook, and I have also been spending more timing using an iPad Pro for work (vs my default of using a Mac laptop for everything).

What I have discovered is that the form factor of the device I'm using matters a lot in terms of what kinds of work it supports best.  Both devices have exactly the same apps, but the experience on each couldn't be more different.

For example, the iPad (the 10.5" Pro model in particular) is great for long-form reading: I use Pocket to gather articles (from wherever I am - phone, tablet or computer) and when I want to sit down and read, I do it on the iPad.  And beyond reading, email on the iPad is possible, but forces you to write shorter responses.  So it's both good for deep reading and also good for quick email processing.  That combination has been working great for me.  

I have been trying to avoid reading -- especially at home, when I am around my family -- on my phone.  There is something about the posture you take when you read on a phone that is both uncomfortable and anti-social.  Hunched over, hands up, squinting down.   By contrast, reading on the iPad feels more like reading a book or a newspaper - open, relaxed.  Not only is the reading area a better size, but it feels more like a "public" device, in the sense that by reading it you aren't lost in the private world of your phone.

The Pixelbook (google's new chromebook) is great in a different way.  What is nice about the Pixelbook is how simple login and setup are (especially if you are a heavy google apps / google chrome user).   You just sign in, load up some web apps (and many enterprise desktop apps such as Slack and Zoom work just as well as Chrome apps) and you're good.  It feels very lightweight and efficient. Low overhead, lean and mean.  When I log into the Pixelbook I feel ready to go.   (There is also an added security benefit to using a Chromebook for work - sign-in can be protected by 2FA).

It just goes to show that the form factor / design / packaging of a system (device, app, etc) really matter so much in terms of how it can / should / will be used.  Maybe this is obvious, but it has really struck me lately.

A little, and then a little more

Back in May, I had what ended up being a major hand surgery -- repairing a torn tendon and in the process reconstructing the end of my pinkie by grafting tendons borrowed from my ring finger.  As a result, I am now recovering from two injuries -- the pinkie itself and the ring finger that was the donor.

What I have learned is that most surgeons under-sell the recovery process.  Surgery is invasive and often causes as many problems than it solves.  In my case, the scar tissue from the surgery is a huge barrier to recovery -- it is currently stopping my tendons from "gliding" correctly, which is what lets you actuate your fingers in both directions.

So I have been going to occupational therapy for the last few weeks to work towards regaining motion in my hand.  It's really 8 distinct projects to regain fluidity on both tendons on each of 4 knuckles (3 in my pinkie and one in the ring finger).

The progress has been slow - each session I find out how many degrees of motion I have gained (or lost) in each knuckle, in each direction.  It is frustrating, because especially in the area of the major reconstruction, it is hard to feel any motion or progress.

But I realized today that even in the worst spot there is at least a wiggle.  And working that wiggle -- even a tiny bit -- gets you a little farther along, and enables a little more.  So I have to believe that progress is possible and work the wiggle so that tomorrow I can work it a little more.  

Like with a lot of things, it is hard to accept that progress happens slowly and incrementally, rather than quickly and fully.    But I am trying to remind myself, that like with everything, we are working with compound interest and that the goal is to get a little better every day, and then build on that.  Easier said than done, of course, but important to remember that that's how things usually work.

Layers

A central concept on the internet is Layering.  Each of the protocols in the internet stack talks to the layer directly above and below it -- new protocols can be added as long as they speak the language of their layer.  Protocols at one layer can be upgraded so long as they don't break compatibility with the layer above or below it.  This architecture maximizes interoperability and allows for a great deal of flexibility.  The shape of the layers has been described as an hourglass, like this:

(credit: University of Calgary)

Beyond layering at the protocol level, we have gone on to build layers at the infrastructure and application levels.  Infrastructure like AWS and Cloudflare, software libraries like Node, Rails, and jQuery, services like Twilio and Stripe.  To build an application today, you do not need to go build a data center (or many of them), think about how to manually process HTTP requests, or write bare-metal adapters to the payments or telecom systems. In the crypto/blockchain space, we are just at the very beginning of establishing layers. I think it's safe to say that today's blockchain landscape looks more like the early days of AOL, Prodigy and Compuserve (standalone, disconnected networks) than like the open, interconnected internet.  A major reason for this is the introduction of cryptocurrencies and tokens, which provide a strong incentive -- for now at least -- for starting new networks and maximizing value of existing networks.   But, as teams continue to build, and continue to build the same things over and over again, layering seems both inevitable and needed. Within blockchains, layers delineate networking (libp2p as a leading tool), consensus (tendermint, hashcash and others), applications/smart contracts, and perhaps indexing/search (something everyone is doing on their own right now, but that thegraph is looking to solve as a layer). Perhaps the most interesting question is how different blockchain systems may layer together.  Cosmos and Polkadot are building systems for interoperable blockchains via a hub-and-spoke model, with shadow assets pegged to outside chains for interoperability.  Interledger is attempting to be a more universal cross-ledger (ledger, meaning blockchains and otherwise) protocol, akin to TCP/IP in the core internet stack. How these systems interconnect, and layer atop one another, seems like a fundamental question as we move from the speculative phase to the functional phase.  We are just now beginning to get glimpses of it.

The Slow Hunch by Nick Grossman

Written by

Investing @ USV. Student of cities and the internet.

Subscribe