Reading the headline I thought you were going to touch on a more software engineering angle:
Many good engineering practices could be described as "working ourselves out of a job". We might keep ourselves busy doing repetitive ops tasks, but good engineers will look for ways of automating such things. We might keep ourselves busy doing a lot of repetitive copying & pasting of boilerplate code, but good engineers look for abstractions and follow the DRY principle. We might keep ourselves busy maintaining spaghetti code, but good engineers will try to write clean code, and spend time refactoring. We might keep ourselves busy explaining to developers how our codebase works, but good engineers will have some sort of documentation. "Working ourselves out of a job", except it's really just keeping ourselves in a more interesting job, where we're being passionate, inventive and always learning.
On the other hand... we might keep ourselves busy endlessly reading up on and following all of the advice and "best practices" to the tee, learning new technologies on the bleeding edge to see if they make our jobs easier, etc, but good engineers will pragmatically pick and choose advice to follow and practices/technologies to adopt.
"working ourselves out of a job" by exploring things which make the job easier ....but also maybe just getting on with it :-)
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.
Reading the headline I thought you were going to touch on a more software engineering angle:
Many good engineering practices could be described as "working ourselves out of a job". We might keep ourselves busy doing repetitive ops tasks, but good engineers will look for ways of automating such things. We might keep ourselves busy doing a lot of repetitive copying & pasting of boilerplate code, but good engineers look for abstractions and follow the DRY principle. We might keep ourselves busy maintaining spaghetti code, but good engineers will try to write clean code, and spend time refactoring. We might keep ourselves busy explaining to developers how our codebase works, but good engineers will have some sort of documentation. "Working ourselves out of a job", except it's really just keeping ourselves in a more interesting job, where we're being passionate, inventive and always learning.
On the other hand... we might keep ourselves busy endlessly reading up on and following all of the advice and "best practices" to the tee, learning new technologies on the bleeding edge to see if they make our jobs easier, etc, but good engineers will pragmatically pick and choose advice to follow and practices/technologies to adopt.
"working ourselves out of a job" by exploring things which make the job easier ....but also maybe just getting on with it :-)