Isaac Gouy
12/23/2005 10:44:00 PM
gwtmp01@mac.com wrote:
> On Dec 23, 2005, at 12:57 PM, Stephen Kellett wrote:
> > In message <BF0740FD-4249-4BDE-988B-F21CFF764FD5@mac.com>,
> > gwtmp01@mac.com writes
> >> At one level I understand this point of view. But at the same
> >> time, how
> >> difficult is it to read a book?
> >
> > Very, if you are too tired to take it in. If you are busy with work
> > and have a young family I doubt it would be that easy.
>
> It really scares me to hear that people don't have time to read.
> Even 10 minutes in bed before you nod off is better than nothing.
> Note, I didn't say that *Ruby* should be at the top of your list but
> I really do think it is important to find time to read.
>
> I wasn't trying trying to make a point about Ruby but instead just
> a general point about finding time to read in order to know what
> is going on in your industry, your community, and the world.
>
> One of the questions I ask in interviews is what sort of professional
> development the applicant has pursued. Web sites they read, magazines
> they follow, books they learned from and so on. If I get a blank
> stare or something about being too busy for that....
>
> Gary Wright
Rather than yet more technical knowledge, the area that frequently
needs improvement is skill in communicating and working with others -
so maybe if they read "How the way we talk can change the way we work"
or "Difficult Conversations: How to discuss what matters most" or
"One-to-One in the Workplace"