Just to muddy the waters further... :)
I was in "in the thick of it" as far as early PCs (Atari 800,
Apple II, TRS-80, IBM PC, etc...) back in '79 due to my father
sending me to a private boys-only school (which I don't recommend,
BTW :) ), where they had, first, a TRS-80 Model 1, then an Apple ][+.
I learned BASIC on both, moving on to 6502 assembler on the ][+.
That started a long road of programming for me; various dialects
of BASIC, LISP, Fortran, Pascal, PL/I, 6502/65816, 68000, and Vax/VMS
assembler, Logo, C/C++, REALbasic (which I consider different than
the previous dialects as they weren't OO), VB 6 and .Net, and a
smattering of Unix shell scripting, Forth, PIC & Atmel-SX assembler,
C# and ObjC.
Eventually I dilly-dallied around in college ('cuz I couldn't make
up my mind what Major I wanted...) First it was Biology, then
CompSci, then EE (and graduated with a BS in Electrical Engr.) I
currently work at Royal Management/RBS Computers as the head (and
only) programmer. I refer to myself as a software engineer by
experience, but an EE by degree. In any case, I consider both to be
"engineering", as they have to do with synthesis and analysis of
complex systems.
CompSci comes first, and - for me, anyway - deals with the theory;
data structures, algorigthms, Big-O notation and efficiency, computer
architecture (Von Neumann vs. Harvard, parallel, distributed, etc...)
and so on. That gives on the tools ones needs as an engineer for the
analysis and synthesis stuff.
Just another 2 cents into the wishing well there...
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|