I mean, it's more like "woodworker" vs "carpenter." We don't ask people framing houses to plane their own wood. Most practitioners in our industry don't apply much fundamental CS knowledge.
After graduating most CS grads seem to forget foundational CS stuff anyways.
I never got a CS degree. So I trained myself. While working and also a lot of a year when I was unemployed during the .com crash.
Which only made me more frustrated to find that most jobs are just "you nail these two boards together" and most programmers are clueless about things like what the "relation" in "relational DBMS" means.
In construction - in the UK - there are first and second fix "chippies". First fix do the big stuff and second fix do everything after the plaster is dry(ish).
There are also cabinet makers and furniture makers, turners and several more wood related trades. Here, woodworker is a synonym for carpenter and carpenter is rarely used as a job title. Generally a specialisation is used.
I happen to own an IT firm and I prefer to see engineering qualifications on CVs (resumes). I'm a rather shabby Civ. Eng myself! I graduated just before the shit hit the fan in the UK in 1991 - recession, >10% unemployment (in Devon and Cornwall) etc. Can't recall what inflation was up to at the time but I think it was worse than now.
After graduating most CS grads seem to forget foundational CS stuff anyways.
I never got a CS degree. So I trained myself. While working and also a lot of a year when I was unemployed during the .com crash.
Which only made me more frustrated to find that most jobs are just "you nail these two boards together" and most programmers are clueless about things like what the "relation" in "relational DBMS" means.