TFA isn't about a productivity metric, it's about establishing a habit. Everyone from Jerry Seinfeld to Anne Lamott to Pablo Picasso extoll the virtue of making a habit of doing some work--even sometimes crappy or merely symbolic work--every day. ("Inspiration exists, but it has to find us working")
But that said, it's not as if doing something every day is totally uncorrelated to productivity. Sure, it's a proxy metric at most, but doing something is eventually a prerequisite to productivity.
But then again, maybe I'm a "clueless manager" type because I'd also argue that test-coverage isn't totally unrelated to quality. It's also a proxy metric and one that's relatively easy to game, but come on, is there anything in software development you find measurable?
TFA isn't about a productivity metric, it's about establishing a habit. Everyone from Jerry Seinfeld to Anne Lamott to Pablo Picasso extoll the virtue of making a habit of doing some work--even sometimes crappy or merely symbolic work--every day. ("Inspiration exists, but it has to find us working")
But that said, it's not as if doing something every day is totally uncorrelated to productivity. Sure, it's a proxy metric at most, but doing something is eventually a prerequisite to productivity.
But then again, maybe I'm a "clueless manager" type because I'd also argue that test-coverage isn't totally unrelated to quality. It's also a proxy metric and one that's relatively easy to game, but come on, is there anything in software development you find measurable?