Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

Education Java Programming

Ask Slashdot: "Real" Computer Scientists vs. Modern Curriculum? 637

Posted by timothy
from the onions-in-those-days-were-called-zumboes dept.
An anonymous reader writes At work yesterday, I overheard a programmer explaining his perception of the quality of the most recent CS grads. In his opinion, CS students who primarily learn Java are inferior because they don't have to deal with memory management as they would if they used C. As a current CS student who's pursing a degree after 10 years of experience in the IT field, I have two questions for my fellow Slashdoters: "Is this a common concern with new CS grads?" and, if so, "What can I do to supplement my Java-oriented studies?"
This discussion has been archived. No new comments can be posted.

Ask Slashdot: "Real" Computer Scientists vs. Modern Curriculum?

Comments Filter:
  • by 0xdeadbeef (28836) on Wednesday August 06, 2014 @02:06PM (#47616269) Homepage Journal

    Those who can write in Java, and those who can write Java.

    Or those who can write in C#, and those who can write the .NET runtime.

    Or those who can write in PHP, and those who can create PHP. Wait, those are the same.

    You get what I'm saying. The programmers who whine about requirements to understand low-level memory management are in the first category, and their knowledge and skills are laughable compared to the kind of programmers who get hired by the likes of Google, Apple, and Microsoft.

    Stop trying to pretend you're as good. If you were as good you'd be doing something interesting instead of slapping together enterprise bloatware.

  • by Guy Harris (3803) <guy@alum.mit.edu> on Wednesday August 06, 2014 @04:00PM (#47617205)

    What's the difference in the behavoir of the unary & op?

    If you've declared int foo[17], then &foo is an expression of type "pointer to array of int", not "pointer to int" or "pointer to pointer to int" or any other pointer type.

No problem is insoluble in all conceivable circumstances.