IT is an administrative function and is really part of operations.
Software development is generally a creative position and is a profit center. If you work somewhere where you develop internal apps, you may have a different perspective.
Infrastructure maintenance is management, security and day to day business, while software engineering is mostly concerned with itself. They use distinct tools and generally have nothing to do with each other (except maybe integration).
We need new terms, IT means “works with computers, but more than Word and Excel” for too many people. In Switzerland they split the apprenticeship names to ‘platform engineer’ and ‘application engineer’, which I think is fitting.
Drivers would be end users, Clients and project managers sometimes.
Think about it. Many drivers don’t know about checking the oil, maintaining proper tire pressure, tire wear, brake wear, air filters or topping off fluids.
I can do all of the above, but I’m nowhere near a mechanic. Just car savvy. So I could make suggestions to mechanics or engineers that look cool but are insane for functionality.
My current workplace organizes both development and infrastructure within IT which itself is a sub department of finance. I’m not saying this is the best approach because honestly it only took 1.5 layers of apathetic management to make long term planning a nonstarter
How is software not a subset of IT?
IT is an administrative function and is really part of operations.
Software development is generally a creative position and is a profit center. If you work somewhere where you develop internal apps, you may have a different perspective.
Infrastructure maintenance is management, security and day to day business, while software engineering is mostly concerned with itself. They use distinct tools and generally have nothing to do with each other (except maybe integration).
We need new terms, IT means “works with computers, but more than Word and Excel” for too many people. In Switzerland they split the apprenticeship names to ‘platform engineer’ and ‘application engineer’, which I think is fitting.
Well yeah, it’d be like if an advertising copy writer said their job was “English”.
Think of it like an engine: The mechanics working on the engine aren’t the engineers designing the thing.
Honest question: what do we call who is driving the engine?
A user
Drivers would be end users, Clients and project managers sometimes.
Think about it. Many drivers don’t know about checking the oil, maintaining proper tire pressure, tire wear, brake wear, air filters or topping off fluids.
I can do all of the above, but I’m nowhere near a mechanic. Just car savvy. So I could make suggestions to mechanics or engineers that look cool but are insane for functionality.
My current workplace organizes both development and infrastructure within IT which itself is a sub department of finance. I’m not saying this is the best approach because honestly it only took 1.5 layers of apathetic management to make long term planning a nonstarter