4 ms·
For years I've held the belief that my job (software developer/whatever) is to do as little as possible but it's mostly been met with bewilderment and disdain f
by beaker52 10y ago
For years I've held the belief that my job (software developer/whatever) is to do as little as possible but it's mostly been met with bewilderment and disdain from most people I've offered it to.
- bsmith 10y agoThis applies to an even greater extent in a highly resource-constrained environment (such as my startup). My job is as much about what I choose NOT to do as it is about what I actually decide to take on; as .5 of only 1.5 software engineers at my workplace, the lion's share of my role relies on me placing the correct bets on what features (or automation workflows) to implement.
- mrweasel 10y agoSadly people often see it as obstruction or laziness, when you point out the possibility that they, and by extension you, might be better of without some feature. The issues I most often face is explaining the running cost, be it due to complexity or hardware requirements. Some potential or minimal income always seems to trump long term savings. Another is "the customers expect us to have XYZ feature", regardless that you can prove that only a limited number of them actually use it. Far less than required to cover the running cost.