3 ms·
Only 36, but - Working longer hours is counter-productive, it reduces output. And having a lot of experience means being able to come up with a better way to d
by itamarst 10y ago
Only 36, but -
Working longer hours is counter-productive, it reduces output. And having a lot of experience means being able to come up with a better way to do things, which typically saves time.
So, I work for companies that don't confuse hours worked with output.
- AnimalMuppet 10y agoExactly. With experience, I'm more productive without working harder. It's not that I write more lines of code, either. It's that I make fewer false starts, so I have to throw less away. I make fewer bad architectural decisions, so I have to write less code. I use libraries better, so I have to write less code. I write fewer bugs, so I have to spend less time trying to find and fix them. I make less of a mess out of the code, so I can read and understand it again more quickly later.
- watwut 10y agoI have made the same observation. Long hours for too long and people start to make less smart decisions and meeting somehow take longer. I assume it is because all that socialization and chatting people need creeps into meetings. Less smart decisions means more chaos, no prioritisation and more late night bug fixing leading to the cycle. Work for company that values output more then worked hours. But also, find workplace that needs the experience - e.g. place that needs people working more independently or figure out less known technologies or needs them to communicate with customers or has big more complicated projects or something like that.
- voycey 10y agoYep, can't agree with this more!