i would like to be a programmer

User 13817637

How can i be good on coding to start programming?

David Crow

Understand problem solving. Ask questions. Ability to think outside the box. et al

"One man's wage rise is another man's price increase." - Harold Wilson

"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles

Victor Nijegorodov

You will work hardly. You will learn hardly. You will communicate with other programmers (in Forums, news groups, and so on) hardly. ... Good luck! :)

CPallini

Quote:

How can i be good on coding to start programming? I start programming in order to be good on coding.

FFY. Experience matters.

jfbode1029

Programming is more than just writing code - it's about solving problems with code. You'll need to develop analysis and troubleshooting skills in addition to straight coding skills. Having said that, the best way to learn how to write code is to actually write code. You could start by looking at Codecademy. It's free, it's all done in the browser (so you don't have to set up a development environment on your local machine), and they cover a useful range of languages. I haven't used it much myself, so I can't comment on the quality of the instruction. It may be good, it may be awful. Depends on what you want to learn.

Vaclav_

Ability to follow instructions. Ability to "read in-between lines" - not every programming task is spelled out in details. There is a difference between being a "coder" which requires mastering the tool - programming language - of your choise, and being a programmer. As already mentioned there is no substitute for experience. Attention to details - loose the "don't sweat the small stuff attitude " fast. And above all - start coding. Best of luck Cheers Vaclav

leon de boer

This is a complex thing so lets go thru it. On a Normal O/S, RTOS very few low level functions ever have exception catches they usually simply report it back. The why is simple, the problem it faces is how the exception should report the error, it isn't clear who it should be reported to the APP or the O/S. As an example, early versions of Windows when low level functions raised an exception put up the blue screen of death and silly things on the API could create it. Blue Screen of Death - Wikipedia[^] It actually became a problem because people got sick of rebooting there computer and on the modern versions of windows it is reserved for unrecoverable errors. Almost all the core windows API almost never raises an exception it simply passes the error back to be handled by the caller because part of being able to handle the error is to know what the caller program is which only the caller knows. So basically there is no problem something like an APP raising exception it can rely on the O/S being able to do something sensible with the exception. However if the caller is something like a driver or the O/S itself there is always the problem the thing you are reporting to has already crashed. So in your case file I/O may well be used by a driver so no-one would set it up to raise an exception. Now there are even newer changes in programming to Virtual O/S which started with VMware. There you have a hypervisor program and the O/S or OS's run above the hypervisor Hypervisor - Wikipedia[^] In that enviroment many low level functsions will raise an exception and the Hypervisor will catch them because it is immune to errors in the VM. So in that situation a file IO may well be setup to raise an exception. See the common theme if you are going to raise an exception the thing that catches the exception must be able to continue running despite the error. So the question of if a low level function should raise an exception depends on there being a stable level below it to catch the raised error. What this answer brings in is the concept of protection rings the wiki entry is very Intel centric Protection ring - Wikipedia[

Tarun Jha

you need to love it, you need to have fun while solving problems, you need to have patience and open mind, you need to be regular, you need lot's of practice and good books, and the rest will follow. that's what i have experienced till date.