I read a book called “The Goal” by Goldratt and he describes his theory of constraints. One of the main predictions of his theory is that the existence of many resources working at maximum capacity is symptomatic of a wildly inefficient production system. Thus you shouldn’t feel guilty about not giving 100% every day. This behavior is necessary to properly balance the total throughout of your company. Ideally only one person should be giving 100% in any given company, and in a fair and balanced system this would be the CEO who is concomitantly receiving massive compensation.
That was one of the most eye opening books for me. I think it all applies to Software development as well. It is not uncommon that you work all weekend to finish your task, only to see it waits two weeks in the next person's queue.
I've applied it to my studies as well. You will achieve little by learning a bit of everything. There is always one area of knowledge you are urgently lacking in, that you should hyperfocus on, in order to alleviate the information bottleneck of the system you are working on. It's the same as in the book: the teacher is always whittling down the incoherent problem space to the critical piece of wisdom that the protagonist then has to discover on his own.
This theory feels like it’s making tons of assumptions and leans heavily on semantics.
In a factory you have many components operating near or at capacity. In a high growth environment you want all of your components working at capacity to explore the problem space and optimize.
