next »

[Oddball]

I code, therefore I am.

[gimymblert]

I always made the distinction between coding and programming:

Coding: the act of typing the program and maintain the readability.

Programming: designing the program and the structure of the code.

But i would also make a difference between coder and programmer.
I would call myself more a coder than a programmer:

Coder: person who can program but not necessarily well, generally autodidact or force by situation. Code tend to be messy, not well organize and not efficient.

Programmer: person who know he in and out of programming and language, produce well organize and efficient code most of the time.

[Aik]

Programmer is probably less ambiguous.  My previous job was doing programming at a non-profit medical research firm, and they kept talking about "coders."  It turns out that in their particular research area people did something called "coding" which was completely unrelated to computers or programming.  Took me a few months to figure that out.

Yeah - my sister had a job as a 'coder', which basically involved watching psychological research videos and analysing/tagging them for what emotions and behaviour the people in them were expressing at a given time.

Still, in context of IT, they're completely interchangeable.

[LemonScented]

Although I've always thought that the two terms were interchangeable, I used to prefer "coder" to "programmer" because it implied something less formal, someone willing to play fast and loose with the rules to do cool stuff, a maverick - compared to a guy who followed procedure and did stuff by the book, getting results but essentially being a bit dull. It was quite an internal distinction, and one I didn't really put into words.

Now, I still consider the terms interchangeable, but now to me they both mean "someone who writes code/programs", as contrasted "engineer", and these days I'm drawn more towards that word because although it doesn't rule out a willingness to hack or bodge a part of a job, it's someone with a deeper understanding of overarching systems and practises, someone with a better sense of discipline and craft. I guess I just got bit in the ass too many times by my own youthful codery hacks to think that it's still cool to be a maverick in the way one writes one's code.

Also: Get off my lawn! 

[Core Xii]

To me the distinction is that a "coder" is someone who can code (and in all like-hood does so) but a programmer does it professionally with a certain degree of experience and the right mind-set.

That is why I don't like to call myself a programmer, even though I am most definitely capable of writing code and indeed do so professionally; But I lack the patience of programming all the boring routines your average program requires. In this respect I'm more of a coder.

Programming: designing the program and the structure of the code.

Now that's the software engineer, the person who decides how the program will be made, but doesn't actually write it. He divides it into modular pieces and gives them to the programmers. In small enough teams this is probably the one and the same person, as is true in my case.

[lansing]

one is slang for the other.

[Jason Bakker]

I use them fairly interchangeably - my job description is "Programmer", but I'd call myself a coder. That said, I could see coder casting a wider net, into people on the more casual side of cod-er-programmi-er--

Now I'm just confused 

[Mikademus]

Coding: the act of typing the program and maintain the readability.

Call he who does this coder if you will. Or programmer. Synonyms.

Programming: designing the program and the structure of the code.

This is software design or software architecture.

Coder: person who can program but not necessarily well, generally autodidact or force by situation. Code tend to be messy, not well organize and not efficient.

Programmer: person who know he in and out of programming and language, produce well organize and efficient code most of the time.

If this is how you see it, more power to ya. But using it that way and expecting ppl to share your notions is inviting misunderstanding.

[StudioFortress]

Programming: designing the program and the structure of the code.

This is software design or software architecture.

It really depends tho. If it's for structuring the whole project, for ensuring a teams body of code all fits together then I'd agree this is an architectual job. But I'd expect a good programmer to be able to think ahead for designing and planning how he should structure his own code (even if it's just quickly in his head).

Architect can also refer to more abstract duties then how to structure code; like deciding what technologies to use (software and hardware), and deciding which sub-projects get the green light and which don't and why (but more from a technical point of view, like giving the ok to a project because it will reduce build times).

But this is all very subjective.

[Klaim]

How is called someone who write Excell (VB) Macros?










 

[lansing]

How is called someone who write Excell (VB) Macros?
 

business analyst?

[StudioFortress]

How is called someone who write Excell (VB) Macros?
 

business analyst?

I used to work at a bank. Most of the BAs there could write some VBA, but typically weren't very good and usually ended up asking a developer to finish the work for them (simply because they never programmed). People tend to underestimate VBA thinking it's a kiddies language for just doing a few tricks in Excel. But most of the VBA work I had to do usually involved lots of database interaction with pages of SQL, interacting with third party apps, and downloading and processing data for generating data files or reports.

I also had to write lots of Java, and I found those tasks were longer but a lot easier then the VBA ones.

So I'd easily include a VBA programmer as a coder, programmer or software engineer.

[gimymblert]

Coding: the act of typing the program and maintain the readability.

Call he who does this coder if you will. Or programmer. Synonyms.

Programming: designing the program and the structure of the code.

This is software design or software architecture.

Coder: person who can program but not necessarily well, generally autodidact or force by situation. Code tend to be messy, not well organize and not efficient.

Programmer: person who know he in and out of programming and language, produce well organize and efficient code most of the time.

If this is how you see it, more power to ya. But using it that way and expecting ppl to share your notions is inviting misunderstanding.

I'm aware in conversation it's not that way it is just internal reference