[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.