I'm sure the complexity, depth, and expected maintenance of some bridges vary too.
Basic static site seems like drafting. A CRUD app or WordPress site or similar between drafting and technician.
There is a continuum between people who author crud apps and people who author compilers, but you can go from one to the other simply by having industry experience and access to good books.
And physics engines and distributed databases and creating Wireguard is software engineering.
I think there are hundreds of times more people doing the former, than the later
Yes, and that's correct. If your skills go as far as building a 1-meter tall wall around a patio you are not an engineer.
I've seen a startup where the front-end is a very simple web-site (just some basic forms, charts and tables). But the team follows all the clean-code, TDD, unit test and whatever latest buzzword you can think of. It takes one front end developer to sort a list alphabetically more than a day, which probably takes a decent developer less than 10 minutes to finish. IMO, the whole clean-code seminars/books industrial complex if responsbile for the amount of time, effort and money wasted following these clean code trends without any real business value.
- people who write basic static sties
- people who write wordpress sites
- people who write simple CRUD apps
- people who write hardware drivers
- people who write compilers
- people who write databases
- people who write google-scale distributed systems
- people who write graphics engines
- people who write physics simulation systems
- people who write video games
The complexity, depth of abstractions, and expected maintenance lifetimes of these tasks vary wildly, but because we all write source code we're all counted as doing the same job! Sort of an obvious lunacy, different mistakes will punish each of these jobs differently than others.