Things Learned Blogging An Article by Jim Nielsen blog.jim-nielsen.com Eschew anything beyond writing the content of a post. No art direction. No social media imagery. No comments. No webmentions. No analytics...Imagine stripping away everything in the way of writing until the only thing staring you back in the face is a blinking cursor and an empty text file. That’ll force you to think about writing. ...[And] write for you, not for others. And if you can’t think of what to “write”, document something for yourself and call it writing. If there’s one thing I’ve learned about the mystery of blogging, it’s that the stuff you think nobody will read ends up with way more reach than anything you write thinking it will be popular. So write about what you want, not what you think others want, and the words will spill out. How to blogWrite the books you want to read bloggingwritinginterest
So that you can get feedback on it and make it better Fascinatingly, one of the other big complaints people had about agile is no iteration. I don't understand how being in an agile environment makes people less iterative, but somehow that seems to be the case. And I think it's because people misunderstand and think that agile is just about putting features out faster, and not about the important part, which is getting something in front of users faster so that you can get feedback on it and make it better. Laura Klein & Kate Rutter, Problems With Agile UX The most rewarding iterationsTo anticipate all the uses and abuses agileiteration