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
Don't Rush to Simplicity An Article by Shawn Wang www.swyx.io You've probably heard this story before: A businessman finds a fisherman, who is living an idyllic, peaceful life by the sea. He laughs and tells the fisherman how to get rich instead. The fisherman asks him what he will do after he gets rich. He replies that he would retire to an idyllic, peaceful life by the sea. There's supposed to be a deep life lesson in there, but it's always felt insincere to me. To me it is better to have reached the heights of a career, or suffered an epic defeat, even if I do end up in the same place as everyone else in the end. To me simplicity is made more beautiful when understood through a long personal struggle with complexity. When I can dance with it, having turned a mighty nemesis into an old friend, and teach others to do the same. Better to have loved and lost, than never to have loved at all. On the other side of complexityMountains are mountains zensimplicity