Re:The dumbing-down of programming (1998)
by wccrawford on Friday November 12, 2010 @06:56AM
(#1897367)
You can always re-solve a problem, if you want that challenge. The fact that someone else has solved it shouldn't stop you, if your goal is to have a challenge.
Re:The dumbing-down of programming (1998)
by zeraholladay on Friday November 12, 2010 @07:35AM
(#1897434)
Consider the difference between math and engineering (at the undergrad level). Math majors learn to solve solved problems, since the solutions are instructive; that is, they could accept a solution as truth but proving it is true has a greater value. However, engineers need to accept a lot of mathematical truths since the occupation applies these truths.
Either way, both of these systems are instructive. You should be able to reverse a process and discover its discrete parts, if that's your goal.
Re:The dumbing-down of programming (1998)
by Mithrandir on Friday November 12, 2010 @01:54AM
(#1896797)
I always run
$ man life
if I have a problem.
$ make life easier
Your life has been made easier: 70,500,000,000 dollars has been deposited into your bank account.
"There's plenty of challenge for anyone who wants to find it."
There are problems that haven't been solved yet and problems that can't be solved. Most problems can't be solved, since the majority of (our) problems are psychological (i.e. there are no axioms, assumptions, systems, etc to define this class of problem) -- the rest are impossible.
The problems that haven't yet been solved are actually interesting tho. The knowledge systems for these classes of problems are heuristic; i.e. a process of discovery and experience. The intention is often not to keep everything difficult but to keep everything knowable, which is contrary to the "don't make me think" principle of design.