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
Ambitions for someone else's mind "One of the first things I learned about teaching is that you have to respond to each student individually. You don't start with any idea of what they should be doing, who they're supposed to be, or what their performance level is, and you don't compare them to one another. You simply start with each one of them wherever they are and develop the process from there. "...I would think that the most immoral thing one can do is have ambitions for someone else's mind." Lawrence Wechler & Robert Irwin, Seeing Is Forgetting the Name of the Thing One Sees Student's future, not teacher's pastI can only conceive for you teaching