Currently developing futuristic smart-device, IoT connected, highway construction site safety system in EU.
Used to work on infrastructure, application architecture and cloud engineering.
Being good at many things and excellent in few made myself always just troubles in my life.
Once they realize you can do other stuff as well - over some time expect them to give you tasks totally unrelated to the position you were originally hired for.
A bonus is, if you get tasks from multiple managers ignoring the others, thinking you are capable of working 200% or 300% on all tasks from all areas because their tasks have higher priority then the other's. And then comes the CEO directly ignoring all resource planning and orders you to have a look at this until the end of the week...
The only exception is Germans. They do not tolerate you doing someone else's job even if you're probably better at it.
Another thing I would like to share is:
You don't need to be excellent. You need to be good + you need to know how and where to look for information that make you look excellent.
I am excellent in some areas but that's just because I have spent many years planning, assembling, installing, configuring, running, patching, maintaning and debugging these systems so I came across all possible configuration corner cases and weird bugs that happened during the lifecycle of that system (I am developing for, deploying and DBA-ing MSSQL Server since MSSQL 2000 until today including MSSQL 2017 on Linux in Docker).
I feel I'm an expert in this area but nobody ever cared in any of my jobs. They were always looking for ordinary DBA. In case there is a weird problem or situation - they unknowingly rely on product support, shared company knowledge and Google.
And that's exactly how it is.
I am managing tens of Exchange Servers. I'm in no means an Exchange specialist. When there is an Exchange problem I know that I need to consult Microsoft documentation, Look at available Exchange Powershell commands, search Experts Exchange eventually craft a advanced Google search query to find a blog decribing a solution to my problem in 2-3 clicks.
And it just works. I'm being treated and percieved as an Exchange specialist.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have to say:
Being good at many things and excellent in few made myself always just troubles in my life.
Once they realize you can do other stuff as well - over some time expect them to give you tasks totally unrelated to the position you were originally hired for.
A bonus is, if you get tasks from multiple managers ignoring the others, thinking you are capable of working 200% or 300% on all tasks from all areas because their tasks have higher priority then the other's. And then comes the CEO directly ignoring all resource planning and orders you to have a look at this until the end of the week...
The only exception is Germans. They do not tolerate you doing someone else's job even if you're probably better at it.
Another thing I would like to share is:
You don't need to be excellent. You need to be good + you need to know how and where to look for information that make you look excellent.
I am excellent in some areas but that's just because I have spent many years planning, assembling, installing, configuring, running, patching, maintaning and debugging these systems so I came across all possible configuration corner cases and weird bugs that happened during the lifecycle of that system (I am developing for, deploying and DBA-ing MSSQL Server since MSSQL 2000 until today including MSSQL 2017 on Linux in Docker).
I feel I'm an expert in this area but nobody ever cared in any of my jobs. They were always looking for ordinary DBA. In case there is a weird problem or situation - they unknowingly rely on product support, shared company knowledge and Google.
And that's exactly how it is.
I am managing tens of Exchange Servers. I'm in no means an Exchange specialist. When there is an Exchange problem I know that I need to consult Microsoft documentation, Look at available Exchange Powershell commands, search Experts Exchange eventually craft a advanced Google search query to find a blog decribing a solution to my problem in 2-3 clicks.
And it just works. I'm being treated and percieved as an Exchange specialist.