SEBASTIAN MARSHALL

Strategy Philosophy Self-Discipline Science Victory

hide

Read Next

Why I'm Not Writing A Post Bashing The Anonymous Troll

Act I: The Discovery of Conflict Invigoration

I recently discovered a phenomenon common among many highly successful people. I'm calling it "conflict invigoration" - this is a personality trait, a mixed blessing and curse. It's the kind of person who can move heaven and earth when inspired, but doesn't do as well when they aren't... and who is always invigorated by a fight.

I first noticed conflict invigoration among a number of the most successful people I knew personally. See, I don't think this is an entirely new observation, but a lot of the people that reach stratospheric levels of success are kind of deranged. You almost have to be, to keep going after you've "won" by every conceivable measure, to work yourself to the bone at the expense of your sanity and longevity and vitality, to neglect so many of the basic human needs and pleasures and comforts.

I saw this trait in lots of successful people, and then I started paying attention to biographies and histories. Indeed, many of the most expansive people in our generation and previous ones are conflict invigorated - they've perhaps always got a baseline of creativity and striving, but it really comes out when a fight breaks out.

"Competition is always a fantastic thing, and the computer industry is intensely competitive." - Bill Gates

Guest Post: Shanna Mann on Systems

After a comment I made about my documentation binder in a previous post, Sebastian asked me to share my own system with you all.

Be regular and orderly in your life so you may be violent and original in your work. ~ Gustave Flaubert

My organizational premise is this-- if your recurring tasks are fully optimized and automated, you have more RAM to devote to novel tasks and projects.

Novel projects should be well documented. If they become routine, it's an easy starting point from which to optimize. If they don't, they may still be useful in the future. This is especially important because optimized systems experience entropy, and needs regular overhauling, which is actually what I was doing when SM asked me to expand on my system.

I like to overhaul about twice a year, but in practice, I overhaul when the drag of changing circumstances has aggravated me to the point where I either have to overhaul my system or abandon it. I don't find that “fixing as you go” is a viable strategy. Tweaks are fine, but there comes a time when you have to tear down and start anew, and you'll never get away from that.

Guest hasn't filled out their bio yet.
Guest
0
Vote
Advanced options  
, at :
Close