Poll: Ongoing professional self-education
Dec. 5th, 2008 11:55 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
I was reflecting today about how much work time I spend just *learning* stuff. As far as I'm concerned, that isn't optional: the programming business will happily steamroller you if you don't work hard to keep up with it, so I spend a considerable amount of time learning random programming languages and such, as well as the enormous amount I spend reading into new technologies for what I'm going to do next. (For instance, I spent nearly the entire past week teaching myself a new language and a new software package.) This leads me to be curious about how much time others spend in this. So let's have a poll!
[Poll #1310015]
[Poll #1310015]
(no subject)
Date: 2008-12-05 05:13 pm (UTC)Part of the trick for me is figuring out where to *find* the information about improving my comic and its various tendrils in the first place ...
(no subject)
Date: 2008-12-05 06:35 pm (UTC)I consider this sort of thing to be personally one of my core job skills / tasks.
(no subject)
Date: 2008-12-05 07:42 pm (UTC)I consider this sort of thing to be personally one of my core job skills / tasks.
Ditto. This poll was inspired by musing this morning about the fact that, as a Software Architect, I consider my morning surf to be an integral part of my job. Indeed, part of two jobs. The CEO is responsible for keeping up with industry news, and the Architect is responsible for keeping up with the technology.
So I officially spend 30-60 minutes just blog-reading and surfing each morning, separate from the constant research into whatever I'm integrating today (my life is Systems Integration, seemingly whether I like it or not) and the personal LJ stuff that gets squeezed into the cracks...
(no subject)
Date: 2008-12-05 06:46 pm (UTC)I'm sure I'm not typical. My current career requires a great deal of further professional education, and my future career has a large frontload of it, as well as some continuing ed.
(no subject)
Date: 2008-12-05 09:31 pm (UTC)(no subject)
Date: 2008-12-05 09:48 pm (UTC)(no subject)
Date: 2008-12-05 09:58 pm (UTC)I'm a bit skeptical about that, since I haven't done anything like writing code since grade school. (I wrote a BASIC program that drew a butterfly.) Plus, current trend here is that learning happens when someone hands me an 800 page book and assumes that I will read it all eventually.
(no subject)
Date: 2008-12-05 11:00 pm (UTC)I'll work furiously on something for a few days to a few months, not really learning anything new. However, during those times I'll often surf up best practices and will occasionally take mini learning vacations looking into all I can find on a particular subject.
I'll treat myself at work by doing things that have nothing to do with work, like talking to a web service with vbscript, playing with a linux distro in a vmware machine, writing a maintenance script in Lua. It's me time, I can't imagine how it would relate to work and I don't bother.
However, more often than expected, there's a company benefit to such amusements. Quick scripting projects that need to be done now, now, now are sometimes done in a day because I once spent a week pissing around with completely non work related stuff.
The other day someone asked me about restoring a mysql database. We're a mostly MS shop, we don't use mysql. But at least one piece of software we use does and I was able to fix the problem without even opening a web browser.
(no subject)
Date: 2008-12-06 03:02 pm (UTC)Fuzziness
Date: 2008-12-08 02:41 pm (UTC)I first answered "60-90 minutes", then changed it to "over two hours", because I decided that the programming language I've been hacking on for the past 6 months counts (since I'm having to teach myself more compiler development skills, I've had a compiler job in the past, and I'd love to have one in the future). It easily comes to two hours a day, since I hack on the train.
Aso, when I'm at work and waiting for the compiler and/or running regression tests, I usually read CS papers—sometimes on compilers, sometimes on Lisp, sometimes on completely unrelated stuff that just might be cool to play with someday.
And then there's grad school, with 2.5 hours in class, plus about 2-3 hours of reading and programming. I'm almost done with that, though—I'm on my last course, and only 2 classes to go.