Re: Getting Started
Oh! I missed your point entirely, but I agree with you on this as well.
On Thu, 2006-02-16 at 00:13 +0900, James Edward Gray II wrote:
Just to be clear, I was actually talking about reading *code*, not
books. I think you learn a lot from figuring out how other
programmers solve problems, by breaking down their solutions.
Though books are valuable too, of course. I also agree with others
that writing code is the key.
James Edward Gray II
Relevant Pages
- Re: Hello Everyobody
... Jerry McBride wrote: ... > Are you the guy now asking for help in figuring out HOW TO DO HIS job? ... brother to go read some more books, gain some more experience and try ...
(comp.security.firewalls) - Re: How Very Interesting!
... who did not enjoy high fantasy get much out of the books? ... quotations in academic journals, number of quotations on Slashdot, ... people who saw the movies based on the books, and so on, an so on. ... When figuring out what books to read, ...
(rec.arts.sf.written) - Re: Harlan Ellison purging his book collection
... thirty boxes so far, with fifty or sixty still to go, and I'm ... You're going to want to enlist Hal's aid in figuring out which books ... doesn't have to get rid of them ... ...
(rec.arts.sf.written) - Re: So what books did you get for Christmas?
... Even the people who know me best seldom attempt to give me books for ... Christmas, figuring if I want to own it, I have it or it's something no ...
(rec.arts.mystery) - Re: Sleeping in Light
... major overhaul of process, adding a department and a staff and someone to oversee it, figuring out which of the tens of thousands of books in your backlist are even in a format that can be disseminated as an e-book (and older books ... are likely NOT in a usable format), to say nothing of checking your contracts to see if you even have the _right_ to distribute the book in that way. ... Within a few years 80% of the books people want will on your e-book catalog. ...
(rec.arts.sf.tv.babylon5.moderated) |
|
