Of all the people I've worked with over the years very few have a degree in computer sciences or related fields.
Most have degrees in physics, mathematics, or chemistry.
A few have more esoteric degrees like biology and business economics.
The few CS grads I have encountered professionaly have often left a less than favourable impression because of their ivory tower attitude towards software development (they never write a line of code, but typically dictate massive and completely unworkable architectures that are beauties of theoretical design but impossible to use).
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337
"Unworkable architectures that are beauties of theoretical design but impossible to use if you do not have a CS degree.
Ok...so i'm a little bias :)
Sauce
Junior Poster in Training
55 posts since Jul 2005
Reputation Points: 10
Solved Threads: 0
>because of their ivory tower attitude towards software development
As I like to say: Good developers look for solutions, good CS graduates look for problems. ;)
Narue
Bad Cop
15,460 posts since Sep 2004
Reputation Points: 6,464
Solved Threads: 1,401
I have not seen a CS degree as a pre-requisite to this phenomenen which I normally see in middleware groups. :)
Which I normally observe as being populated largely by CS grads (at least at the decision-making level) :cheesy:
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337
Hi everyone,
The last thing you need to worry is whether your degree is accredited. What matters the most is what were the modules you learned and were they useful to your own personal knowledge bank and the benefits that it would bring to your carrer and yourself.
What you know is more important than where you are from
Richard West
freesoft_2000
Practically a Master Poster
623 posts since Jun 2004
Reputation Points: 25
Solved Threads: 10