views:

438

answers:

10

Part of our job is to be competent enough to make intelligent decisions pertaining to new technologies. How much time should be spent learning/researching versus implementing?

+9  A: 

As much as necessary to get your job done and done well. IMO there's really no set limit or percentage.

Matthew Jones
+1 Absolutely spot on
Cobus Kruger
Well darn. I wish there was a way to take off CW...
Matthew Jones
+1  A: 

Implement constantly on your own (dev stuff for yourself, try a new task/language/feature each week) and you'll learn/research constantly in the process.

The best we can do while being paid, is to implement the best we know how. And knowing is half the battle.

DreadPirateShawn
+1 for the implication that professional learning and researching is our responsibility as well as our employer's
mas
+1  A: 

I don't think people stop learning when working!

You can do the same thing a million ways. Work time is constant research and learning providing your work is diverse enough

Aiden Bell
+1  A: 

At the end of the day, one get paid to get the job done.

So - if by investing X percent of your work on learning you'd be able to complete your missions earlier, it would be in the best interest of both you and your employer.

Now it's only a matter of providing and proving the correct X to your manager

Ken Egozi
I agree in general but would expand 'earlier' to include ' and/or better' and the broader concept of providing value to the employer.
mas
+5  A: 

Abraham Lincoln said it best:

Give me six hours to chop down a tree and I will spend the first four sharpening the axe.

So apparently Abe Lincolns rule of thumb was 2/3rds of the total time.

Yes, he actually said "four", not "hour": http://www.brainyquote.com/quotes/quotes/a/abrahamlin109275.html

Neil N
So 33.3% would be about right.
Nosredna
see my edit... I looked up the quote, He said 1 hour in 6.
Neil N
So 16.7% would be about right.
Nosredna
He actually said 4 in 6
Neil N
So four (of six) hours spent sharpening the ax?
ecounysis
So 66.7% would be about right.
Nosredna
+1  A: 

Google give their engineers 20-percent time, though from my experience few other companies would give over so much time for this, more like 2-percent time (if you're lucky).

Graham Miller
+1  A: 

It depends on the urgency of the job (sometimes you just have to get it done, yesterday), but by all means, learn and understand as much of what you are doing as possible. Taking the time to understand why things work the way they do along the limits and purposes of your given tools will always pay dividends in the future.

If you find a piece of code on SO and it solves your problem, take the time to learn exactly what it is doing and why. I believe this will always lead to getting things done quicker and smarter in the future

Tom Hubbard
+1  A: 

When you're not implementing existing technology, you should be researching new. When you're constantly thinking about how doing something using new technology would be soo much easier than using the old, it's time to start using the new.

joebert
+1  A: 

The answer for a lot of people in this profession is "O%" or "whatever my employer will fund". These people end up leaving the business. I'd say 20% is a minimum if you want to be outstanding, and keep your edge over the long haul. On the other hand, I know one guy who does amazingly well learning on the job, so your mileage may vary.

A. L. Flanagan