Sunday, October 20, 2019

Integrity and Athletics

For years, I've been opposed to athletic recruiting at elite academic institutions; it seems obvious to me that athletic accomplishment is but one factor that should be considered individually and in the process of building out a well-rounded student body. In particular, the prioritization of athletics over artistic, musical, and scientific excellence during the university recruiting process has always struck me as a quirk of history.

This quirk of history recently made the national news when investigators discovered that certain coaches were taking bribes from wealthy parents in order to push students through the recruiting process.

What confuses me isn't that this happened, but that university leadership didn't take this opportunity to modernize the system. This would have been the perfect catalyst to take a national stand and act with courage and intellectual fortitude in order to attempt to switch the Ivy League from Division I to Division III, or to remove itself from the NCAA entirely. Instead, university leaders took the path of least resistance, instituting minor and insignificant policy changes which do nothing to address the root cause of the problem: allowing college admissions to be warped by the need to recruit athlete-students rather than student-athletes.


Thursday, October 3, 2019

Cyberwar and the Economic Battlespace

Note that cyberwar for the purposes of this essay is meant to refer to mechanisms of conflict that are fundamentally oriented around gaining access to siloed intellectual property, rather than the conventional definition which is more expansive and includes political manipulation and the targeting of traditional military target with cyber-weaponry, sometimes resulting in the destruction of physical property.

As an increasing amount of aggregate global value comes from intangible, non-traditional assets such as human capital and intellectual property, and as the relative value of raw materials and commodities decreases, modern nation states face a new competitive landscape. In particular, while historical conflict was zero sum as a result of finite amounts of geographic space and the fixed resources contained within a given border, modern conflict also involves attempts to develop, destroy or redistribute these more abstract resources.

These abstract resources have a number of attributes which make them challenging to think about without updating our fundamental assumptions which underpin many classical theories of conflict. This essay focuses on the conflict over intellectual property, but I believe that conflict over human capital is equally fascinating given trends towards specialization and a much wider distribution of human capital across the population.

Intellectual property has long been a challenging type of capital to protect; the asymmetry between the high cost of developing new technology and the relatively low cost of deploying existing technology makes it a tempting target for competitors. If achievable, acquiring access to technology without bearing the development costs is a strong strategy.

Further, unlike in a traditional conflict, transferring technology between combatants does not harm either entity on an absolute basis: technology transfer eliminates the profit that can be extracted by producers of the technology, but the intrinsic value is often increased, and always conserved.

In these terms, belligerents in cyberwar could be considered as fundamentally moral from the perspective of a finite game: by stealing proprietary property and releasing it publicly, access to that technology would become broader, increasing the amount of value in the world.

At the limit, as the share of "abstract value" created by access to new technology increased relative to the share of "raw value" defined by access to physical materials, it would be theoretically possible to completely redistribute value across the population, resulting in a non-violent Marxist equilibrium ("from each according to his ability to each according to his need").

However, from a capitalist's perspective, this equilibrium would also signify the end of progress. If the only way to create new value is through developing new technology, and the pervasive theft of intellectual property decimates the return on capital that a private entity can expect to obtain from the development of new technology, markets will no longer be able to function to fund and develop new technology, and this equilibrium will represent a pyrrhic victory. Without the ability to fund innovation in present by relying on proceeds from the future, technology would stagnate and one of our most unique assets as a species (the ability to shape our own evolution) would be destroyed.

As such, cyberwar represents a fundamental battle between socialist and capitalist values: if you believe that technology development would occur at the same rate without market incentives, it is fundamentally moral to redistribute it as soon as its developed. If, on the other hand, you take the other side, and especially you believe in non-linear compounding growth of knowledge and technology, this equilibration is likely the single greatest threat to progress for our species, and you should probably take up arms in this quintessentially modern form of battle.

The good news, though, is that once we start fighting over abstract goods, with abstract weapons, in abstract spaces, the only true harm that is possible in the present is relative, which means that even the price of conflict is fundamentally abstract and requires discounting into future.

And how fun is that!

Saturday, July 13, 2019

Model-driven Product Management

Towards the end of 2018, I found myself struggling with the new demands of my job - for the past four years, I had been operating in a relatively simple world with a single major customer and a relatively small engineering team (~25 engineers).

Six months earlier, I had started leading product management for a bigger team with ~100 major customers and ~200 engineers. While I felt like we had been doing an okay job and were prioritizing the right things, I knew we could do a lot better. Additionally, at this scale, it was becoming difficult to communicate how the prioritization process worked.

So over the past few months, I've been thinking about how to build a loosely-democratic technocratic and believability-oriented system for deciding which projects to prioritize over time.

Note that this system may not be ideal for other organizations or other product managers: I'm a hybrid Business / Technical Product Manager per Stripe's description, and so it's clearly biased by those perspectives. Our operating environment is also probably pretty different than most -- it's characterized by a substantial disconnect between users and payers, which leads to a lot of indirection between value creation and value capture, large per-client integration teams, which leads to indirection between user feedback and the product team, and very discontinuous revenue growth given the relatively small number of large scale (~1m ARR) customers.

Effectively, there are two models, a cost-oriented model which is driven primarily by engineering, and a value-oriented model which is driven primarily by sales. The goal of the system is to order a list of projects by their business value, and then achieve maximum throughput and long-term velocity from the engineering team against those projects.

First, the value model - the current instantiation is less sophisticated, but at the limit, I'm hoping to implement a believability weighted democratic process by which every member of the business development team is able to vote on the full spectrum of available projects. Votes are then weighed by the believability of the voter, their position in the organization, and the amount of value (DCF of revenue / user happiness) that they would produce. Currently, the process is much simpler: each account votes on a 1-10 scale for each of the projects (with stack ranking), then the head of sales provides a vector of weights which is applied to the per-account votes. We add a couple of magical bonuses, which produces the business-weighted value vector.

A visualization of the current value model is represented in this prioritization matrix:


On the cost side, the projects are arranged in a dependency graph modeled after the concept of a tech tree, a game mechanic common in many strategy games. Currently, dependencies are firm, though in the future, I've considered adding additional bonuses and soft dependencies to better express the distinction between MUST and SHOULD dependencies. This graph is expressed as a DOT file, which produces an intuitive visualization, with green nodes representing active projects, grey nodes representing completed projects, and yellow nodes representing available projects. Each project is given a rough cost (using a rough fibonacci scale).

A visualization of the current cost model is represented in this dependency graph:













Then, the value vector is applied to the graph, and value is propagated through the dependencies to sort all of the available projects (projects where all of the dependencies are either active or completed). I've played around with various algorithms - the one I was happiest with is one that rolls the value back to all parents equally rather than splitting it, and which doesn't dissipate. This seems to result in the the most intuitive ranking, but without distinguishing between must / should dependencies, it can end up overvaluing infrastructure projects - dissipation can help with this at the cost of losing expressivity in very deep trees.

So the result is a series of value vectors for the projects:
  • Vectors representing the votes from each individual account
  • A vector which represents the business' strategic weights applied to the per-account votes
  • A graph-propagated value vector that takes into account engineering cost and cross-project dependencies.
Having these three vectors makes it really easy to talk with a wide array of stakeholders across the company, and  have made it a lot easier to discuss why we're doing what we're doing across the company. Additionally, when the graph vector gets wildly out of order versus the business vector, we can look hard at the graph to try and figure out cleverer paths to get to the value more cheaply.

Additionally, for staffing, I've found found that people tend to find it meaningful to flow through the graph: each project moves naturally into the next project, creating a strong professional growth narrative and helping project teams retain context and mentor new teammates.

More than anything, the model is transparent - we spend a lot more time talking about the inputs and the framework rather than the outputs, yielding much more substantive conversations.

Some limitations of the model that I'd like to fix:
  • Doesn't take into account constellation building and project complexity. I've considered adding a complexity metric to enumerate projects which need a delicate and fragile constellation of team members in place to ensure success.
  • This model doesn't express time value or cost of delay particularly well and is best suited for peacetime rather than a wartime.
  • Most people don't understand it - there's a fundamental tension between accuracy, legibility and simplicity, and I probably could have made it simpler, but I opted towards a more accurate less immediately legible model in order to express the factors I found most critical.

Thursday, January 3, 2019

My favorite books from 2018

This year, questions of authoritarian ideologies, the wider arcs of history, and the pursuit of innovation drove my reading. In that vein, I think that my favorite books of the year reflected those themes. Also, it seems like i need to read more fiction perhaps...

1. Our Kindly Inquisitors
Written in the middle of the culture wars in 1993, this is a must-read for anyone engaging in or struggling with modern identity politics. Even if you disagree fundamentally with parts of this book, you should read it. Ostensively about free speech, the book is probably more appropriately viewed through an epistemic lens, with Rauch viewing epistemology as deeply intertwined with politics. His crisp language cuts deeply at the core of questions that remain relevant to this day: does the identity of a speaker tarnish the validity of that speech? How do we maintain our right to fight against ideas we find repugnant without suppression and censorship? Who has the right to bless speech, and with it, the ideas that we find acceptable in polite society?

2. Deng Xiaoping and the Transformation of Modern China
It's not an exaggeration to claim that Deng Xiaoping was the single most influential person in the 20th century - it might not be right, but it's defensible. Deng had an impact on the scale of FDR, Hitler Churchill, Khrushchev and Kennedy. The difference is, Americans don't know anything about Deng. Anyone looking to understand modern China and "socialism with Chinese characteristics" should read this book, as should anyone trying to make big, sweeping societal changes. While not perfect, Deng is appropriately viewed by many Chinese as the founder of modern china, his leadership took a country that had a lower per-capita GDP than North Korea into the modern economy and began the process of healing from the Cultural Revolution.

3. Wild Swans
As a foil to my flirtation with Deng Xiaoping, Wilds Swans is a memoir that centers on the Cultural Revolution and the atrocities that happened under the Communist Party in the middle of the 20th century. Banned since publication in her native China, Chang's prose tells the story of three generations of women before and during the Communist's rise to power and presents the chilling reality of the Cultural Revolution from the perspective of a young woman growing up in a deeply unstable world. One thing stuck with me from this book: there was no KGB or Gestapo during the Cultural Revolution - in China, it was the entirety of the population that terrorized one another in a gruesome perversion of Marxist ideology.

4. The Idea Factory
If I had to go back in time, I would go back to Bell Labs and apply for a job. This book explains why. Bell Labs was a powerhouse of innovation - it's hard to find an example of modern technology that doesn't trace back to its hallowed halls. Somehow, under the monopoly of 'Ma Bell, a small research lab in New Jersey attracted some of the most talented scientists and engineers in history: nine Nobel Prizes were granted for the work done at Bell Labs. In fact, this year's Nobel Prize was won for research that was done in Bell Labs during the 1970s and 1980s. This book made me think a lot about the fundamentally inegalitarian world of innovation. Were the people at Bell Labs substantively better than anyone else in the world at what they were doing? The answer is an unqualified yes. Together, they were responsible for more innovation than any similarly sized group of people had any right to be. Interestingly, these researchers did not get rich. They were, of course, well off. But they were motivated by research and by discovery, not by money. Can we have such researchers today, in a neoliberal world dominated by high-paying jobs optimizing the existing world? Or was it a unique confluence of circumstances that led this group of humans to invent our modern world?

5. The Lessons of History
Written by Will and Ariel Durant, this is at once an optimistic and tragic story. The premise is ambitious: to summarize the main lessons and themes from the Durant's life's work, their 10-volume, 10,000 page opus "The Story Of Civilization," and remarkably, it succeeds. The book is structured as a collection of short essays, and the fundamental thesis, that we are more similar to our forebears than we might realize and that we have transcended the world of individual Darwinian competition and earned the right to evolve as a civilization rather than as a species is a compelling way to think about our role in history.