wwqrd
Joined 8 years ago
Joined 8 years ago
Have since moved to much smaller company, and I think the advice is valid there.
Most software work is just churn / doing the same thing over and over. More productivity can just mean more output, not better output.
I got his satellite clock kit for the office and love it!
If you are implementing a feature for stakeholders on a large piece enterprise software, you don't necessarily have knowledge or understanding of helper tools from earlier work, so that's extra overhead to understand anything non-standard. Then when the stakeholders change direction (as they often do), any assumptions in your code may need to be upheld while implementing the next feature.
Edit: This is also why it's nice to use widely adopted libraries and frameworks for any helper code. That way a new starter has a chance of understanding what's going on.
So really it becomes a balance of maximising volume against sustainable recovery.
How rarely? How does it compare to self driving cars per km driven?