If you want to be a good programmer, you must work so hard – initially you need to have patience’s to learn something new!, if you have good attitude and patience’s then you can go for it and you can do anything….

All the best for your future endeavors!

Thanks,
Vivek

Godbless all.

Finally, my suggestion will be don’t dream to become a marine engineer, if you don’t like ships.

Meaning, if you don’t like working 40 hours per week sitting infront of computer, then don’t take up computer science. It will not only cause a nervous breakdown, but as well cause a life breakdown.

This is very good presentation for the new comers to Software, but will be some what bore to already people. i think the presenter published this article, keeping freshers in Mind.

But my comments are as follows:
It seems its completely theoritical presentation. Why dont you include some real time examples such as

1) Learning Programming Languages in efficient way

ex:- follow these rules and flow of concepts like first History, variables, keywords, datatypes, syntax, input/output, functions like that,

2) debugging :- examples should be given like how to debug, no. of ways testing the code, etc..

3) Self Motivated:- How to update ourselves… need to give live examples such as watching technolgy sites, searching in google, reading IT magazines and technology trend magazines like Digiquest. DIGIT etc,

Am i right?

Let me know your thoughts.

If you had said: “3 Steps to become a Good Developer”, then I would totally disagree. Actually, I would be off topic if you hadn’t asked “Developers” for comment.

PS: Yes, there is a HUGE difference between the two. I have worked with some who are AMAZING programmers, but would NEVER be able to write/design a large app that would work. (read: unscalable, buggy mess…kind of like your typical large scale php app

I don’t have time to go into masses of detail, but:

i.e.1 2/3 steps would not use the word “efficient”. The word would most likely not be in the top 10. 98% of the code you write need not be performant, but thread safe, well laid out, DRY, proper exception handling, (unit) tested etc.

i.e.2
“you need to include some common concepts like Class,”
yes…well…
Architecture and best practice would at least make a showing….

i.e.3 “The Most fun part in programming is Debugging.”
NO!! Maybe for a “programmer”/script monkey/etc.
Unit testing was invented BECAUSE of this. If you said your favourite thing about programming is debugging, I would NOT HIRE YOU. (yes, I have hired many people before for myself and companies I work for)
Unless it was for a testing team, of course!

i.e.3
It wouldn’t all be about the language. I know about 16 languages to various degrees. They are all just tools. The principles behind their best practice are FAR more important.

“Developers!! Please let me know your thoughts on this…”

Done.