Sign In

Taylor Pearson

Principal at Mutiny Fund

Taylor Pearson, Principal at Mutiny Fund

Taylor Pearson is the Principal at Mutiny Fund, a long volatility and tail risk focused hedge fund based in Austin, Texas.1 He has spent the last decade researching and writing about how individuals and institutions can be more resilient in the face of uncertainty.2

Key Points About Taylor Pearson:

  • He is the author of the book "The End of Jobs", which Entrepreneur Magazine called one of the "7 Books Every Entrepreneur Should Read"1
  • His writing has been featured in dozens of media outlets including NBC, Inc, Coindesk, and The Financial Times1
  • He works as a consultant, coach and advisor to small business startups, founders and executives1
  • He has helped clients triple their business, publish bestselling books, launch new product lines and improve their decision-making skills1
  • He is an active speaker, having spoken at institutions ranging from universities like Georgetown to NYU and companies from small VC firms to Fortune 500s1
  • His speaking topics include Decision Making Under Uncertainty, The End of Jobs and Future of Work, and How Markets are Eating the World1

Mutiny Fund, which Taylor oversees, has been designed to act as an "antifragile" or "crisis alpha" investment for accredited investors.1 It aims to achieve large asymmetric gains in times of high volatility or tail risk events.13

When combined with short volatility assets like stocks, bonds, real estate, VC/angel or private equity, Mutiny intends to provide effective diversification, allowing investors to achieve superior returns while reducing drawdowns over a market cycle.1

Taylor lives in Austin, TX and is active on Twitter where he shares useful information related to antifragility, investing, and complex systems.3

Highlights

Feb 9 · twitter

The most interesting thing about Claude Code is the extensibility — small things can easily compound into bigger things you didn't plan.

I started telling Claude Code to write project notes at the end of each work session: What got done, decisions made, open questions, etc.

This is a practice I've had for a long time, just a way to make it easy to pick up where I left off.

It writes the notes itself into a file so I don't even have to write it anymore which is already really nice. (I eventually turned this into a /wrap command I run at the end of every session.)

After a few days I realized: I have project-level notes across everything I'm working on. Those could roll up into a single daily note pretty easily. So I told Claude to summarize the project workbenches into a daily log. Took about two minutes to set up.

Then I started doing my weekly review for the week. I already had seven daily summaries sitting there.

Instead of manually going over my calendar and task list like usual, I made a command that pulls from those and drafts the first version of my weekly review — what got done, what's stuck, what to prioritize next week.

Then I realized: I also have a file with my goals and priorities, and now I have a summary of how I actually spent my week. Why am I manually eyeballing whether those line up?

I told Claude to audit them — compare what I said I'd focus on against what I actually did, and flag the gaps.

The gaps then inform what I need to work on next week. If I decide to reprioritize, I can tell Claude to update my quarterly goals and weekly boals based on the new priorities.

Because it has access to my Google Calendar, it can pretty easily check whether I actually have time for what I'm planning.

You can imagine how you could build more on top of this:

E.g. Send the team weekly update — make a command that takes the weekly review and reformats it for a team audience. Different tone, more context for people who aren't in my head all day. The raw material is already there.

None of these steps were planned in advance. Each was a small, obvious extension of the last primitive.

  • Daily note = summary of project workbenches.
  • Weekly review = summary of daily notes.
  • Goals audit = cross-reference of two files that already existed.

Each piece took a few minutes to set up because the building blocks were already there.

That's the thing that's both impressive hard to convey about these CLI tools — while some single steps are impressive (e.g. the ability to one shot complex software), the more interesting and exciting thing to me is the ways they compound over time.

Feb 6 · twitter

https://t.co/WqQa20e5JS

https://t.co/WqQa20e5JS

Related Questions

What is the main strategy behind Mutiny Fund?
How did Taylor Pearson come up with the concept of Mutiny Fund?
What are some key takeaways from Taylor Pearson's book "The End of Jobs"?
How does Taylor Pearson's approach to investing differ from traditional methods?
What are some notable achievements of Taylor Pearson in his career?
Taylor Pearson
Taylor Pearson, photo 1
Taylor Pearson, photo 2
Add to my network

Experience

Principal at Mutiny Fund since Jan 2019
Product Marketing and Sales Lead at Valet Up (2014-2015), Marketing Manager at Two Tree International (2012-2014)

Education

Bachelor of Arts (B.A.) in History/Spanish from Birmingham-Southern College

Location

Austin, Texas, United States