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
What happens to user experience in a minimum viable product? An Article by Ryan Singer signalvnoise.com "Feature complexity is like surface area and quality of execution is like height. I want a base level of quality execution across all features. Whenever I commit to building or expanding a feature, I'm committing to a baseline of effort on the user experience." There’s a distinction to make: The set of features you choose to build is one thing. The level you choose to execute at is another. You can decide whether or not to include a feature like ‘reset password’. But if you decide to do it, you should live up to a basic standard of execution on the experience side. Features can be different sizes with more or less complexity, but quality of experience should be constant across all features. That constant quality of experience is what gives your customers trust. It demonstrates to them that whatever you build, you build well. Minimum Awesome Product qualityproductsfeaturesux