Re:Improving my productivity as a working programmer (2017)
by MaxBarraclough on Saturday February 08, 2020 @07:32AM
(#22275416)
> It would just make me more worn down and exhausted when I leave the office
Only if you're working harder. Generally when people talk about productivity-boosts they mean working smarter. That may mean stopping doing things that are just making things needlessly difficult.
The example in the article is a good one:
> I would write all my code for a new feature up front and then test all of the code collectively
Knowing that this is a bad approach is an important lesson - doing things that way creates frustration and wasted effort, and likely harms quality, with no upside.
Another example might be with organisation skill: if you're working in self-made chaos, it's more tiring, more frustrating, and it's less productive and harms quality.
Only if you're working harder. Generally when people talk about productivity-boosts they mean working smarter. That may mean stopping doing things that are just making things needlessly difficult.
The example in the article is a good one:
> I would write all my code for a new feature up front and then test all of the code collectively
Knowing that this is a bad approach is an important lesson - doing things that way creates frustration and wasted effort, and likely harms quality, with no upside.
Another example might be with organisation skill: if you're working in self-made chaos, it's more tiring, more frustrating, and it's less productive and harms quality.