css: p{color:blue;}
js:
If you want to learn other languages, start with syntaxes. Then move on to next step, multiple elements and multiple functions and then so on.
Remember that it is all gradual. Every language is built from 1s and 0s. So start with baby steps and you will be there in no time!
Also remember to work with projects. Even if its just printing out a statement, try to do it on an editor. ( http://jsfiddle.com or Online REPL, Compiler & IDE or CodePen are good to start ) Just know that once you know a minimum level of stuff, you’re gonna feel invincible and you can do anything. Actually you can do anything! Happy programming!
Lindsey Spratt
Computer Scientist (2017-present)
193w ago
I am interpreting this question as "How are you learning to code?" I started learning to code 45 years ago, and I still hope to become really good at it.
I am learning to code by reading books about programming, reading programs, and writing programs. A lot of programs. And talking to programmers. A lot of talking.
I started programming the DigiCompI using boolean algebra in 9th grade (1969). It was so cool. (Minds-On Toys - Kits)
I finally got back to declarative programming using Prolog (my favorite programming language) in 1986. In between I programmed in Fortran, PL/I (IBM and Multics), and Lisp. For each of these languages I read books, wrote programs, read other people's programs, and talked to people who were expert programmers.
I did not take any classes in programming languages; that might have been useful. However, I was an undergraduate at MIT and there were programmers and computers and programming projects everywhere. So I got jobs where I learned to program on the job and saved my formal education for subjects I loved but could not find anyone to pay me to learn: mathematics; history, theory, and criticism of architecture; music theory, composition, and performance (yay trombone).
The mathematics has been really useful in programming: particularly algebra (groups, rings, functions, isomorphism), number theory (primes, big O notation), mathematical logic (proof theory, model theory, axioms, inference, …), set theory (union, intersection, power set), and probability and statistics. I recommend learning as much discrete math as you can - it will make you a better programmer.
After working for 11 years as a programmer (Multics operating system, computer-aided software engineering tools), I went back to school and earned a masters and doctorate in computer science. This was finally some formal learning that improved my programming.
Eventually I picked up languages in the C family: C, C++, Objective C, Java. yuck. I do not like these languages but they are pervasive.
As long as you are programming, you should always be learning to program better. Read books about programming, talk to other programmers, read other people's programs (with so much open source code, there are a lot of programs available to read), and write a lot of programs. Do this every day. Think about it all of the time. Enjoy yourself. Even after 45 years of this, I am still having a great time programming.
Mark Miller
Academic wanderer, writer, aspiring computer scientist
193w ago
I first learned to program in Atari BASIC on an Atari 400 that my local library allowed patrons to sign up for time on back in 1981. I was 11 going on 12.
The first program I got working, that was my own idea and was more than just the equivalent of "Hello world," was a little math quiz I wrote to help myself with my arithmetic skills.
What motivated me to learn about programming was I witnessed a middle-aged man doing some on the same machine. He was working with graphics, and was trying to get some sort of low-rez horse racing game working the way he wanted. I had done a little practice with animation on paper when I was younger, so I could relate a bit to what the man was trying to do. The first thing that caught my eye were the colorful graphics. What fascinated me was the idea that this man was doing something to the machine to generate them. I had never witnessed this before. The guy didn't look superhuman, or anything out of the ordinary. That gave me my first clue that maybe I could do what he did.
At first it was just a wish. I thought that since he was an older adult, perhaps working for the library, he must've had special permission to use the computer. That had been my experience. Computers were expensive, delicate, and rare, and usually only special people got to use them, even if they were kids. My mom noticed my interest and goaded me to ask the librarian if I could use it. She said yes, anyone 10 years or older could use it. All I had to do was take a 15-minute orientation.
I tried out an interactive tutorial from Atari called "An Invitation to Programming." It was kind of nice as it started out slow, but they didn't design the learning curve well. It got steep pretty quickly, and I got lost and frustrated. After going through it a couple times I realized this wasn't the right way to go for me, but I was not deterred in my goal. I asked a librarian if they had anything else I could use to learn about programming the computer, and they told me they had the Atari Basic manual. I tried that. It was less exciting, and gave me a headache reading it, but I found I was learning more from it than the tutorial, so I kept reading it. That gave me a good start, but I still needed a lot of help. Fortunately, there were always other kids and young adults that hung around the computers, and we'd discuss programming problems. They were a tremendous help. Within several months I learned there were computer magazines around that had type-in programs readers could try out. I read them eagerly, typed in the printed listings, and read the technical explanations of how they worked. This opened up possibilities in my mind for my own projects.
No comments:
Post a Comment