How Do You Solve Problems

This is a discussion on How Do You Solve Problems within the A Brief History of Cprogramming.com forums, part of the Community Boards category; Originally Posted by Bubba I solve problems through research and some through trial and error. I agree with this about ...

  1. #16
    Registered User
    Join Date
    Mar 2003
    Posts
    580
    Quote Originally Posted by Bubba
    I solve problems through research and some through trial and error.
    I agree with this about 1000%. I believe understanding concepts at a very fundamental level via doing research, then trial and error, is the way to solving problems.

    Of course, this assumes you've already clearly defined the problem you are trying to solve, which can be a difficult task in and of itself.
    See you in 13

  2. #17
    Registered User
    Join Date
    Sep 2004
    Posts
    123
    It all depends on the kind of problem.

    If it's an algorthmic issue, I'll draw diagrams and write the code from the diagrams. Very rarely do I ask someone for assistance because by the time I've communicated the exact requirement I could have worked it out anyway.

    If it's a thing such as confusion on how to use a specific command (e.g. the command doesn't appear to do what the documentation says it should) and I can't get an answer by reading help, Googling, or forum-searching, then I'll ask a question.

    Generally speaking, I always try to get an answer myself before involving others.

    Other problems are simply solved with difficulty:

    Code:
    with Difficulty {
      problem.Solve(x);
    }
    where x is the problem you want to solve. It works wonders!

  3. #18
    Its not rocket science vasanth's Avatar
    Join Date
    Jan 2002
    Posts
    1,683
    I usually imagine problems to be blocks of diagrams composed of various smaller blocks.. But when I see the problem for the first time.. I only see the bigger blocks.. I decompose them, only when I reach that particular part....

  4. #19
    Unleashed
    Join Date
    Sep 2001
    Posts
    1,765
    I cheat as much as possible everywhere I can.
    The world is waiting. I must leave you now.

  5. #20
    Registered User
    Join Date
    Oct 2004
    Posts
    63
    I do a couple of things.

    If its possible I build a shell of a program, and then slowly upgrade it until it does everything I want it to. (for example....take in one input at the first stage and act on it, second stage take in next input, third stage its fully ready).

    If it isn't really possible (or worth it) to do that I often just sit down, write on paper what I want to do and some ideas...and then start typing. If I come up with a problem I can't solve, I get annoyed by it, if I still haven't found it in half an hour I probably won't find it...so I talk to some friends on MSN, and just relax....then the answer comes to me

  6. #21
    Code Goddess Prelude's Avatar
    Join Date
    Sep 2001
    Posts
    9,796
    The first thing I do when solving a problem is figure out what the real problem is. Most of the time, what you're asked to solve isn't what you end up solving. So you turn your wheels without going anywhere if you try to solve the first problem that arrives at your door. Next, I try to simplify as much as possible so that I don't do any unnecessary work. It's all about laziness, really. If I can minimize my coding time by molding the problem to something I know I can get right then I'll also minimize my debugging time.

    The next step is to prototype the hell out of the problem. With a trashy prototype I gain valuable experience in the implementation of the problem without the burden of being forced to throw away nice code when I reach a stumbling block. I've found that several big prototypes and a lot of small prototypes followed by a final version tends to end up better and gets written faster than trying to put Band-Aids on good code using bad assumptions.

    So I guess my three biggest rules for design are
    • Understand
    • Simplify
    • Prototype
    My best code is written with the delete key.

  7. #22
    Banned nickname_changed's Avatar
    Join Date
    Feb 2003
    Location
    Australia
    Posts
    986
    Quote Originally Posted by manofsteel972
    My pet monkey is hard at work on my other system. I decided to do away with the compiler and just create the binary directly. He is busy flipping a coin for a 1 or 0. He almost has a working os kernel
    Wow, I didn't know the linux kernel developers frequented this board

Page 2 of 2 FirstFirst 12
Popular pages Recent additions subscribe to a feed

Similar Threads

  1. C Pointers Problems
    By mhelal in forum C Programming
    Replies: 8
    Last Post: 01-10-2007, 06:35 AM
  2. String Manipulation problems -_-
    By Astra in forum C Programming
    Replies: 5
    Last Post: 12-13-2006, 05:48 PM
  3. c problems
    By hitman_here in forum C Programming
    Replies: 5
    Last Post: 02-06-2006, 05:54 PM
  4. Coding Problems
    By RpiMatty in forum C++ Programming
    Replies: 12
    Last Post: 01-06-2002, 02:47 AM
  5. programming problems from competition..
    By Zeeshan in forum C++ Programming
    Replies: 0
    Last Post: 11-12-2001, 12:26 AM

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21