[softwaredoug]

I’m pretty enthusiastic when I learn something at work. But the learning comes from a task I seek/was assigned. And I’ll do work appropriate for my skill level. Starting small and growing in complexity. Naturally to do the work there’s a bit of reading and understanding. Indeed starting out, doing a small change, is mostly an activity if gathering context on the code base and tools. But just enough to do a reasonable job at my assignment, and to get feedback from peers.

Instead of “studying” during work I write about my learning process and document my learnings. These are artifacts others find useful, so I’m still building work products.

But if it interests me enough I will read books on it in my own time.