It varies with the individual person what makes most sense, but here's how it worked for me.
I had a class in programming, where I had access to the manual & various reference documentation, access to a computer that had that language, and various exercises or assignments where I was to program to do this or that, similar to examples in the book.
The big thing the class failed to communicate was how the world of computing capabilities was severely constrained by how that language was structured, what it could and could not do efficiently.
In your educational community, something you should be on the look out for is a class in comparative languages. Usually this is not available to students until after they have learned several languages in a spectrum of different computing environments.
I have learned approx 20 different programming languages from that kind of approach. Today I am only using about 5 of them, the others having fallen into legacy replaced by something else.
After I had shown competence in one or more programming languages, I get hired some place.
I find that the place is using maybe 10 different programming languages or equivalent ... I know some, I not know others. To help new employees like me, they have manuals and other documentation in the languages, examples of code that they are using to run their business, written in those languages, and I am given simple assignments, that work up to more complex, to get stuff done in those other languages.
I have learned approx 40 different programming languages from that kind of approach. Today I am only using about 5 of them, in the same form, the others moved on in my next example.
Every few years, every computer vendor comes out with new versions of old languages. We all need to learn the new features. The arrival of each new version comes with tons of literature talking about how to use the new features, which we read avidly, then figure out how to implement what we have learned.
I have gone thru this process with dozens of languages more times than I can count.
I started programming in the 1960's. At most every employer there were maybe a dozen programming language environments that I needed to be proficient in to keep my job. On the average, these environments went through a revolution every 2-5 years, and I had to stay current. On the average, a whole new set of languages arrived every 10 years, and I had to learn some of them also. On the average, stuff written in the older languages needed to be maintained for decades after other replacement languages came along, but over time the older stuff tended to fade away as re-writes got done in whatever was the language of the day.
2007-12-29 05:42:28
·
answer #1
·
answered by Anonymous
·
0⤊
0⤋
One of the problems with learning programming is that there isn't really any 'first step'. This is because computers are usually very strict about how you type your code, and will just sit there and throw errors at you if you make even one little mistake. It is usually necessary to learn several aspects of a programming language before you can actually write a program that works properly and does something.
That said, I think the most basic part of a programming language that you really have to know is the syntax. Without that, you'll be going NOWHERE. And besides, most programming languages have a lot less syntax than they do types of instructions, so there's just plain less to learn in that aspect.
If you're having trouble choosing a language to learn, I would suggest NOT starting with a low-level compiled language like C++. I'm trying to learn C++, and it can be VERY confusing. Instead, you should start with something higher-level and easier to understand, write and use, like Javascript or Python.
2007-12-29 08:10:59
·
answer #2
·
answered by Anonymous
·
0⤊
0⤋
i think the very first would be understanding how a program works..
For an example
START
INPUT birth_year
IF birth_year <18
PRINT you are too young
ELSE
PRINT you may enter
END
This is a general example and think of how it works and what might be the effect of changing the value of the birth_year.
Understand how a general algorithm works can helps a lot in future of learning programing.
Then you will have to start learnign a specific programing language of your choise starting from its very first basics,andd ....
2007-12-29 05:43:30
·
answer #3
·
answered by Hayaakuda 1
·
0⤊
0⤋
both.
you will need something to program in order to learn to program.
I dont think you can learn programming only by studying the syntax of a language neither by only studying algorithms. do both at the same time.
2007-12-29 05:33:41
·
answer #4
·
answered by gjmb1960 7
·
0⤊
0⤋
what do you mean exactly? an algorithm is a sequence of events to complete a task....the first step in learning a language would be to pick one( Java, C++, ) and understand it and how it works
2007-12-29 05:33:10
·
answer #5
·
answered by biznitchil 4
·
0⤊
0⤋
Why don't you check up on google lol. They will definately have an answer.
2007-12-29 05:32:23
·
answer #6
·
answered by Kulla kulla 1
·
0⤊
0⤋
learn
2007-12-29 05:31:51
·
answer #7
·
answered by sugar m 1
·
0⤊
0⤋