Developer productivity: The art of saying no
This post is almost comically ridiculous if you try and apply any of it outside of the context of (I imagine) a small team that doesn't really do anything externally.<p>How do I tell my clients that I only do meetings on Thursdays?  If they happen to be unavailable one Thursday, do they have to wait a fortnight before I deign to speak to them again?<p>Is this guy seriously suggesting that the way to stop being overwhelmed by inbox zero is by using Slack?<p>And honestly, doing one thing a day - really?  How in the world does that work?  Sure, doing one thing well is better than doing nothing or half-doing a bunch of things, but surely your goal should be actually doing a reasonable amount of things that reflect a solid day's work - and figuring out a strategy for reliably making that happen.<p>Perhaps I'm just a grouch today, but it feels like this post is either satire or written from a completely different universe, utterly unrelated to the one I inhabit and work in.