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
Software Engineering as a Craft An Article by Thomas Wilson thomaswilson.xyz The decreasingly tangible product of code, i.e. that all we have are files on a hard-drive, may make it easy to forget that writing software produces a thing. If you produce a wonky chair or an overly long fork, it’s easy to see the quality of work was not great. By calling for a perception of software as a craft, we fight against that ability to forget or not notice the final quality of the product. You could watch two software engineers with different levels of experience, or in different domains, and it wouldn’t necessarily be so easy to guess which is which, at least from a distance. So maybe there is something to be said for the value of software as a craft, for sometimes focusing on the practice of making better, or at least different, software just for the sake of it. craftsoftware