Hacking Capitalism: Modeling, Humans, Computers, and Money.
Rate it:
Kindle Notes & Highlights
Read between September 6 - September 6, 2023
57%
Flag icon
your ability to build efficient systems is how you’ll outperform them.
57%
Flag icon
While an initial working prototype might satisfy the definition of success, it’ll likely be offensively inefficient.
57%
Flag icon
You can then introduce small changes to the system. If you built the system well, it should be easy for you to demonstrate success or failure after each small change. Keeping the success cycle small lets you make dramatic changes over time.
57%
Flag icon
In the same way that a definition of success lets you quickly check whether your system is working, a definition of efficiency can let you quickly check whether your system is as efficient as you need it to be.
Gareth
Performance budgeting
57%
Flag icon
Definition of Efficiency is a simple way of determining if a system is working as well as it needs to be.
57%
Flag icon
You will need to be efficient in your career, and with your relationships with people.
57%
Flag icon
A good builder should be able to advance both their reputation and their system’s purpose.
58%
Flag icon
As an engineer, you should find excitement and joy in collecting an endless list
58%
Flag icon
Every problem in the tech industry is a vastly underestimated exploitation opportunity with an enormous attack surface!
58%
Flag icon
In the eyes of a tech corporation, architects apply technology to the capital to advance product development.
58%
Flag icon
Architects and builders can use labeling to think about systems and later components. Once someone creates a label, people can understand what it means. You can focus more time on the labeled components than on defining what a component might do.
59%
Flag icon
The easier a system to observe, the easier it is to operate. The easier it is to operate, the higher value the system can generate. Thus, higher revenue.
59%
Flag icon
An ability to easily change the internal state of a system is its operability.
60%
Flag icon
Over time, the markets have shown that having a common interface creates micromarkets that can operate with a product interchangeably.
61%
Flag icon
The takeaway with the Bay Area bridges is that if you want to support elaborate projects such as the beautiful and famous Golden Gate Bridge, you must first start with the simple, economic, and less impressive functional work.
61%
Flag icon
Build the boring bridges first.
61%
Flag icon
Likewise, your projects should follow the same pattern. Whether you’re designing distributed systems, a monolithic software repository, or managing a complex structure of people, you’ll need to add support for commerce first. Supporting commerce can be unattractive, but it’s necessary.
61%
Flag icon
Do the unattractive work first as a gift to your future self and future architects.
61%
Flag icon
Remember, successful projects and platforms grow like cities. Organically. Start simple and enable commerce first and foremost.
62%
Flag icon
Some systems will need to move fast and inspire innovation, such as Tesla. These systems are hungry for profit and their design should reflect this.
Gareth
How should,design reflect this for Corral?
63%
Flag icon
Building and applying systems lets good builders do more effective work with the same or fewer resources. This, unfortunately, is one of the few ways that you can progress toward the elite in capitalism.
63%
Flag icon
The building process supports small iterative changes. With capitalism, your ability to turn limited resources into efficient machinery can be a compelling tactic.
63%
Flag icon
Your ability to design more efficient systems will come from your experience with observability, measurability, and operability.
63%
Flag icon
So if you can uncover new resources, that can free up time and energy that you can dedicate to accelerating toward the elite.
63%
Flag icon
Breaking lets you introduce resources that wouldn’t otherwise exist. I often look at breaking as a way of rolling the dice for resources.
63%
Flag icon
To break a system, you must first see the system in its many forms.
63%
Flag icon
Breaking can show you where a system will end up. Breaking increases resiliency. The more that you break a system, the more you can repair the system and prevent it from breaking.
64%
Flag icon
Many architects neglect to consider that systems exist in a perpetual state of brokenness.
64%
Flag icon
You can apply breaking’s constructs to the tech industry by observing how the elite respond to breaking. Breaking will expose new resources, new functionality, and new opportunities to you. Where there’s carnage, there’s opportunity.
64%
Flag icon
As systems break down new opportunities present themselves.
64%
Flag icon
For example—and perhaps counterintuitively—forests need to periodically burn to achieve sustainability.
65%
Flag icon
Fuzzing is the act of trying to break a system by providing invalid, unexpected, or overwhelming inputs to the system.
65%
Flag icon
Destruction of Service is rendering a system inoperable by causing the maximum amount of long-lasting damage.
65%
Flag icon
Market Disruption is the process of introducing economic innovation to a market by disrupting the current norms.
65%
Flag icon
Where there’s market disruption, there’s room for growth. Where there’s systems destruction, there’s opportunity to exploit others. Where there’s chaos in an organization, there’s space for influence.
65%
Flag icon
Breaking is a viable way of instilling innovation in a system.
65%
Flag icon
An astonishing amount of groundbreaking change comes about during emergencies
65%
Flag icon
These disasters break social structures and create opportunities.
65%
Flag icon
These reorganizations of human resources can be frustrating to employees because the reorg’s debris can cause unexpected changes in employees' working experiences.
65%
Flag icon
Take careful and detailed notes of newly forming systems. Observe these systems in their raw forms while they come to life. Exploit any vulnerabilities as soon as you detect them.
66%
Flag icon
If your goal is to earn more money, you might structure the chaos toward your expertise.
66%
Flag icon
If your goal is to earn a higher title, you might structure the chaos toward your ability to delegate and influence others.
66%
Flag icon
If your goals are to do as little labor as possible and to preserve your mental health, you may want to take the chance to offlo...
This highlight has been truncated due to consecutive passage length restrictions.
66%
Flag icon
It’s easy to exploit a system at the expense of others. It’s tolerable to exploit a system with no impact to others. It’s skillful to exploit a system and elevate others in the process.
66%
Flag icon
Madness is widespread in the tech industry. Startups repeat the same product ideas, business models, and market strategies over and over while continuing to fail. But from one effort’s debris can come another effort’s foundation.
66%
Flag icon
Remove yourself from the path of destruction in a madness cycle. Position yourself near the path of productivity in a madness cycle.
Gareth
Trend of maximizing productive path in these books
67%
Flag icon
It is possible to identify voids in the organizational structure and adopt a posture of "gap filling" temporarily.
67%
Flag icon
This can be done much more effectively during the chaos of a breaking cycle, than during the st...
This highlight has been truncated due to consecutive passage length restrictions.
67%
Flag icon
Organizations, companies, and even teams are subject to panicking when things suddenly break. During this panic, rules, behaviors, constraints, and system boundaries are often overlooked.
68%
Flag icon
Breaking a system can offer tremendous value—whether that system may be economic, societal, or technical. And breaking is fundamental to success in capitalism because breaking exposes new opportunities and resources that wouldn’t otherwise be available. Without breaking, you lose vital opportunities to gain a competitive edge.