Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 5
    +1 for the last paragraph alone. I wish more companies thought like that! Commented Apr 14, 2011 at 13:12
  • 3
    +1 because I agree that you shouldn't have to setup "slices" of time to learn. Learn as you need to, and if you've learned what you need to know and should be working on implementing it then get to doing that instead. Commented Apr 14, 2011 at 13:21
  • 1
    a complany can definitely increase loyalty of its developers if it follows the advice in the last paragraph. Commented Apr 14, 2011 at 13:23
  • I really don't think this is what the OP was asking about. Of course all programmers learn in the course of the job, that's not even a question. The question I would ask is, "Do you spend your working hours learning something that will not help you solve any immediate problem (but which may make you a better programmer)?" Commented Apr 14, 2011 at 22:04
  • Books - yay, training - nay Commented Apr 15, 2011 at 0:19