No, what you mention are themselves just technologies, not domains.
Engineering is just a collection of technologies; finance is technology
(insofar as it is mathematically-based); health is nothing without
technology these days; same with education, aeronautics, etc, etc.
No. You're missing the point. Unless you've got an artificially broad
definition of technology, the domains I refer to are real-world
processes, problems, solutions, procedures, techniques etc. Domains are
real-world environments that are a mishmash of science, engineering,
technology, human knowledge, human emotion, community conventions and
mores and standards, conventional wisdom, habits and entrenched interests.
A business or application domain (_you_ might want to read up on domain
driven design to understand what a domain is) is what you are trying to
model in your software. While some of the existing processes that you
are modeling may use technology, those processes themselves are *not*
technologies.
I can also assure you of one incontrovertible fact: it's not possible
for a programmer to think the way you do unless they have never moved
away from tools and toy apps.
AHS