Computer Programming vs. Computer Science

i'd say computer programming is the application and coding of computing languages, whereas computer science is developing these languages and the mathematical stuff involved.


__________________
star trek rulez
 
Last edited:
Maybe I should think about it more. But, off the cuff: computer programming is the application and implementation of algorithms. Computer science is the study and development of algorithms.
 
It's similar to chemistry vs chemical engineering. Chemists formulate spiffy new materials. Chemical engineers figure out how to produce those on large scale for cheap.
 
if you suck at math, then computer science is not for you.

Not necessarily true. I know someone who claims he sucked at math and hated it but was a computer science major and now makes his living as a self employed programmer, after being an adjunct programming professor at a University in the DC metro area (I am beginning to think he lied to me, lol).

I also sucked at math and was a CIS major. While that does not entail as much math as CS I did have to do my fair share of calculus. My derivatives business class was also all math and fricking math derived models. Lets just say I knew where my tutoring center was!
 
what is the difference between someone who has a calculator and someone who knows math? programming is a tool, science is the knowledge.
 
I was under the impression computer programming was more application while computer science was more theory.
 
I was under the impression computer programming was more application while computer science was more theory.

Bingo, imo!

I went the CIS route in college instead of CS.

I had more business classes, the same amount of programming classes, less "theory" classes, more *nix classes, and a ton less math classes.

I look back I believe it was the right decision. I love what I do and I love the business aspect of it.
 
The guy who knows math knows how to think. The guy with the calculator doesn't necessarily know what to do with it.

"Math" as in a collection of known formulas isn't whats important, it's the analytical mathematical mind, developed by learning math, that is important.

The skills in decomposing a real-world problem into tasks that can be solved with a computer are nearly identical to the skills in modeling a real-world problem to be solved mathematically, in my opinion.

what is the difference between someone who has a calculator and someone who knows math? programming is a tool, science is the knowledge.
 
Math is definitely one of the more important aspects of computer science. I know at my university, CIS students only had to go through Calculus I while the CS students (like myself) had to go through linear algebra and differential equations.
 
If it's down between the two, I'd pick the harder route -- you're more likely to learn a lot and push your limits. This is all personal opinion though about college.
 
Computer programming degrees are focused on training graduates in using programming languages to write code for software, whereas a computer science degree goes much deeper and focuses on the theory behind computing. While a programming degree will be much more application-oriented, computer science will have more to do with theory, mathematics, algorithms, etc. Most CS degrees also teach programming!
 
I was under the impression computer programming was more application while computer science was more theory.

This is it. I just got my Master's in Comp Sci at the end of May, and I can tell you that practical programming was NOT a major focus of the curriculum (both undergrad and grad). Its theory and low-level (as in the kind of hardware-software interactions that operating systems are responsible for) applications of said theories. This isn't necessarily BAD though. It actually makes you better equipped for practical programming because it desensitizes you to the semantics of any particular programming language. It teaches you to think in a much more general, algorithmic way. By doing so, you wind up not caring so much about the particular tools you're handed because the same, basic principles always apply.

The pure math aspect wasn't terrible. We were required to take up to Calculus II but we didn't realy use anything beyond Calculus I, and even thats a stretch. Its not really about crunching numbers, but analysis. So things like Discrete Math, algorithm design, performance, and computational complexity take precedent. None of these really require complex mathematics.
 
It varies heavily by school imo a CS degree that prepares you in the sense of general programming is good, however I think they are doing you an injustice if you don't get enough hands on time. I think the best slogan is learn by doing a ton of theories and studies don't make up for actually performing the task.

If the theory is too heavy I don't consider that a good school just my opinion but from my internships and experience outside of college holds pretty true. They train you for the high level design, but the reality is almost everyone starts as a hands on function tester.
 
The pure math aspect wasn't terrible. We were required to take up to Calculus II but we didn't realy use anything beyond Calculus I, and even thats a stretch. Its not really about crunching numbers, but analysis. So things like Discrete Math, algorithm design, performance, and computational complexity take precedent. None of these really require complex mathematics.
I only have four courses left for my bachelor's in computer science and my school required math up to linear algebra. We didn't use calc II/III much, but linear algebra was used extensively in the graphics class I recently took.

Like others have said, regardless of the program you choose, each university/college will have different requirements. If it is an ABET-accredited program, at least you know the cirriculum is solid and worthwhile.
 
I only have four courses left for my bachelor's in computer science and my school required math up to linear algebra. We didn't use calc II/III much, but linear algebra was used extensively in the graphics class I recently took.

Like others have said, regardless of the program you choose, each university/college will have different requirements. If it is an ABET-accredited program, at least you know the cirriculum is solid and worthwhile.

We had some flexibility in that. Linear Algebra was an option but I chose another track. UCF is ABET-accredited. These are the current program requirements for C.S. (under the Course Requirements tab obviously) if anyone is interested:

http://www.eecs.ucf.edu/index.php?i...rgraduate/computerscience#Course-Requirements

I'm not shilling for my school. Really. ;)
 
That's partially correct. I've seen mathematics offered as both in most universities. Also, if we're going to split hairs, then all "sciences" are liberal arts since you can get a BA in physics, chemistry, or biology.
 
That's partially correct. I've seen mathematics offered as both in most universities. Also, if we're going to split hairs, then all "sciences" are liberal arts since you can get a BA in physics, chemistry, or biology.

See jimmyb's comment. Science was traditionally considered a liberal art, though has since been moved to its own "thing" in many universities.
 
What are the applications of each? and what makes them different?

I had an instructor that saw computer scientists as the guys in the white lab coats that designed systems and never touched a keyboard. The guys on the keyboards were the programmers.
 
I had an instructor that saw computer scientists as the guys in the white lab coats that designed systems and never touched a keyboard. The guys on the keyboards were the programmers.

Hard to agree with that assessment.
 
I generally see computer science as a theoretical discipline for computation, while programming is a vessel of carrying out observations and experiments for said theory.
 
I took computer science in college and it was essentially general computers but mostly programming. But there was also networking, system administration etc... basically overall usage of computers, it does not really specialize in anything specific. oddly, we never touched hardware though. And I suck at math. I had trouble with the 3 math courses but the other courses had no complicated math so I aced most of it. Cisco I had a bit of trouble with mostly because it's lot of memorization of information you'd just lookup in the real world.

Even when programming for real, you don't normally touch complicated math, it's mostly just basic algebra. Unless of course you are writing a program that needs to do lot of math, like a game, but even then it's not that hard since the computer does the hard work of actually calculating everything, you just tell it what to calculate and how.
 
What are the applications of each? and what makes them different?

1: "Software Engineer". No one will take you seriously if you call yourself a computer programmer.

2: Computer Science is the over-arching study of all things computers, which includes but is not limited to programming.
 

I think it's because today "computer programmers" are nothing more than code monkeys that get handed already solved solutions and software designs, and the "programmers" merely transcribe the idea into code.

It really does not take much skill if the design is already written for you and most of this work is being outsourced. Its like taking a detailed story outline and being the one who types it up.

A Software Engineer needs to be able to come up with a solution to the problem itself. He must know how to code as well because he has to keep in mind what kinds of things are possible in code and what languages and technologies to include in his designs and solutions. He must understand how the systems work together and what types of design patterns will work to solve the problems.

Would you rather be the author who gets to dream up the story, the characters and the plot? Or would you rather be the typist who merely transcribes the details into words.

Most Software Engineers do start out programming from designs written up by the engineers and architects but most don't want to be doing that forever. Engineering is problem solving and once you have been coding for a couple years you want to be able to have the skill-set to move to engineering and architecture or you will be replaced by a new young guy who has some basic coding ability.
 
Last edited:
I think it's because today "computer programmers" are nothing more than code monkeys that get handed already solved solutions and software designs, and the "programmers" merely transcribe the idea into code.

It's really does not take much skill if the design is already written for you and most of this work is being outsourced. Its like taking a detailed story outline and being the one who types it up.

A Software Engineer needs to be able to come up with a solution to the problem itself. He must know how to code as well because he has to keep in mind what kinds of things are possible in code and what languages and technologies to include in his designs and solutions. He must understand how the systems work together and what types of design patterns will work to solve the problems.

Would you rather be the author who gets to dream up the story, the characters and the plot? Or would you rather be the typist who merely transcribes the details into words.

Most Software Engineers do start out programming from designs written up by the engineers and architects but most don't want to be doing that forever. Engineering is problem solving and once you have been coding for a couple years you want to be able to have the skill-set to move to engineering and architecture or you will be replaced by a new young guy who has some basic coding ability.
Interesting perspective, and several of your points emphasize (or are benefited from) proper hiring practices and evaluations.

Part of the problem I see with judging a person by their title is that we, as an industry, do not do enough to uniformly qualify what a job title means. Judging a person strictly by title is not guaranteed to be effective in hiring/project goals. You still need to look at personal and work history and interview a potential candidate to determine how accurately the person selected their self-assigned job title.
 
Last edited:
Interesting perspective, and several of your points emphasize (or are benefited from) proper hiring practices and evaluations.

Part of the problem I see with judging a person by their title is that we, as an industry, do not do enough to uniformly qualify what a job title means. Judging a person strictly by title is not guaranteed to be effective in hiring/project goals. You still need to look at personal and work history and interview a potential candidate to determine how accurately the person selected their self-assigned job title.

Software Engineers are the people who actually know how to develop code. These are the heavy hitters, the ones who understand how the system they code for works. They understand how the software and hardware interact, and understand how to build a software platform for the system environment that is being used.

Point being, NEVER LABEL YOURSELF A "Computer Programmer", as thats the quickest way to show you don't have a clue how to program beyond basic Windows applications.
 
Software Engineers are the people who actually know how to develop code. These are the heavy hitters, the ones who understand how the system they code for works. They understand how the software and hardware interact, and understand how to build a software platform for the system environment that is being used.
Both "software engineers" and "computer programmers" should know what their efforts are targeting.

Point being, NEVER LABEL YOURSELF A "Computer Programmer", as thats the quickest way to show you don't have a clue how to program beyond basic Windows applications.
I'd consider that label as being a junior developer, and not necessarily as a negative consideration or warning sign.... unless you are not interested in hiring a junior developer.

Regardless, a screening and interview would be required to determine whether it is a reflection of history/experience or a legitimate warning sign.
 
Last edited:
Regardless, a screening and interview would be required to determine whether it is a reflection of history/experience or a legitimate warning sign.

You assume that any resume with "computer programmer" instead of "software engineer" makes it past the software that screens resumes, which I can assure you will not happen.

Seriously, stop debating this point. Start using "software engineer".
 
You assume that any resume with "computer programmer" instead of "software engineer" makes it past the software that screens resumes, which I can assure you will not happen.

Seriously, stop debating this point. Start using "software engineer".

What about software developer?
 
You assume that any resume with "computer programmer" instead of "software engineer" makes it past the software that screens resumes, which I can assure you will not happen.

Seriously, stop debating this point. Start using "software engineer".
Resume scraping software is still mostly run by non-developers entering keywords. They're not going to filter their search criteria by grey-area nomenclature, when work history and interviews are more effective at getting placements.

But the main point is that this isn't a debate -- I already understand the differentiation you're trying to make between the two labels. The problem is that the differentiation(s) is subjective and non-standardized. Even the concept of applying "engineer" to computing professionals historically raised eyebrows and disdain from other engineering fields that are grounded around constructed physics. You can even add other one-off similarities, such as what noobman pointed out. So until we can get consensus between ourselves, as an industry, then we can't expect others to follow along.
 
Resume scraping software is still mostly run by non-developers entering keywords. They're not going to filter their search criteria by grey-area nomenclature, when work history and interviews are more effective at getting placements.

But the main point is that this isn't a debate -- I already understand the differentiation you're trying to make between the two labels. The problem is that the differentiation(s) is subjective and non-standardized. Even the concept of applying "engineer" to computing professionals historically raised eyebrows and disdain from other engineering fields that are grounded around constructed physics. You can even add other one-off similarities, such as what noobman pointed out. So until we can get consensus between ourselves, as an industry, then we can't expect others to follow along.

I'm just trying to tell you how things work in the real world.
 
Back
Top