I sat in front of Mat, idly chatting about tech and cuisine. Before now, I had known him mostly for his cooking pictures on Twitter, the kind that made me envious of suburbanites and their 75,000 BTU woks. But now he was the test subject for my new project, to see if it was going to be fruitful or a waste of time. “What’s your job?” “Right now I’m working on microservices for a social media management platform.
I think being associated with trades scares software people because of the negative stigmas assigned to traditional trade work. That shouldn’t set us astray from calling a spade a spade.
Software has been ever consistently marching towards more standardized higher level abstractions. That brings closer to the concept to trade work. Where in the practitioner isn’t necessarily engineering as much as they are applying a process. Computers are still quite hand wavy magic to many people so it’s easy for that to be obscured behind a veil of engineering.
I think the author lends too much to how easily it is to move between the two modes of operation. A very intelligent engineer can design an elegant system of software architecture for practitioners to apply. Not every practitioner can so easily do the opposite.
I think being associated with trades scares software people because of the negative stigmas assigned to traditional trade work. That shouldn’t set us astray from calling a spade a spade.
Software has been ever consistently marching towards more standardized higher level abstractions. That brings closer to the concept to trade work. Where in the practitioner isn’t necessarily engineering as much as they are applying a process. Computers are still quite hand wavy magic to many people so it’s easy for that to be obscured behind a veil of engineering.
I think the author lends too much to how easily it is to move between the two modes of operation. A very intelligent engineer can design an elegant system of software architecture for practitioners to apply. Not every practitioner can so easily do the opposite.