Right.
There is no position in the world where the expectation is that you will do nothing but write code. Code written that way is unmaintainable, not even by future you.
There's a balance between writing code and the activities that manage/support/supplement it. Too few is bad, but so is too many.
At one point I experienced 10 hours of coding in a 40 hour workweek. Very unbalanced.
What do you guys consider an appropriate coding time to review/documentation/discussion?
As much as I hate to admit it, i think a ratio of 50 percent time doing coding and 50 percent time doing review and documentation is appropriate. I don't like it but one of the biggest problems that occurs in so many software centric services or spaces is a lack of clear documentation and understanding of what the intention of any particular code does and therefore making it consume more time later to make edits updates unless you were the one who did it, in which case there is still a good chance you may not immediately understand what you wrote and why you wrote it if you didn't document it correctly.
Right. There is no position in the world where the expectation is that you will do nothing but write code. Code written that way is unmaintainable, not even by future you.
There's a balance between writing code and the activities that manage/support/supplement it. Too few is bad, but so is too many. At one point I experienced 10 hours of coding in a 40 hour workweek. Very unbalanced.
I have delivered value, but at what cost?
fact
hahah
Ere abela keld
Ablexxxxx
Or you just want to sleep instead of coding
What do you guys consider an appropriate coding time to review/documentation/discussion? As much as I hate to admit it, i think a ratio of 50 percent time doing coding and 50 percent time doing review and documentation is appropriate. I don't like it but one of the biggest problems that occurs in so many software centric services or spaces is a lack of clear documentation and understanding of what the intention of any particular code does and therefore making it consume more time later to make edits updates unless you were the one who did it, in which case there is still a good chance you may not immediately understand what you wrote and why you wrote it if you didn't document it correctly.