You should focus on your I/O ratio, the balance between getting input (learning) and producing output (creating new knowledge). I've found when there is no bal

You should focus on your I/O ratio, the balance between getting input (learning) and producing output (creating new knowledge). I've found when there is no balance there is no productivity: if you read too much without writing you'll get frustrated by not producing anything; when just writing code without reading you'll realize your work was not fully productive, in the meantime some nice technologies were published which would make you far more productive if were used.