This is something I wish I realized when I started programming, so I am posting this in hope that I enlighten some newer programmers. 
Programming is an art form, just as much as sculpting, music, painting, sketching, etc.
Most of the programmers you ask will agree to this.
Like a conventional artist's different mediums, a programmer has different programming languages. Some of these are lower level, dealing directly with the processor. These programs are much harder for people to write and understand, but they are much easier and faster for the computer. This is comparable to how Pointillism is very tedious, but you end up with a very beautiful, detailed, and interesting result.
But most programming is not done like this. Most programmers use "higher-level" constructs, like "if statements", "objects", and "for loops."* This is like using paint brushes. It is much less tedious, but does not allow for as much detail.
Just as a painter has their set of paints, a programmer has a set of instructions. In most programming languages, you have "loops" (they let you execute the same code multiple times), "functions" (basically they can perform a specified chunk of code, optionally taking or returning values), "if statements" ("if <condition> is true, do this code, otherwise, do this code"), and "objects" (I'm omitting my definition in the interests of keeping this essay concise)
Programmers also have style guides, which are simply rules for formatting code that are generally agreed upon. Not only does having a loosely followed standard aid readability, but most programmers agree that the style is actually pleasing to look at. Sometimes, the style is mandatory or the code will not run, such as Python.
Some programmers play "code golf". They try to make their code as small as possible (similar to golf, where you try to get the ball into the hole in as few hits as possible, hence the name). Not only is this a fun and rewarding task, but you also lear a lot about the quirks and intricacies of the programming language you are working in.
Still other programmers try to may their programs actually take a physical shape, essentially drawing with their code. This is really hard on certain languages, and is the most obvious ways that programming can be an art form.
* Though, arguably, these exist in lower level languages, this is clearly not caring about the technicalities.
Post your own advice for new programmers! What do you know now that you wish you had realized earlier?
Programming is an art form, just as much as sculpting, music, painting, sketching, etc.
Most of the programmers you ask will agree to this.
Like a conventional artist's different mediums, a programmer has different programming languages. Some of these are lower level, dealing directly with the processor. These programs are much harder for people to write and understand, but they are much easier and faster for the computer. This is comparable to how Pointillism is very tedious, but you end up with a very beautiful, detailed, and interesting result.
But most programming is not done like this. Most programmers use "higher-level" constructs, like "if statements", "objects", and "for loops."* This is like using paint brushes. It is much less tedious, but does not allow for as much detail.
Just as a painter has their set of paints, a programmer has a set of instructions. In most programming languages, you have "loops" (they let you execute the same code multiple times), "functions" (basically they can perform a specified chunk of code, optionally taking or returning values), "if statements" ("if <condition> is true, do this code, otherwise, do this code"), and "objects" (I'm omitting my definition in the interests of keeping this essay concise)
Programmers also have style guides, which are simply rules for formatting code that are generally agreed upon. Not only does having a loosely followed standard aid readability, but most programmers agree that the style is actually pleasing to look at. Sometimes, the style is mandatory or the code will not run, such as Python.
Some programmers play "code golf". They try to make their code as small as possible (similar to golf, where you try to get the ball into the hole in as few hits as possible, hence the name). Not only is this a fun and rewarding task, but you also lear a lot about the quirks and intricacies of the programming language you are working in.
Still other programmers try to may their programs actually take a physical shape, essentially drawing with their code. This is really hard on certain languages, and is the most obvious ways that programming can be an art form.
* Though, arguably, these exist in lower level languages, this is clearly not caring about the technicalities.
Post your own advice for new programmers! What do you know now that you wish you had realized earlier?
If you look hard enough, I remember posting some code on here that didn't work back when I had just joined. It was because I didn't know about End statements in If-Then-End blocks (don't ask me how that even made sense, since the calc had no way of knowing what code to execute under what conditions). To be honest, I'm surprised I got as far as I did without knowing some very basic things (having taught myself the basics of ti-basic without any documentation, manual, forum, etc.)
