Programmer vs software engineer
-
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.
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.
-
So, you are not the sort this rapper is looking for.[^]
I have lived with several Zen masters - all of them were cats.
-
I continually have to check the details of syntax and stuff when programming. Things like print format specifiers, the syntax of things I havent used for a year or so, and use a calculator to work out bit masks and check my bit wise logic. I can never get it right in my head. I dont remember details. I dont pride myself on that. I spend my time and energy on the big picture. Designing and understanding complex mechanisms. The architecture. The guts of the machine. So I think of myself as a software engineer, not a programmer. How about you lot?
-
I continually have to check the details of syntax and stuff when programming. Things like print format specifiers, the syntax of things I havent used for a year or so, and use a calculator to work out bit masks and check my bit wise logic. I can never get it right in my head. I dont remember details. I dont pride myself on that. I spend my time and energy on the big picture. Designing and understanding complex mechanisms. The architecture. The guts of the machine. So I think of myself as a software engineer, not a programmer. How about you lot?
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.
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
} -
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 fucking geek ass nerds who want to sound like SpecOps. Take that devops crap and flush it down the toilet.
-
Chances are you're just getting old then brother. ;P
Jeremy Falcon
:( Could be.
-
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
-
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.
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.
-
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.
-
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
-
I continually have to check the details of syntax and stuff when programming. Things like print format specifiers, the syntax of things I havent used for a year or so, and use a calculator to work out bit masks and check my bit wise logic. I can never get it right in my head. I dont remember details. I dont pride myself on that. I spend my time and energy on the big picture. Designing and understanding complex mechanisms. The architecture. The guts of the machine. So I think of myself as a software engineer, not a programmer. How about you lot?
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
-
DevOps was a term coined by fucking geek ass nerds who want to sound like SpecOps. Take that devops crap and flush it down the toilet.
-
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.
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
:thumbsup: 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.
-
DevOps was a term coined by fucking geek ass nerds who want to sound like SpecOps. Take that devops crap and flush it down the toilet.
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
-
I think of myself as Pete, don't really care about the job label.
This space for rent
-
I continually have to check the details of syntax and stuff when programming. Things like print format specifiers, the syntax of things I havent used for a year or so, and use a calculator to work out bit masks and check my bit wise logic. I can never get it right in my head. I dont remember details. I dont pride myself on that. I spend my time and energy on the big picture. Designing and understanding complex mechanisms. The architecture. The guts of the machine. So I think of myself as a software engineer, not a programmer. How about you lot?
007 ;)
Latest Article - Class-less Coding - Minimalist C# and Why F# and Function Programming Has Some Advantages Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
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
-
I continually have to check the details of syntax and stuff when programming. Things like print format specifiers, the syntax of things I havent used for a year or so, and use a calculator to work out bit masks and check my bit wise logic. I can never get it right in my head. I dont remember details. I dont pride myself on that. I spend my time and energy on the big picture. Designing and understanding complex mechanisms. The architecture. The guts of the machine. So I think of myself as a software engineer, not a programmer. How about you lot?
-
I continually have to check the details of syntax and stuff when programming. Things like print format specifiers, the syntax of things I havent used for a year or so, and use a calculator to work out bit masks and check my bit wise logic. I can never get it right in my head. I dont remember details. I dont pride myself on that. I spend my time and energy on the big picture. Designing and understanding complex mechanisms. The architecture. The guts of the machine. So I think of myself as a software engineer, not a programmer. How about you lot?
It's not about the abilities of the individual; it's about the criticality of the product. If it's a web site or line-of-business app, it ain't engineering, so don't call yourself an engineer. There are very very few software engineers. I'm a software developer and architect.
-
I continually have to check the details of syntax and stuff when programming. Things like print format specifiers, the syntax of things I havent used for a year or so, and use a calculator to work out bit masks and check my bit wise logic. I can never get it right in my head. I dont remember details. I dont pride myself on that. I spend my time and energy on the big picture. Designing and understanding complex mechanisms. The architecture. The guts of the machine. So I think of myself as a software engineer, not a programmer. How about you lot?
Having a title just means you're still a junior looking for a promotion to the next higher title. My business card doesn't have a title, and I rarely hand one to anybody that does. (Well I do have some old business cards from a previous employer, useful for trade shows where they expect you to provide a card to get in - they're not getting my real card either.)
Installing Signature... Do not switch off your computer.