From this post forward, I will attempt to use the term “Prog” to refer to programmers.
I read a lot of Michael Bolton and I agree, testers are developers too. So are the BAs. Testers, Programmers, and BAs all work together to develop the product. We all work on a software development team.
Before I understood the above, I used the word “Dev” as short hand for “developer” (meaning programmer). Now everybody on my development team says “Dev” (to reference programmers). It has been a struggle to change my team culture to get everyone to call them “programmers”. I’m completely failing and almost ready to switch back to “Dev”, myself. I don’t much like the word, “programmer”…too many syllables and letters.
Thus, I give it one last attempt. “Prog” is perfect! Please help me popularize this term. It’s clearly short for “programmer”, easy to spell, and fun to say. It also reminds me of “frog”, which is fitting because some progs are like frogs. They sit all day waiting for us to give them bugs.
Where do I fit in? I'm a programmer in a testing department who develops automated regression tests :)
Popularize this term? It is ancient! LOL. I understand that developer now encompasses so much more than writing code, but a developer also does more than just write code these days. I did a little web frolicking and found this interesting blog about programmer vs developer vs engineer. Thoughts?
http://ibuilthiscage.com/2008/07/03/developer-vs-engineer-vs-programmer/
Hi Shawn. Ancient? I've never heard anyone use it. Here I thought I coined it. Darn.
Anyway, thanks for the great post. It really made me think... But in the end I arrived back at the same place. I still need a short, one syllable, name to describe those who's main job is to write our product's code.
Hmmm, but what do I call you...can not compute...
Craig, you got me. So true. Test Automation Engineers are programmers too. And so are lots of manual testers who use automation as a helper.
Still, if we differentiate between those who write product code and those who write code to check the product (and I think we should), you my friend, are still a "tester".
Fortunately, for you, testers are way cooler than Progs.
That works for me! Just thought I'd point out the oddball in the testing group.
I don't think it much matters. If you are on teams Like I've been on where everyone is a developer, with different responsibilities? I'm not sure arguing over something like that is worth the effort.
I call my QA team "blame someone else and earn money"