When will I be a good programmer?

[Sebouh]

Ok, i was thinking about this the other day, and i thought i'd ask here. I'm still a newbie programmer cause i only know a little JAVA and C. But i don't only learn programming languages, i learn theory too. I've learn about computer architecture, algorithm analysis, and all that stuff that you get at the university.
My question is, when will i be considered as a good programmer. Or how deep should my programming knowledge be to start working in a company. When do I "stop" and say i know "enough"?
So for you guys who already have jobs as developers or engineers, what languages do you know and how much?
Discuss...

[Loismustdie129]

I don't know about hard facts or jobs, but my dad always told me that you never know enough about anything to stop learning. I guess you develop and learn new things all your life.

Basically what I think, and how I learn, is that I never know everything and that I barely know anything. I jump from there and never stop. I know this doesn't help but, I like philosophy so I always delve deep into a question.

[Ganon11]

"When will I be a good programmer?"

Does it matter?

I didn't think I was 'good', but apparently I'm able to answer 80% of the questions in the C++/C forum. I didn't think I was good, but I scored high enough on a standardized test that I have the option of skipping an entire year of programming courses in college.

Let other people decide if you are 'good', but continue to learn so that you will be considered good.

[DeMan]

Firstly as the previous posters have said, "good" depends on definition.

I had two Epiphanies, where I realised I was a better programmer than I though. The first was after 2nd year University. After getting a Distinction in a core topi (Data Structures and Algorithms), I still though "it was a fluke" because I didn't really think I understood much of it. Having run out of things to read, however, I revisited the text-book from the course (on public transport, to kill the boredom) and suddenly realised exactly where the Distinction had come from, I actually UNDERSTOOD a lot of what was in the text -> soemtimes you learn without really realising.

The second experience I had, was comin g to this forum for a question (which I don't think I ever asked, nor can I remember what it was). I came accross a post I thought (from the tile) might be similar, and soon realised it wasn't. It was a question, however, that I felt I could answer. -> there are always (or close enough to always) people less experienced than you. If you feel you have an answer to a question, share it....aside from all else, I have found I have learnt by answering questions, sometimes because I deliberately look things up, othertimes because I read what someone else has written, and sometimes because thinkiong about someones problem helps me to expand my knowledge.


According to Industry, the biggest factor is experience. You need education to develop initial ideas and theory, but it isn't (IMHO) until you work in the industry, that you really start to refine the skills you need. Basically at UNI you learn the theory, and (as with any work) in your first months in a job you develop much of the skill that you will rely on throughout your career.

[willakawill]

I started programming professionally the same day that I started learning. I had no idea about asp and websites and forms etc. but I was getting paid to write them. My policy in everything is to say yes and worry about how to do it later.

This field is full of bluffers (I include myself). You don't need to know a lot. You must have the right attitude. There are enough website tutorials and books and people willing to help to keep you going through any problem if your attitude is right. Be fearless if only because there is nothing to fear.

[r035198x]

There are people who have been programming for more than 5 years and still are not good. If you want to be a good programmer, write lots of code using the best programming practices all the time.

[MMcCarthy]

Moving to Software Development Forum.

[DeMan]

I'm guesing programming must have something to do with software development.... .

[Banfa]

When do I "stop" and say i know "enough"?

You don't, because if you do you will start going backwards because the computer industry is moving forwards, if you stand still you will be left behind.

Several years experience will help, when I look back at the things I did in my 1st 5 years I often find things I would do differently now.

And finally being able to do a good imitation of a cow (or some other farmyard animal) can't hurt.

[MMcCarthy]

I'm guesing programming must have something to do with software development.... .

The idea is that general (non-technical) but on topic discussions will be placed here.

[AdrianH]

A "good" programmer knows the full life cycle of developing an app and knows how each is done:

1. Concept
   Important as it will start the ball rolling as to what is wanted. Not necessarily the job of the programmer though.
   
2. Gather Requirements
   A "good" programmer asks (others or themselves) what is needed now and possibly in the future (to allow for design growth).
   
3. Design
   Programming (developing) is one thing, but if you are asked to solve a problem by writing a programme and you just start to programme. You're in for trouble.
   
   With a design, you make a specific goal, a target to attain. It will give you a structured outline as to what to do and how the system is broken down. It will also give you a means to give a more accurate timeline to your boss too.
   
4. Develop
   Programming is child’s play. It is just a bunch of logical statements, executed in sequence.
   
   Don’t get me wrong, I’m not dissing those who just programme; there are some who know the ins and outs of how something can be done and how to use certain libraries to get things done faster. But when you have to debug, or maintain it later, you or your team had better have done more than just the programming, or else you will not know when you are finished (achieved the original goal).
   
5. Test (Unit/System)
   Testing a unit is to ensure that the code will work in the rest of the system. This limits the places where problem can occur.
   
   System testing a much bigger task, but can be less of a problem if Unit Testing is done.
   
6. Debug
   This is done in response to both Unit and System Testing. If the system is designed well, then this should be a piece of cake. This is because a good design breaks down the problem into small, almost trivial units, and will sometimes allow you to track it down without even looking at the code but just the design.
   
7. Document (Design/Unit/System/User)
   Documentation is key to any project. Without documentation, you have nothing to refer to but the code, and if it isn't working, you are guessing as to what it is supposed to do.
   
   With a Design document, you should be able to write a preliminary User document to tell the user how to use the app. However, if this is a library and not an app, this is not necessary as the user will not see the internals.
   
   Documentation for a Unit and the System can be embedded in the code as comments. There are document extractors which can be run on the code to make a pretty book or web site.
   
8. Maintain
   With all the stuff you have done, and the documentation that is available, maintenance should be a breeze. If something is added to the project problem, then figure out how it is to be added to the Design and document it.

Requirements Gathering and Designing are critical stages for writing a good code. These give you a target and set the pace of the entire project. Only in the most simplest of programmes (a one - ten liner) will you not need these and this is only because these are one shot deals, where Maintenance is not an issue.

A “good” programmer may not know how to do everything here, but the more you know, the better the salary you can demand. Some of these sections can be delegated to others as well, making this a team effort working in parallel.

If you know how to do all of this, you’re better than a “good”, you’re “Grrrrrrrrrrrrr eate” (I hope Kellogg’s doesn’t sue me :)). It may even put you in to the Engineer class, something that I personally am trying to aspire to.


Adrian

[enreil]

I think this is by far a distinguishing factor of a 'good' programmer. Without solid requirements, a programmer is most likely wasting his or her time. It seems that almost invariably users change their minds or have expectations of the system that are not clearly articulated beforehand. The programmer may write excellent code that does what he/she thinks the application is supposed to do, but if those tasks don't do what the user needs them to do, much time and money have been wasted, and the programmer may be looking for another job.

A "good" programmer asks (others or themselves) what is needed now and possibly in the future (to allow for design growth).

[DeMan]

I'll be a good programmer tomorrow, I'm enjoying being a BAD one too much today.

[Sebouh]

Thanks for the replies.
But just to clear out some things i said: I know i should never stop or else I'll go back, but what i meant was when do i feel comfortable enough to work in an industry and actually develop a software? I know I'm not ready now, but when i graduate will i be ready? Maybe I'm worrying too much...if I won't be ready what about my friends? I really feel I'm better than most of them cause i have less problems with programming assignments all the time, but it still worries me that i don't know the languages enough. When i look at job requirements from time to time, all i see is expected to know this language...i never see expected to know the development cycle or whatever. And my teachers won't teach me languages (they do, but as part of the course topic), so i have to learn them on my own. But how much do i learn, till i drop dead? Till i know the basics? I don't wanna get hired and find out I'm not ready for the job. I know i can always learn later, but that's doesn't put me in a secured position, nor helps increase my self confidence.
What do you guys thing?

[DeMan]

When I completed my studies I found I didn't 'feel' qualified, and was a little aprehensive when I first started to work in the industry.
It is important to remember that Universities/Colleges have been around for a long time (and usually pride themselves on their reputation). This means when they give you a piece of paper saying you are qualuified as something, you probably are.
Often, you won't actually realise how much you have learnt, ubntil you are given the opportunity to apply that knowledge. Sharing answers on forums (like this one) can help you to realise what you actually have learnt, and 'hobby programming' may also help. Getting work, however, is the biggest factor, and you will find that most employers are used to training people fresh from studies, and you should fit in fairly quickly (and probably realise that you know all those thiongs you thought you didn't).....