I agree with Riven, even if you don't complete a project, what you are considered depends on the amount of time you spend doing it.

There are many people who write computer programs, but do not have a degree. Just because they do not have a degree, it doesn't make them any less of a programmer. So how can you say that if someone doesn't finish a computer program, they are not a programmer. Whether you finish something or not, it depends on the amount of time spent doing it.

A person who spends a little bit of time is usually an amateur, beginning programmer. Even if they don't finish anything, they still have the title because they spent the time to try. It is the same with any profession, you really don't need a certificate. You just need to spend a little bit of time and you'll be recognized with the title. The only difference here is how much time you've spent, the more experience you have... the deeper the title meaning. Like the difference between an expert, intermediate, or beginner. It is all based on time.

When you type lot of semicolon. Because normal computer user wont use semicolon that much.

But... but... WHAT IF I WANT TO USE PYTHON!!?!?!?!

@Oskuro:I like to program, but I get tired of doing it 45+ hours per week. Part of what I loved so much about making hobby games before I went professional was that games are so multi-discipline; I spent a lot of time on the art, music, design, etc. as well. So I could get breaks from the programming. There is absolutely satisfaction to the problem solving, writing a smart algorithm, etc., but goodness is it a drag to be all that I do. Half of my brain is unused.

Most people I know working as Software Engineers see programming as a necessary evil they must endure until they can become managers.

Ugg. Exact reason why I stopped working for corps. Program less and replace that by soul sucking activities like yet more meetings, moving people from important roles to making coffee, firing people, cancelling projects and/or jumping up-and-down on peoples heads. Management sucks.

Yeah, I'm actually very lucky that my current job keeps presenting interesting programming challenges. Other jobs I've had bore me to tears, and it really had an impact on my productivity and mental health.

Now I'm in a rare position where once I'm off work, I have enough ideas boucing around my head I can easily get coding my own projects.

Roquen said:

Quote

Management sucks.

Yeah, it's far from what people believe it to be, but that's the thing, most people focus on what they see as problems now, and fail to see the difficulties of a future position. I have the feeling I'll be dragged kicking and screaming into a management position in the not so far future (mainly when I'm the most experienced developer around and the new hires need to be herded into usefulness)

Cero said:

Quote

Nah, you are what you do.

Well, of course, but I was under the impression that this thread aimed at being a bit more philosophical about it. On the other hand, I call myself a "programmer", while most of my colleagues prefer to refer to themselves as "developers" or "computer technicians" (Actually the spanish generic word for Computer Science people is "Informaticos", not sure what the english term is). That was my point about "liking" it.

Riven said:

Quote

You are considered a programmer if you have once killed the illusive artifically sweetened kangaroo elf.

Writing HTML is writing a logical script of commands, which a parser executes to do something intended.Its as much programming as Java or C++ is.

I think the question here is more: "Who do I consider 'Da Cool' Programma"

In the end only someone writing in Assembler is a true programmer, since he is creating the actual machine program. (with some convenience functions)(the most bare being someone using a HEX Editor to write programs)

Am pretty sure we all know the biggest secret of knowing who's a programmer...

Having a beard or long hair... Or both & if not that cloths that just say "meh".But yeah if not they things I think you can tell if you start having a conversation about programming what tools, engine you use etc.

Scripter: Scripts around, familiar with 1 programming language. *Able to make a calculator*Coder: Does code for programs or for the web. Familiar with at least 2 programming languages. *Able to make a networked game*Programmer: Same as Coder but also knows the fundamentals of how computers work. Years of experience with at least 2 languages and familiar with others. *Able to make a compiler*Hacker: Knows all of the above + intimately familiar with unix and years of experience as a sysadmin.

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org