A bigger container

An idea I like from Zen Buddhism is becoming a Bigger Container.  My understanding of the idea is this: There are a lot of difficult/bad/sad/scary things going on in the world, ranging from serious global issues, war, famine, terrorism, etc; to things in your city like homelessness or joblessnes; to things in your family, like difficult relationships or substance abuse; to tiny things in your life like a daunting project at work, or your inbox, or going through bills or cleaning your desk. It's hard to open yourself up to all of these things, because the are overwhelming and scary.  So the easy thing to do is turn away - to avoid. Becoming a bigger container means making space within yourself to face an increasing number of these things, with compassion and without fear.  Being able to hold them and look them in the eye without any one of them grabbing control of you, carrying you away or breaking you. From the reading linked above:

"What is created, what grows, is the amount of life I can hold without it upsetting me, dominating me. At first this space is quite restricted, then it’s a bit bigger, and then it’s bigger still. It need never cease to grow. And the enlightened state is that enormous and compassionate space. But as long as we live we find there is a limit to our container’s size and it is at that point that we must practice. And how do we know where this cut-off point is? We are at that point when we feel any degree of upset, of anger. It’s no mystery at all. And the strength of our practice is how big that container gets."

When am most proud of myself, I am able to make space within myself to deal with hard things.  To look them in the eye, be with them, and not look away.  When I'm frustrated with myself, it's often because I'm avoiding doing this. The visualization that works for me is that when you become a bigger container -- when you can generate some perspective -- each of these individual things becomes smaller by comparison; less dominant. It can be hard to do sometimes but I find it to be a really useful construct.

Cryptonetworks and why tokens are fundamental

"Cryptonetworks" can help us build a more competitive, innovative, secure and decentralized Internet.  "Tokens" (also known as cryptocurrencies or cryptoassets) are integral to the operation of cryptonetworks.  As we design new laws and regulations in this emerging space, we should keep these concepts in mind, beyond the financial aspects that are today's primary focus.


In recent months, there has been untold attention paid to cryptocurrencies, blockchains and the coming of the "decentralized web" or "web3".  And, given the rise of the cryptocurrency markets (over 1500 coins, with a total market cap of $370B as of today) and the recent boom in token-based fundraising (including a healthy dose of scams and shenanigans) there is increasing regulatory and legal attention being paid to the sector, and rightly so. This is a profound, and confusing, innovation.  As John Oliver so aptly put it last week, it's "everything you don't understand about money combined with everything you don't understand about computers".  Basically right. At USV, we've spent the better part of the past five years exploring and investing in this space, and now have roughly a dozen investments touching it in one way or another.  As we have watched the technology and market evolve, alongside the public discourse, we feel its important to reiterate why we think this technology is so powerful and important, and contribute to the ongoing collective learning about how it works. While much of the focus, especially in the context of regulations, is on the financial and fundraising applications of cryptocurrencies, our interest continues to be on the potential for cryptonetworks to provide digital services, such as computing, file storage, social applications, and more. You might ask, why is it important to have another way to provide digital services?  We already have lots of websites and apps that do that today.  The reason cryptonetworks are an interesting addition to today's digital services is their core architecture of decentralization.  Just as the original internet gave us a decentralized layer on top of the telecommuncations network, which resulted in untold innovation, cryptonetworks are a decentralized way to provide digital services.  Chris Dixon has a great post exploring why this is important, including the historical parallels to the original internet. The decentralized architecture of cryptonetworks has the potential to address many issues in today's tech and business landscape, including information security, market competition, product innovation, and equitable distribution of gains from technology. Imagine, for instance, if the owners or users of Amazon/Google/Facebook/Reddit/etc. were able to "fork" the product and launch an identical competing copy, if they didn't agree with the direction of the company?  And imagine if all of the users of & contributors to a web platform also had a direct, monetary interest in the success of that platform, that reflected their own contributions as community members?  This is how cryptonetworks work, since they are essentially open-source, mutually owned & operated web platforms.  Each network's cryptocurrency or "token" acts as the internal currency, incentive mechanism, and "binding agent" for the other processes that help the platform function.  And further, the internal data structure of cryptonetworks, the distributed ledger or blockchain has unique properties that can improve privacy and data security.  See also, Steven Johnson's recent NYT piece exploring these ideas. With that as context, it's important to walk through how cryptonetworks function, and importantly, how tokens function within them -- especially given the growing regulatory scrutiny around how tokens are created and traded. The deck below (full size / downloadable PDF) is meant to help explain this.  While it does touch on some public policy goals at the end, it does not attempt to make specific, detailed recommendations.  The main takeaways should be (a) cryptonetworks are an important new innovation in how digital services are delivered, (b) tokens are fundamental to their operation, and (c) as we design new laws and regulations in the space, we should keep (a) and (b) in mind as guiding concepts. 

Running the USV analyst application process using Ziggeo, FormAssembly and Airtable

We are in the middle of our 2018 Analyst hiring process at USV.  For the last several hiring cycles, USV has had an open process where anyone can apply.  I actually wrote about it back in 2011, right before I joined, remarking at the high quality of applicants that the process produced. That is still the case today.  In this year's Analyst application produced 326 applicants, of remarkable accomplishment.  Albert has been writing updates about the process on the USV blog.  At this point, we have reviewed all of the applications, and are working towards a second round of interviews with semi-finalists. What I'll cover here is how we've managed the process this time. For the past 3 cycles we have solicited video responses as part of the application process, powered by Ziggeo.  Having video in the application process has really worked for us.  Even with short videos (our were 30 and 60 seconds, respectively), you can get a good sense of a person's manner of speaking, sense of confidence, thoughtfulness, etc.  While it doesn't tell the whole story, it's been a very helpful signal for us over the years. The first time, we used a custom web application that Oliver from Ziggeo helped us build (source code here).  The second time, we re-used that codebase with some modifications.  This time, we tried to make it even more simple, using only off-the-shelf tools. What we ended up with was a combination of FormAssembly for the form itself (because FormAssembly supports Ziggeo integration) Ziggeo for the videos, and Airtable for the ultimate data storage and workflow management. FormAssembly made it easy to build the form, including nice features like letting applicants save a partially-completed form and come back to it later.  The form looked like this:

post image

Ziggeo made it really easy to capture the video.  Note the embedded video recorder in the form above, which looks like this when you fire it up:

post image

For our internal process of reviewing applications, we needed something else, which is where Airtable comes in. For those who don't know Airtable, it's basically a hybrid spreadsheet / database, with handy aspects of each.  It's like a spreadsheet in that it's really easy to update the schema and edit data.  It's like a database in that you get persistent records that are linkable with one another (a feature that we didn't use here but we make lots of use of elsewhere internally), and that has a great API. There's not an automatic way to move records from FormAssembly to Airtable, so we just did CSV export/import.  Ultimately, we ended up with a view like this, where we could review applicants one-by-one and then comment/score/sort/etc:

post image

You can see a stripped-down version of the Airtable we used for the process here. All in all, this setup worked great.  It took zero coding to build, had a really modest number of errors or mishaps, and handled our workflow well. There are, of course, a few things that could have been better.  Top of the list would be direct Ziggeo support within Airtable.  Airtable has a feature where you can expose a form that will collect data directly into a table in Airtable.  Ideally, you'd be able to have a "video" type form element that would embed a Ziggeo recorder directly in the Airtable form.  Then, on the back end, it would be great if you could view those videos directly in Airtable, rather than clicking out to a link -- imagine the screenshot above, but with embedded video players rather than links.  I suspect a lot of people use Airtable for applicant tracking, and I'm sure this kind of video support would be popular.  Another would be automated connectivity between FormAssembly and Airtable, maybe via Zapier. So, that's what we did.  Remarkably easy to manage this time around -- thank you to all the teams out there building the tools that make this kind of thing easier by the day.

The Slow Hunch by Nick Grossman

Written by

Investing @ USV. Student of cities and the internet.

Subscribe