Thought this was pretty funny -- I recently (re-) read "I Think You Must Be Joking", where Feynman described his problem-solving approach:

1. Write down problem
2. Think real hard
3. Write down solution

I agree with a log of the comments here, esp. about those full-screen pics that you have to scroooollllll past before you can even begin to read.

OTOH, a picture can serve as a shortcut for a summary, or help to create interest. For better or worse, the web is largely a visual medium.

In my own case, I started publishing my (technical) blog without pictures, and it just looked boooorrrrrrrinng. So I started sticking whimsical little pictures next to the lede, and I have to say that I think it looks a lot better that way, and I suspect that it helps create interest for people who may just stumble upon it.

FWIW, here's the blog: http://btorpey.github.io/

My understanding is that developers at Google have root on their development machines. (Googlers please feel free to confirm or deny). If Google can make that work, with their bazillions of developers, I would think that others could do as well.

I've managed to get that done at my shop (finally) -- prior to that I ran VM's just so I could have root.

It's interesting -- I'm watching spring training games on TV, and what you see there is a whole bunch of old guys (coaches and managers) telling a whole bunch of young guys how to play the game. (My personal favorite is Terry Collins, who is 67, and who is constantly in teaching mode).

This is considered normal in baseball -- it's taken for granted that the old guys know a whole lot more about how to play the game than the youngsters, and the youngsters have no problem with that. (And the smart ones go out of their way to soak up as much of that knowledge as they can).