And hence somebody became a Expert Developer!!!
-
Bribery and corruption did it for me.
The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
-
Generally, it takes lot of efforts to be into a Elite category of developers. Yes, everything comes from experience, experiments, lot of practice, lot of learning, knowledge sharing, etc etc... But I would like to know what's the main turning point in your life when you felt that you are almost a legend developer or you are close to be called an expert. What it has taken you to reach that great level? What were your unique style of learning, experimenting, role models, best practices that have helped you a lot to become an expert? Your inputs will be of highly importance to me and might help me and others to become a better developer. I always feel happy to be a part of a great developer Community:- CodeProject. Thanks all in advance.
Most great developers don't think they're great. Conversely, most developers who think they're great, aren't. http://www.hanselman.com/blog/ImAPhonyAreYou.aspx[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
How much did it cost you? Where do I pay?
Cornelius Henning Corruption is not the #1 priority of the Police Commissioner. His job is to enforce the law and fight crime. -- P.B.A. President E. J. Kiernan
Brown envelope fulls. In the park, behind the third tree on the left. Password is "Seagull Paté" ;)
The universe is composed of electrons, neutrons, protons and......morons. (ThePhantomUpvoter)
-
Expert: Spurt = small ejaculation, ex = past it. OK, so it works better when spoken than written. Edit: I'll accept it is a crap joke, but spam or abusive? Get a life.
“I believe that there is an equality to all humanity. We all suck.” Bill Hicks
I prefer the version: Ex - Out of date. Spurt - a drip under high pressure.
I was brought up to respect my elders. I don't respect many people nowadays.
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier -
Generally, it takes lot of efforts to be into a Elite category of developers. Yes, everything comes from experience, experiments, lot of practice, lot of learning, knowledge sharing, etc etc... But I would like to know what's the main turning point in your life when you felt that you are almost a legend developer or you are close to be called an expert. What it has taken you to reach that great level? What were your unique style of learning, experimenting, role models, best practices that have helped you a lot to become an expert? Your inputs will be of highly importance to me and might help me and others to become a better developer. I always feel happy to be a part of a great developer Community:- CodeProject. Thanks all in advance.
Watch, learn and apply. Know your basics. The biggest problems are just collections of smaller issues. I think by now you see that the consensus is that you should always be learning. Some very, very good programmers who I would consider "expert" have replied to your post and stated that they themselves wouldn't call themselves "expert". You will know that you are getting pretty good yourself when other programmers start coming to you for help. My member page says it about the best I can: "The more I develop the more I realize how little I do know and seek to discover cooler, better and faster methods to implementing new ideas."
It was broke, so I fixed it.
-
Nepotism and cronyism are the simplest ways for the uninitiated, however, that's not always a possible channel. Even then your status will mean nothing outside of that organization. If you're taking the term expert literally, experts generally function with their skill almost without even thinking. Hopefully you're an expert at walking by now. There's a widely publicized concept that it takes 10000 hours of performing an activity to become an expert, and that's not a guarantee. With that out of the way, the short answer is: you will need to practice. -You may get there by just performing your regular weekly job, only if you are lucky enough to get enough variety to keep challenging you. Because if you are writing programs at the same level of difficulty for 5 years (~2000hrs/year * 5yrs => 10000hrs), you will only be an expert at writing that type of basic program. -You will need to constantly seek more challenging tasks. Once you get comfortable at a certain level, improve the difficulty of what you are trying to learn. -Seek mentor's. The resident expert's and build a relationship with them. Learn as much as you can from them. Ask questions. -Teach other's. You'll find out how quickly you understand a topic, based on how well you can intelligibly talk about it. You will get there faster if you actively seek topics that you enjoy, continue to learn about them AND practice. One final piece of wisdom: you will know you are on the right track, when you begin to realize that you don't know as much as you think you do, and you become aware of what knowledge exists that you have not yet learned. That will help you strengthen on your weak areas, and keep you learning. This relates to what an earlier poster said, to paraphrase, if you think you are an expert, then you aren't.
To know and not do, is not yet to know
-
Most great developers don't think they're great. Conversely, most developers who think they're great, aren't. http://www.hanselman.com/blog/ImAPhonyAreYou.aspx[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Thanks Richard.
-
Watch, learn and apply. Know your basics. The biggest problems are just collections of smaller issues. I think by now you see that the consensus is that you should always be learning. Some very, very good programmers who I would consider "expert" have replied to your post and stated that they themselves wouldn't call themselves "expert". You will know that you are getting pretty good yourself when other programmers start coming to you for help. My member page says it about the best I can: "The more I develop the more I realize how little I do know and seek to discover cooler, better and faster methods to implementing new ideas."
It was broke, so I fixed it.
Yes. Agreed, thanks.
-
awesome. At least someone did try to give honest input rather than making fun of an honest question :-)
Thanks, Milind
Thanks for considering it as a honest question..
-
Generally, it takes lot of efforts to be into a Elite category of developers. Yes, everything comes from experience, experiments, lot of practice, lot of learning, knowledge sharing, etc etc... But I would like to know what's the main turning point in your life when you felt that you are almost a legend developer or you are close to be called an expert. What it has taken you to reach that great level? What were your unique style of learning, experimenting, role models, best practices that have helped you a lot to become an expert? Your inputs will be of highly importance to me and might help me and others to become a better developer. I always feel happy to be a part of a great developer Community:- CodeProject. Thanks all in advance.
well i'm still a student but i think that the first step should be finding something "major or speciality" and work on it till you feel that you mastred it, then you move on to something else in the end you'll find yourself knowledgable in lots of majors Which basicly is becomming an (expert) :cool:
-
Generally, it takes lot of efforts to be into a Elite category of developers. Yes, everything comes from experience, experiments, lot of practice, lot of learning, knowledge sharing, etc etc... But I would like to know what's the main turning point in your life when you felt that you are almost a legend developer or you are close to be called an expert. What it has taken you to reach that great level? What were your unique style of learning, experimenting, role models, best practices that have helped you a lot to become an expert? Your inputs will be of highly importance to me and might help me and others to become a better developer. I always feel happy to be a part of a great developer Community:- CodeProject. Thanks all in advance.
Becoming an expert at anything takes time, not talent. Someone has done a study of what it takes to become an expert at lots of things and calculated that 15,360 hours will get you to be an expert in computer programming. There was some other report a few years ago that basically said 10,000 hours of deliberate study will make you an expert at anything.
“I believe that there is an equality to all humanity. We all suck.” Bill Hicks
-
Generally, it takes lot of efforts to be into a Elite category of developers. Yes, everything comes from experience, experiments, lot of practice, lot of learning, knowledge sharing, etc etc... But I would like to know what's the main turning point in your life when you felt that you are almost a legend developer or you are close to be called an expert. What it has taken you to reach that great level? What were your unique style of learning, experimenting, role models, best practices that have helped you a lot to become an expert? Your inputs will be of highly importance to me and might help me and others to become a better developer. I always feel happy to be a part of a great developer Community:- CodeProject. Thanks all in advance.
It depends on the view. To my friends i´m an expert in programming, to you a bloody beginner. You can improve by learning, experimenting and watching other, only to mention a few ways. Also don´t be shy to ask questions or answer some if you think you can. To become a better developer write code and think how you can improve the lately written.
-
Generally, it takes lot of efforts to be into a Elite category of developers. Yes, everything comes from experience, experiments, lot of practice, lot of learning, knowledge sharing, etc etc... But I would like to know what's the main turning point in your life when you felt that you are almost a legend developer or you are close to be called an expert. What it has taken you to reach that great level? What were your unique style of learning, experimenting, role models, best practices that have helped you a lot to become an expert? Your inputs will be of highly importance to me and might help me and others to become a better developer. I always feel happy to be a part of a great developer Community:- CodeProject. Thanks all in advance.
Hi, I thought about what an expert would be, and for me it represents someone who would write clean and efficient code as others would write a letter and knows what He/She is doing. I think an Expert is someone who has a solid understanding how computer hardware works and how to do tasks that are hard to accomplish with higher programming languages (assembler). He/She also I guess has also knowledge of the Inner workings of the (different) operating systems , network protocols and how network devices function. To write good code an extensive knowledge of a higher level programming language is required. For me an Expert is also someone who has good knowledge on Design Patterns (GOF, Fowler, Evans) to understand how to build software (and how others have builded it (Architecture)). Reading what I wrote I have a long way to go to be an expert.
With friendly greetings,:) Eric Goedhart
-
Mohammed Hameed wrote:
Can you please englighten what can be those important steps/routes to become a very good developer in your view.
That's easy: practice, practice, practice.
Use the best guess
I've heard that Carnegie Hall is a good place to do that, but I can't seem to figure out how to get there. Do you know how I can get to Carnegie Hall?
-
Not sure if understand what this means but I still take a shot. That's just me with a lot more attractive personality which does not exist due alcohol deficiency in the body.
"Bastards encourage idiots to use Oracle Forms, Web Forms, Access and a number of other dinky web publishing tolls.", Mycroft Holmes[^]
Argh! I've read your signature... and I've thought you were Mycroft Holmes... :sigh: And, as it is well known Sherlock like to drink... Sorry!
[www.tamautomation.com] Robots, CNC and PLC machines for grinding and polishing.
-
I've heard that Carnegie Hall is a good place to do that, but I can't seem to figure out how to get there. Do you know how I can get to Carnegie Hall?
-
-
well i'm still a student but i think that the first step should be finding something "major or speciality" and work on it till you feel that you mastred it, then you move on to something else in the end you'll find yourself knowledgable in lots of majors Which basicly is becomming an (expert) :cool:
Thanks a lot for your explanation. Being a student you have very good thoughts. Keep it up. :thumbsup:
-
Becoming an expert at anything takes time, not talent. Someone has done a study of what it takes to become an expert at lots of things and calculated that 15,360 hours will get you to be an expert in computer programming. There was some other report a few years ago that basically said 10,000 hours of deliberate study will make you an expert at anything.
“I believe that there is an equality to all humanity. We all suck.” Bill Hicks
Thank you!
