You mean the school would have cared that I wasn't attending class and playing Civ II for 8 hours a night. Sweet I might not have failed out then.
Brings a whole new meaning to the calulator attendence that some physics classes were taking.... Ah, the sweet 5 dollars for sitting wide and using TWO calculators on the pop quizes.
The theory and math behind a CS degree help in finding optimized solutions when things go down the drain. To understand state machines and big-O provides insight with creating algorythms as well.
To leave out the math in computer science is to ask an engineer to ignore physics when constructing plans for the building of a sky scraper.
In building a structure....
I like to think of the architech as the one who thinks of an idea, and large how-tos. The engineer to understand the workings of what how-tos are possible, resulting in functional plans. Finally with the contractors/builders who actually build the object.
Notice how some architech schools lack DEEP science and physics for the engineers. They spend more time in art.
The same applies to programming. A lead architech figures out the overall interworkings of object communication. Not much science, but patterns of work flow should be needed.
A software engineer, understands the process of creation, what data structures to use, how the objects actually interact. The nitty gritty.
A programmer knows VI and macros (hehe) for generating tons of implementations fast. Including understanding the API's to know how parts fit together.
Computer science generally covers the architech and engineer rolls.
Note, I don't think any jobs are defined this well
and most everyone must partially fill each roll.
Slashdot Mirror
You mean the school would have cared that I wasn't attending class and playing Civ II for 8 hours a night. Sweet I might not have failed out then. Brings a whole new meaning to the calulator attendence that some physics classes were taking.... Ah, the sweet 5 dollars for sitting wide and using TWO calculators on the pop quizes.
The theory and math behind a CS degree help in finding optimized solutions when things go down the drain. To understand state machines and big-O provides insight with creating algorythms as well. To leave out the math in computer science is to ask an engineer to ignore physics when constructing plans for the building of a sky scraper.
In building a structure.... I like to think of the architech as the one who thinks of an idea, and large how-tos. The engineer to understand the workings of what how-tos are possible, resulting in functional plans. Finally with the contractors/builders who actually build the object.
Notice how some architech schools lack DEEP science and physics for the engineers. They spend more time in art.
The same applies to programming. A lead architech figures out the overall interworkings of object communication. Not much science, but patterns of work flow should be needed.
A software engineer, understands the process of creation, what data structures to use, how the objects actually interact. The nitty gritty.
A programmer knows VI and macros (hehe) for generating tons of implementations fast. Including understanding the API's to know how parts fit together.
Computer science generally covers the architech and engineer rolls.
Note, I don't think any jobs are defined this well and most everyone must partially fill each roll.
I would really like to give donations to these organizations as gifts to my friends. Does anyone know how to do this?