4 ms·

"Five hours in the lab will save you a whole hour in the library." I am confused on this, you mean "a whole day" or am I missing something here? What I do to c

by blindra 14y ago

"Five hours in the lab will save you a whole hour in the library." I am confused on this, you mean "a whole day" or am I missing something here? What I do to cover my this stupid problem is I work a lot. I always repeat myself and it is of course frustrating. (for example I studied Dynamic programming 3 times from scratch, solved 20-30 problems each time, but after 1-2 months I completely forgot how to solve.)

brudgers 14y ago
I studied Basic in High School on TRS-80's in 1981. I bought the Amiga ROM kernel manuals a few years later. I've owned Turbo C++, basic compilers, downloaded VS express, Python for my Symbian Phone, Beans, JavaFx, and a whole lot more. I did the Code Academy Javascript class. I worked through some of project Euler in Javascript. I started working through Graham's Common Lisp a few months ago. I am hung up in Chapter Three. It's pretty obvious that I can't program for shit after thirty years. So what? Sometimes I enjoy the challenge anyway.
- blindra 14y ago
  Wow that's a lot of trying. What you are suggesting is basically I should keep trying to learn. Because even though I can't memorize important stuff or I have to re-learn important concepts, at the end I am able to write good code, and I solve problems.
Spoom 14y ago
I think it means that looking at the reference materials is quicker than just "throwing stuff at the wall and seeing what sticks", or at least, that's how I interpreted it. It's highlighting that the library trip is more efficient. I could be wrong though.
- blindra 14y ago
  That's kinda strange to me, because I generally hear "practice over theory" quotes.
  - brudgers 14y ago
    Reading a book isn't writing code. Referring to documentation is. And despite not being writing code, reading a book may be part of developing software...just as downloading a compiler is.

by blindra 14y ago

brudgers 14y ago

I studied Basic in High School on TRS-80's in 1981. I bought the Amiga ROM kernel manuals a few years later. I've owned Turbo C++, basic compilers, downloaded VS express, Python for my Symbian Phone, Beans, JavaFx, and a whole lot more. I did the Code Academy Javascript class. I worked through some of project Euler in Javascript. I started working through Graham's Common Lisp a few months ago. I am hung up in Chapter Three. It's pretty obvious that I can't program for shit after thirty years. So what? Sometimes I enjoy the challenge anyway.

blindra 14y ago
Wow that's a lot of trying. What you are suggesting is basically I should keep trying to learn. Because even though I can't memorize important stuff or I have to re-learn important concepts, at the end I am able to write good code, and I solve problems.

Spoom 14y ago

I think it means that looking at the reference materials is quicker than just "throwing stuff at the wall and seeing what sticks", or at least, that's how I interpreted it. It's highlighting that the library trip is more efficient. I could be wrong though.

blindra 14y ago
That's kinda strange to me, because I generally hear "practice over theory" quotes.
- brudgers 14y ago
  Reading a book isn't writing code. Referring to documentation is. And despite not being writing code, reading a book may be part of developing software...just as downloading a compiler is.