9 hours ago, Fulcrum.013 said:
May be it language issue, but on slavic languages anything of it called engeenering. By other world anything related to any tech (not machinery or construction only) or ever chemistry and economy, that require to find way how to solve tasks and prove it solution by calculations/mathematical theories doing by persons that have qualification engeener of related field. For eхample engeeneer-programmer, engeneer-builder, engeneer-economist or ever engeneer-mathemathic and so on.
In English - or at least, in Canadian English - "engineering" and "tech" are different things, even though some tech workers are sometimes called "engineers." Colloquially, "tech" usually refers to software or information technology. "Engineering" refers to things like designing bridges and machines. Where I went to school there was a degree program called "software engineering", but it was just a specialization of computer science, which was a department in the faculty of science. "Software engineers" who go through that degree program cannot become certified professional engineers because "software engineering" is not actually recognized as "engineering" by the organizations that license engineers. Some schools even put computer science under the faculty of mathematics, not science!
A true "engineer" to a Canadian is someone who wears the Iron Ring - someone who has learned the ethics of engineering and gone through a ritual where they swear an sort of "engineer's oath" to uphold that code of ethics and can be held accountable by the public for mistakes (which is NOT true of the vast majority of software developers!). Typically when I think of engineering, I think of fields like mechanical engineering, where there is a lot of emphasis on rigorous mathematical design of physical things. Such engineers do write software - and there are "computer engineers" - but they tend to approach software problems with the mindset that the code itself is only incidental to the real problem, which is almost always control of a piece of hardware. Computer scientists and "software engineers" typically have the opposite. Most of our problems involve software as the primary thing we are building - how it is structured and how it interacts with other software and even whether the customer is happy with how it looks on the screen. How we are going to deal with (inevitable) requirements changes a month before ship - or three years after shipping our software...
Since my undergrad was in computer science, I didn't go through the Ritual of the Calling of an Engineer, I don't wear the Iron Ring, and I am actually not allowed to call myself a "professional engineer." Nonetheless, my job title is "software engineer", which is a term I try to avoid applying to myself because it arguably dilutes the meaning of the word "engineer".