By pheaven
via programmersheaven.com
Published: Jan 16 2008 / 07:46
What does it take to be a good programmer, and are computer science courses providing that to today’s students? This post takes a quick look at the key things that really should be on a computer science course, and discusses what the overall aim of the course should be: not just turning out code monkeys in today’s hot languages, but scientists who can effectively use (or create) the tools and languages that are available in a couple of decades time.
-
Reducing Firefox startup I/O in libxul.so
-
there's a major security flaw in Android design
-
Cloud Standards Customer Council Forms Security Working Group and Initiates Work on Service Level Agreement Guidance Document
-
Wyse CEO to Discuss Leading Trends in Mobility and Cloud Computing at the Stifel Nicolaus Technology & Telecom Conference 2012
-
Chrome on android, finally!
-
An Eight in a Million chance
Comments
gfxpulse replied ago:
Hrm, I am recently out of school, and my alum taught all the things mentioned as being 'missing' from students educations. After first year, we didn't go back to java again, except when given freedom to choose languages. Algorithmic complexity and proofs involved in calculating said complexity were thoroughly covered. Assembly was covered, operating system level programming, you name it. I'm unsure what other schools are teaching, but at least a few out there aren't in a rut as this article states.
kieronwilkinson replied ago:
I know my university course still teaches 68000 Asm, Occam (parallel, CSP-like), Miranda (Haskel-like pure functional), Java, Prolog and SQL in their course. A very wide understanding of computer languages is necessary . This is in the UK, maybe it is different in the US. Also, I don't agree that dynamic typing particularly adds much if the above categories of languages are taught (especially strongly-typed OO, parallel and functional).
Voters For This Link (11)
Voters Against This Link (4)