It depends of the work I am tasked with. If it is boring and tedious, I tend to become lazy. If I find it interesting, I tend to work more.
If I am tasked with design and implementation, I tend to enjoy more so I tend to work more. If I am tasked with just the implementation, I tend to work less.
It also depends on teams. I worked in teams where the product owner wasn't very pushy and the all team mates tried to work as little as possible and I worked in teams where high pressure was the norm, the product owner was very pushing, team mates committed to over work and kind of pressured their pears to overwork, too.
In the low pressure teams we had less code of higher quality, in the high pressure teams we had tons of code of less quality which kind of needed rewrites.
If someone asks me, I don't think either of the extremes is good. A team or developer should produce a reasonable amount of work of good quality.
If I am tasked with design and implementation, I tend to enjoy more so I tend to work more. If I am tasked with just the implementation, I tend to work less.
It also depends on teams. I worked in teams where the product owner wasn't very pushy and the all team mates tried to work as little as possible and I worked in teams where high pressure was the norm, the product owner was very pushing, team mates committed to over work and kind of pressured their pears to overwork, too.
In the low pressure teams we had less code of higher quality, in the high pressure teams we had tons of code of less quality which kind of needed rewrites.
If someone asks me, I don't think either of the extremes is good. A team or developer should produce a reasonable amount of work of good quality.