Programmer vs software engineer
-
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.
-
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 usually introduce myself as a geek. When talking to non geeks. In a company of other geeks I say I do development. I try to leave it at that. Some days I am a strict coder. Some days I am an architect. Some days I am the customer. Most days I am just keep politics from ruining mine and my teams lives. As someone else said. I don't really fit into the current buzzword. I also don't want to be labeled by a buzzword. I can do design work, I can meet with the customer and come up with an overriding solution. I can be put in a corner and given specs and crank out code.
To err is human to really mess up you need a computer
-
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 also call myself software engineer, although, if blundering hacks like us would be held up to the standards of civil engineering, we would all be in jail.
-
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.
I dont have a business card and it wasnt a question about titles, it was a question about mentality.
-
"Jim, for one million dollars, what is your name!"
-
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 dont have a business card and it wasnt a question about titles, it was a question about mentality.
So when you say "So I think of myself as a software engineer, not a programmer" that's not putting a title on yourself/what you do? Okay then, keep going, work hard and you might get there one day.
Installing Signature... Do not switch off your computer.
-
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?
IDE operator
-
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. :doh:
-
eh... I'm whatever the job description says. Just tell me the technologies used and the pay scale. Call me whatever you like, just don't call me late for dinner.
-
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?
Code Monkey?
Someone's therapist knows all about you!
-
I usually introduce myself as a geek. When talking to non geeks. In a company of other geeks I say I do development. I try to leave it at that. Some days I am a strict coder. Some days I am an architect. Some days I am the customer. Most days I am just keep politics from ruining mine and my teams lives. As someone else said. I don't really fit into the current buzzword. I also don't want to be labeled by a buzzword. I can do design work, I can meet with the customer and come up with an overriding solution. I can be put in a corner and given specs and crank out code.
To err is human to really mess up you need a computer
Geeks are circus performers.
-
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?
Everyone at the current gig is called a "software engineer". I don't really care much for titles - I just enjoy getting paid to play with computers all day.
