Sounds right to me. Do you think it’s something else?

As for programming, maybe you never have scalability problems, but my little photo management database, just a hobby, mind you, has hit the scaling wall twice now, and may hit it again if I get serious about HDRI and my scanning projects. Modern cameras produce an awful lot of pixels and I have all kinds of different work flows and information requirements. If I were actually a member of the photographic trade, I’d surely have to rethink my entire approach, after a bit of reading. My CS degree is from the 70s, so a literature search is often worth while. (P.S. I’m a big believer in trying the simple solution first, but when it bogs down horribly, it’s time for brain power. A good way to get a reputation as a software genius is to have a bag of maybe five or ten techniques on hand …)

CallIng something a trade indicates that in some areas of the skill, the work can be considered somewhat commoditized, while other areas require a very specific niche skill set. It also insinuates that there are various levels of expertise in the trade. Both of these hold true in software development.

A trade also is coupled with various levels of education. I’ve worked with 2 year vocational school graduates and PHDs on the same project. But neither degree indicated their relative success or importance to the project. You know what did? Passion. Passion for their craft. I’ve worked shoulder to shoulder with tradesman. But I’ve always seeked out craftsman for my team. Therein lies the difference, and the pride that comes with mastering a trade.