4 ms·
I guess I feel guilty when I'm not producing code and simply learning for the sake of it. There is no good ratio if I'm not sure what I'm studying can be applie
by lowglow 16y ago
I guess I feel guilty when I'm not producing code and simply learning for the sake of it. There is no good ratio if I'm not sure what I'm studying can be applied to what I'm producing.
Also looking into Pomodoro (http://www.pomodorotechnique.com/ http://www.pomodorotechnique.com/)
- michael_dorfman 16y agoI'm a firm believer in the value of learning for learning's sake, so I don't worry if the things I am learning can be directly applied to what I am producing at the moment-- as long as I am producing at the moment. What's your general situation? Self-employed? In control of your schedule? If so, why not start with 7.5 hours a day on production, and half an hour a day of research/playing. Give that a couple weeks, and adjust if necessary.
- lowglow 16y agoI work at beyond full time at a start-up cranking out code and putting out fires (~10am-7pm+). Then I come home and crank out more code on a project I'm working on (~7pm-1am+). There are just a ton of things to research/play nowadays. I feel like I'm constantly playing catch-up with things I need and want to know. Do people get to play with new tech at work? Should I be pushing for more hours to try something new at work?