My Programming Challenges

Question

I love programming and I can't imagine living without it. The problem is when I am developing my own unique algorithms I find it difficult to properly co-ordinate my thinking and I spend more than the reasonable time trying to visualize the solution, although I usually find the solution. I think spending that much time on sometimes "not that hard" algorithm show's that my thinking strategy might be wrong.

Have you experienced similar issues? How do you solve it? Or am I wrong? Please advise me.

Answer 1

With the same talent for getting dug in too deep, I had to look at how I was thinking about design, architecture, algorithms, and all that goodness. Getting bogged down in so much information makes it difficult to regain your vision - "what was it I was looking for?

So, I have taken 2 steps to improve my development efficiency and keep from getting information overload:

• Start writing notes as if you were talking to someone else about the design issues, etc. You will find that when you get buried under tons of information, this document can help you get back on track - or find flaws in your logic.
• Draw pictures, Paint is awesome. As you gain a clear vision of how objects relate to each other, your diagram will take shape.

Answer 2

In my experience, the more you program the better you get at mentally picturing an algorithm and converting it into code. You'll find that common patterns keep on emerging.

Often if you are spending a long time programming simple, well known algorithms, you are better off using implementations that already exist. Most well-known languages have extensive support for many useful data structures and algorithms that can save you a lot of time.

Other than that, i'd say that spending a bit of extra time planning a solution saves you debugging work in the long run, so it's not all bad!

Answer 3

At the beginning, I was forced to create flow charts before I could write the code. I also had to create printer spacing charts for each report.

Occasionally I will create a small flow chart when I need to test out some logic or when I need to figure out a piece of code written by someone else.

Here are three simple questions you can use...

1. What is the input? (this can be data, business rules, formulas, etc.)
2. What is the output? (this can be reports, screen output, database tables)
3. Do I have enough input to create the output?

Answer 4

The solution is to not feel obligated to be smart. Just enjoy the process of discovering the solution. Your thinking skill will be improved over the time but don't feel bad if there is a limit as every one has its limit. Forget about the desire to be smarter than average people and focus on what you are doing, you will have better chance to reach or even push your limit.

Answer 5

I tried diving straight into C++ and tried to take on some immense tutorials when I started to program. After learning nothing (but making some groovy apps thanks to copy paste), I picked up a book on BASIC, and among the first things it told me was how to plan programmes and data flow using pseudo-code and flow-charts/diagrams. I think that if you have something like that sat on a notepad, or as a jpg you can quickly refer to will help immensely in letting you visualize your algorithms., and help you see solutions where juggling everything inside your head has failed.