It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
Your teacher may have used "engineer" to mean what I'd call an "architect", which is a role less focused on daily coding (although I personally have a foot in both camps, and would argue that we deserve to maintain the systems we design -- keeps us humble). Many other people and companies use "engineer" synonymously with "developer".
There are no standards and we're all making it up as we go along.
Your teacher may have used "engineer" to mean what I'd call an "architect", which is a role less focused on daily coding (although I personally have a foot in both camps, and would argue that we deserve to maintain the systems we design -- keeps us humble). Many other people and companies use "engineer" synonymously with "developer".
There are no standards and we're all making it up as we go along.
Naming mixup aside, I definitely agree with this:
And I think the world feels more this way than it used to.