However, if a company has gimpy organization and technical APIs for many complex pieces of software and or processes in which making mistakes is costly and expensive, it is economical to raise someones salary $15k than have to invest in a newb to spend the next 7 months being able to operate as quickly as you do. It took me about 7months to be up and running efficiently with everything and be able to train other people. I still had to perform at full capacity on day one, but I was less efficient and because mistakes were so costly, I would have to wait 30-45minutes to find someone else to confirm an operation before making one, instead of making a mistake in production, until I knew how to do it myself.
In the manufactoring line, bottlenecks for tools being down was calculated by the millions per hour, because linear bottlenecks in product production actually cascade down a 4 months timeline for meeting product deadlines, which have payment associated with them, and significant penalties for being late.
Additionally, metrology tools to check errors sometimes cannot, based on chemistry and physics, detect errors in production until multiple steps down the line. So if there is a mistake in a base design, it won't get picked up for 3 weeks, and the entire line has to be restarted, so it really helps to have people know how to not screw up even if there isn't an official process for it.
They kept me on because I worked hard, and because I knew how to use over 18 different independent horrible pieces of software with no APIs, and run them simultaneously in realtime in production while operating a team of 15 people.
However, if a company has gimpy organization and technical APIs for many complex pieces of software and or processes in which making mistakes is costly and expensive, it is economical to raise someones salary $15k than have to invest in a newb to spend the next 7 months being able to operate as quickly as you do. It took me about 7months to be up and running efficiently with everything and be able to train other people. I still had to perform at full capacity on day one, but I was less efficient and because mistakes were so costly, I would have to wait 30-45minutes to find someone else to confirm an operation before making one, instead of making a mistake in production, until I knew how to do it myself.
In the manufactoring line, bottlenecks for tools being down was calculated by the millions per hour, because linear bottlenecks in product production actually cascade down a 4 months timeline for meeting product deadlines, which have payment associated with them, and significant penalties for being late.
Additionally, metrology tools to check errors sometimes cannot, based on chemistry and physics, detect errors in production until multiple steps down the line. So if there is a mistake in a base design, it won't get picked up for 3 weeks, and the entire line has to be restarted, so it really helps to have people know how to not screw up even if there isn't an official process for it.
They kept me on because I worked hard, and because I knew how to use over 18 different independent horrible pieces of software with no APIs, and run them simultaneously in realtime in production while operating a team of 15 people.
Losing me was uneconomical for them.