4 ms·
Is eliminating jobs an unintended consequence, or is it the fundamental purpose of software development? Personally, I see job elimination as my goal and my pu
by welshwelsh 3y ago
Is eliminating jobs an unintended consequence, or is it the fundamental purpose of software development?
Personally, I see job elimination as my goal and my purpose as a developer. Whenever my company is able to lay people off as a result of my work, that means I am doing a good job. I always try to keep track of how many people my software can replace and how much my company pays these people, so that I can take credit for these cost savings and claim a portion of their salaries for myself during salary negotiations.
- kevingadd 3y agoFor tools programmers at least, generally the work you do is meant to enable the work other people at the company do - they aren't able to do it without you. Eliminating their jobs entirely is a different matter, even if that can also be done by a tools programmer. For creative tasks like game development the applications for full automation are usually narrower, so you're typically doing 'force multiplier' sort of stuff, like creating powerful macros or error checkers etc. Hammers and nails don't eliminate carpenters. Most of what I did at that job was building a syntax highlighting editor w/autocomplete for game scripts, making builds faster, etc. Instead of eliminating jobs that mostly let us ship the same product faster.