|
Realize that where all getting old? 
|
|
|
|
|
The Klingon kind of.
|
|
|
|
|
|
Today is a good day to code!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
I think of myself as Pete, don't really care about the job label.
This space for rent
|
|
|
|
|
Just Pete? Not Pete O'Hanlon?
"Hi. My name is Pete, Pete O'Hanlon. You can call me Pete".
|
|
|
|
|
 Same here. You get an email from me it says Joe. I get one from someone sitting 5 feet from me I get a 10 line email signature, chain or not.
|
|
|
|
|
Software Engineers design and implement entire software application systems. Programmers/developers take those designs and code individual units of work from those designs/specs. Programmers/developers rarely design.
So, if you are designing things, then you are an engineer/architect, if you are strictly just coding to someone else's designs/specs, you are a developer/programmer.
Simples.
Edit: Semantics. Some would argue that "developers" develop software, similar to engineer/architect. With that said, I guess the word "developer" is interchangeable here. - depends on your employer.
modified 8-Nov-17 5:00am.
|
|
|
|
|
Ok, so far. Let's add that you ar a manager or a wizard if you get things done by waving your hands.
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
True, of course, but I have never worked in a situation where the two were separated. In all my roles the engineers designed and coded the product.
|
|
|
|
|
Yep. My experience as well, and seems to be the current trend. IMHO, I think it has to do with more shops are going "agile" so to speak, and there is less up front time spent purely in design. So, your "coders" have to know design as well (design & code as you produce and deliver). That is my high level opinion about that - don't know if it is accurate or not.
|
|
|
|
|
In agile there are product architects who decide on the overall direction for design.
Software developers then take this general direction hint and write the code.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
Current job title is "Software Development Engineer, Staff". We pretty much do it all. We have Business Analysts who do no coding but come up with the requirements and tell us what the forms should look like. For the most part as long as I get a steady paycheck and benefits I really don't care what they call us as long as it's nothing derogatory.
Scott
|
|
|
|
|
CodeZombie62 wrote: as long as it's nothing derogatory.
That's always nice. Don't call me Lead Jackass. 
I actually take the approach that Pete mentioned in his reply.
|
|
|
|
|
It could be DevOps if programming is accompanied by related activities like use case analysis, testing, deployment, monitoring, updating, etc ...
BR
|
|
|
|
|
DevOps was a term coined by f***ing geek ass nerds who want to sound like SpecOps. Take that devops crap and flush it down the toilet.
|
|
|
|
|
Oh no ... my favourite term gets bashed ... It could also be "programmer++"
|
|
|
|
|
Based on how many coders don't seem to have any idea about SysAdmin or Ops work, I completely disagree.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
So, what's wrong with SysAdmin and Operations? Why does it have to be "DevOps"? Oh, that's right, it sounds cooler. 
|
|
|
|
|
|
Nothing is wrong with those, but they're not developers, and vice-versa.
There may be a branding element to the term, but I think it does describe a different enough job to warrant its own title.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
For me the basic rule to separate those both terms is:
Programmer : Codes stuff (Mostly on base of plans or decisions)
Engineer : Developes/Designs (Keeping track, planning, managing, defining Architecture etc.) stuff + programming
Therefore i see myself as SW Engineer.
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
HobbyProggy wrote: Programmer : Codes stuff (Mostly on base of plans or decisions)
Engineer : Developes/Designs (Keeping track, planning, managing, defining Architecture etc.) stuff + programming
 IMO, this is the most accurate definition. This description perfectly fits in Agile project development.
Btw, all these related words are more or less same for those who do not know more about Software world. Whatever you say to them, they will just think, we can do anything with computers.
You can have all the tools in the world but if you don't genuinely believe in yourself, it's useless.
|
|
|
|
|
My job has evolved more into the buzz word known dev ops because primary code writing and debugging is becoming a smaller part of my work. Today I struggle with design, app store and deployment, minor but regular server issues, second level customer support and marketing.
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
... my situation is +/- the same ...
Perhaps it would be an idea for a weekly poll on CP, unless we had this one already ?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
, BR