I think software engineering is a unique case because on the one hand actually writing code isn't the "real work"; the real work is the thought and design that

I think software engineering is a unique case because on the one hand actually writing code isn't the "real work"; the real work is the thought and design that comes before writing the code. On the other hand, even after you've performed the "real work" of thinking things through, the fact that your code works isn't the "real product". The real product is the degree to which the code can be understood, maintained, and extended. I think that the idea that software engineering is a trade skill produces two problems: It encourages management to discount software engineers' expertise and view the planning that comes before writing code as a waste of time. I think when people today say "trade skill" they think of things like factory work and relatively routine construction. However, a programmer is more like a traditional artisan who must always be honing their craft and learning new techniques. In my opinion, a better way of looking at it is that companies should start actually treating software engineers like engineers. I.e. by viewing them as professionals with the expertise to inform project planning and a professional obligation to follow best practices and design.