[gwd]

Imagine if you told your boss you were only going to actually write code or investigate bugs from 1pm-5pm on Fridays, and the rest of the week you were going to practice "fundamentals". Your boss would think it completely ridiculous, but it's still a larger ratio of performance to practice / training than a professional musician or athlete.

[Juliate]

The nature of the work is not the same, hence, the proportion of the modalities of your work are not identical.

The problem is considering that only your office boss work view is the one that qualifies as work.

The problem is also considering that a software engineer performance is in writing code/investigating bugs, whereas it is in the whole process/intellectual pursuit. In some cases, you will need to spend a whole week of going back to fundamentals or training or other, to be able to solve your issue in a few hours on Friday.

[johnnyanmac]

>The nature of the work is not the same, hence, the proportion of the modalities of your work are not identical.

I guess we solved that problem then. We're comparing apples to oranges and wondering why oranges don't have edible skin.

>The problem is considering that only your office boss work view is the one that qualifies as work.

So you're suggesting that more programmers should practice in their free time?

>The problem is also considering that a software engineer performance is in writing code/investigating bugs, whereas it is in the whole process/intellectual pursuit.

You can argue we're always performing or never performing in that case. Or perhaps our "performance" is crunch for a deadline, or right after a product shislps.

Either way, it's fundamentally different from practice/performance scheduling of athletes or musicians. Performance should be a place where you put 110% into an act, often in a burst. Physically or mentally, we can't afford to operate at 110% every day. That's why there's often a rest day for musicians/athletes. Knowledge workers is much more spotty.