[giltleaf]

I essentially used the 4 hour workweek script and am somewhere in the middle of that timeline, setting up my business now. 1. Figured out how to get all of my work done super fast 2. Started taking days off and working remotely using my above efficiency skills to put more and more time into my side project while still meeting all of my deadlines and obligations 3. Negotiated a remote and part time contract that only has me in the office 3 days a week. 4. Grind.

I'm still in the setup phase of my business (a hydroponics farm/green wall installations) but being able to devote entire days to getting going has been immensely helpful.

I started working the new contract about a month and a half ago. It was hard staying focused at first and I was a little too happy - go - lucky with my newfound freedom (Overwatch). So, while I was getting everything done for my 9-5, I've been moving slowly on the farm. Things have been better these past two weeks and I'm excited to get cranking in a serious way.

I should note that before I had even considered building a business or taking this step, I'd been doing research for the past 4 or so years that started my last semester in undergrad. I'd also done many small scale, non commercial projects for different clients in the evenings/weekends before I made the jump. Like another poster, to me, this is the equivalent to grad school. I could spend a bunch of money on an MBA and learn some things, or I could start this business, learn hands on, and potentially walk away with profit instead of debt.

[jventura]

>> 1. Figured out how to get all of my work done super fast

I always assumed that, as developers, we couldn't afford to automate writing code (as Tim's proposition is originally to automate the income), and so you do your work faster. Can you comment how you do that, how did you buy your remote time from that, etc.?

[giltleaf]

I'm not a developer, I'm a researcher. However, a big take away from the book for me that I'd imagine would apply to developers as well was not answering emails or going to meetings. He get's into how to do this politely and gradually, and it's definitely saved me time.

The gist of it is, generally, no matter how huffy the person at the other end is, what they're sending you is probably not an emergency. That being said, you can afford to batch your emails so you are only going through and responding to them once or twice a day as opposed to constantly losing your train of thought to reply to them or read them. This might not exactly apply to you, but reading 4hww got me to consciously think what sorts of things I might be able to cut. Actually taking the time to notice what those things are could help anybody I'd guess.

I got my remote time from that because I've been working at the same org for 2 years and have kept track of my wins/successes. I've gotten a lot of those because I've learned to be more efficient using ideas like the ones above. Over those two years, I've also noticed that our org has a problem retaining mid level employees and so I was able to leverage that when talking about remote time as well.

So I'm not automating my income, but I am saving time by cutting unnecessary tasks.