Career Enhancement: totierne 22October2001 ver0.1
Maybe the answer is to allocate time for different hats to aspire towards
and take notes on:
- System Architect 8%
- Manager 2%
- Knowledge Sharing with Other Developers 10%
- Developing better 5%
While still spending 70% of your time productively churning out code
And 5% surfing which you only pretend is useful.
And not to think too much consiously about this stuff outside your 40 hrs
a week.
The problem is we do not work on enough projects to learn much, unless we
learn from other developers experience.
Check out
Slashdot article
archived here
(since you cannot sort by on old slashdot articles).
Which I'll try to make notes on later