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
-2000 Lines Of Code An Article by Andy Hertzfeld www.folklore.org Bill Atkinson...who was by far the most important Lisa implementor, thought that lines of code was a silly measure of software productivity. He thought his goal was to write as small and fast a program as possible, and that the lines of code metric only encouraged writing sloppy, bloated, broken code. ...He was just putting the finishing touches on the optimization when it was time to fill out the management form for the first time. When he got to the lines of code part, he thought about it for a second, and then wrote in the number: -2,000. I'm not sure how the managers reacted to that, but I do know that after a couple more weeks, they stopped asking Bill to fill out the form, and he gladly complied. The amount of work not done metricscodemanagementproductivity