exoduse223
n00b
- Joined
- May 3, 2012
- Messages
- 1
What are the applications of each? and what makes them different?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
if you suck at math, then computer science is not for you.
if you suck at math, then computer science is not for you.
I was under the impression computer programming was more application while computer science was more theory.
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 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.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.
if you suck at math, then non-liberal arts majors are not for you
This is going to shock you, but math is considered a liberal art.
As is science
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.
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.
What are the applications of each? and what makes them different?
Why not?1: "Software Engineer". No one will take you seriously if you call yourself a computer programmer.
Why not?
Interesting perspective, and several of your points emphasize (or are benefited from) proper hiring practices and evaluations.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.
Both "software engineers" and "computer programmers" should know what their efforts are targeting.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.
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.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.
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".
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.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.
LOLI'm just trying to tell you how things work in the real world.
Please, let the n00bie through so that he may enlighten us on the workings of the real world.I'm just trying to tell you how things work in the real world.