what should learning before programming ?

Even with high level programming languages, the key to a programmers skill is their understanding of math (Boolean in particular) and logic.

The better your math and logical approach to solving problems, the better you will understand a programming language and be able to write efficient code.

As a lot of other languages are built on the core of "C" and "C++", I would want to have a working understanding of "C" before moving on to other languages.

Chas

The really important concept is "formal systems". That is systems that have complete and precise definitions, and which you can use formal logical arguments to prove or derive things and be absolutely certain they are correct.

The same applies to programming languages. For example, an Integer in programming is not just a "normal" integer. Among other things, they have a maximum value. They can't be infinite like a "normal" integer. So, you need to keep this in mind when writing you code.

The danger is when you think about a programming construct as being like something with the same name in the real world. They are not, and they don't follow the same rules.

Maths helps people learn to think in a formal methodical way, particularly when you work through proofs. Just like maths, in programming, you have a number of relatively simple, precisely defined tools and have to figure out how to combine them to create a solution.

Good Luck

I don't think there is any thing you really need to know before programming. A math background helps but unless you are writing some really complex algorithms it probably isn't necessary.

There are programming concepts that you should learn as you go. So I'd suggest buying a good book or following a detailed tutorial that will walk you from the basics to the advanced.
"Big Bad Java" is the book my program used for java and it seemed to cover most of the programming concepts used in java.

If there is no command of a written language, you'll never develop computer languages.

Dijkstra a long time ago said something like "If I had to choose programmers I would choose them on the basis of excellent command of their native language". I do not know how well heshesh2010 commands his own language, and that is Dijkstra's criterion, but his English could do with improvement and mapping one's own language to another is comparable to mapping a user's desires (often expressed in poor natural language) to good specifications and thence algorithms and thence to program codes.

Being able to think logically and being able to see complex patterns helps a lot.

Also, as said before, you need to have a good grasp of your spoken language, whatever that may be. A big part of programming is documenting. If your documents are unreadable, you won't be employed for long.

Also, always remember that a user will do everything wrong, and its your job to stop them.

But while you are learning make sure you take the time time to really understand how to use the Debugging tools and the methods of Debugging that are employed by the development environment/tool/language interface. I struggled with different areas here and there as Our program (instructional class) progressed thru the coursework, but when I learned how to employ the debugging interface it gave me insight to things and really helped me understand some of the concepts I just wasn't grasping completely.. (It also helps you to ensure that you have an understanding of what exactly your code is supposed to be doing.) Often in life we use "things" that we just input some material and get a predefined or "expected" output but when the result does not meet what we are expecting or desire, it would be great if we could "peel back the cover" to see what is actually happening to that input or whatever the case may be and possibly provide some clues as to why the result is returned the way that it is. Does that make any sense?

is thing called a grammaring, you how to grammar should learning.

i also think the term ' Dara structure' is important and some logical ways to solve problem in design stage .

i want to ask what is best java books that turn me from A to Z and make me very perfect .

In addition to what others have already said, you also will be better served if you know to read technical material. This is a skill you have to learn. Technical documentation is becoming a lost art, and as a newbie programmer, you're going to face a doubly difficult time because so much of the material written on the web for free is written by people who do not know how to do technical documentation. Which means there are really two issues here - one is that you have to be able to recognize good technical documentation, and then, you have to be able to learn from it.

The main difference between technical documentation and regular writing is the specificity of terms, and the completeness of the content.

In sloppy technical articles, they will tell you about maybe one or two different aspects, of which there could really be fifteen or twenty. They won't even let you know those other options (they could be key words, reserved words, arguments, tags, functions - whatever)
and you will miss a huge part of the picture.

Also, when learning to program, you are learning a new environment, and there is a vocabulary you have to learn. Many web articles don't teach you that vocabulary.

I've found that going on Amazon and buying a ten-year old book is very cheap. You can get them for under $10, including shipping. And the basic languages have not changed that much in 10 years. But again, you have to make sure that it is good book. You'll have to look at samples from the book either on google books or peek inside feature of Amazon.

I can't speak from the formally educated perspective as I am not, but I can speak from someone that has learned quite a few languages and built a lot of applications. It all depends on what kind of programming you want to do as to what kind of background you'll need.
If you want to do game or complex algorithms of various kinds, math is critical. If you want to do business software that supports various forms of data manipulation then math is not so critical. I have built custom software applications for many (25+) years and the ability to understand business problems and translate them into custom applications is probably something that can't really be taught. You may be able to get the basics like manufacturing processes, accounting, etc. but it takes a very determined mind to learn what is needed. I was fortunate in that I didn't tell anyone that I didn't have a formal education in business processes and in a way, they taught me their business as I translated it into a custom solution.
The key is learning the correct tool for the job. If someone wants a web based solution it would be silly to use C or C++ as the tool of choice. As would using HTML/PHP/Javascript/CSS/MySQL for a disk formatting utility. It all depends on what you really want to pursue as a career.
All of the suggestions so far have been good advice. I say do the research on what kind of programming careers there are and make a choice of which one interests you the most. Then make a decision on what you really need to streamline your learning process. Formal education always helps when applying at Microsoft or Apple but if you don't want to work for a large corporation then you might want to self teach all that you need using books and the web. A formal education will teach you the thinking skills necessary for programming if you don't have the natural ability but make sure you will absolutely need the skills taught before spending the money and the time. If you're a natural and you don't need to be taught then get some books and go for it.
Best of luck to you...

My advice would be to stop and make Pascal your introduction to programming.

You need to learn things like referencing, iteration, functions, and abstract data types. Wirth designed the language to be safe during implementation of those concepts.

I would stay away from C++ for the same reason I would stay away from Java as your first programming language. They have complicated elements not suited for beginners.

If you want to dive into object based or object oriented programming I would suggest Oberon (an OOP learning system designed by Wirth)

In addition to programming languages you will want to learn tools related to the process. Things like a complier, linker, text editor, revision control and make tool.

There are integrated environments that do this for you but I started with vi, rcs and make in a BSD UNIX environment. Pick those tools for the OS you use.

I would recommend the Pragmatic Programmer books. http://en.wikipedia.org/wiki/The_Pragmatic_Programmer

i have Studied java and c++ and html and java script .in my college

because i'm student in it and computing faculty .

Flow Charting. If Then Else means very little to the average person but once you understand how to flowchart it means everything. The computer ismple it's either on or it's off. If you can't concieve how something can work by being nothing more then an on and off switch you can not percieve the logic behind how it should work. Therefore you can't make it work beyond simple things.

Before writing "accounts receivable", you need to know at least some accounting; terminology,
procedures, etc. If you are monitoring a nuclear reactor, you need to know some atomic physics!

You need to know algorithms and data structures. Perhaps the most difficult thing you need to
know is how to document what your program does and how it does what it does. If you can't do that or neglect doing it, your program will wind up in the dumpster because it's easier to do
it over again, from the beginning, than it is decipher your program.

Challenge yourself and get up to speed extremely quickly. Although Math and Logic is logical approach but object oriented thinking builds on declarative approach.

Try the first chapter Strategy pattern in the book Head First Design Patterns. It will challenge traditional programming logic. Next, css and html suggests you are looking into web technology. I recommend web services. How to host or consume web service. You will realize how to put the Java logic you have build, separate from html forms and css. Get this and you will be ready for basic interviews, competitive salary and basic!! real world programming.

Hello,
One big thing most seem to be missing in the advice is the problem solving skills you will need. Flowcharting helps once you can visualize the problem, but it first must be broken down to a series of smaller steps. I use mind-mapping during planning. You can continue to break the problem down until you can visualize the process line by line in code. The smarter programmers can take these abstract steps and wrap them into functions that can be re-used over and over.

I started from scratch learning Java. That being said I already had basic scripting experience in php, html, javascript, and VB.

Java really opened my eyes to the whole OOP perspective. If you are going to write applications for systems, OOP is essential. For smaller web-based apps, you could get away with a procedural language. I prefer php as you can combine OOP and procedural language if you have to (older external libraries use procedural code sometimes).

My first java book which is still my favorite is "Thinking in Java" which is a large book. It covers all aspects and is well written.

I would also recommend all of the Head First books. They are very well written and easy for beginners to follow.

Best of luck, we need more good programmers out there! Don't be lazy!
Rob