Bachelor of Arts in Computer Science, or just change the curriculum?

Bachelor of Arts in Computer Science, or just change the curriculum?

  • Comments 1

Alfred Thompson discusses the concept of a Bachelor of Arts, Computer Science, and I have been working with CSUDH, and the CS department is applying for a curriculum based using a Bachelor of Arts type of approach.  But the issue is the idea that students learning object oriented languages are not learning how to "really do computer science", which is not true.  The issue is that the professors have not been able to keep up with the recent changes in technology related to software engineering and software architecture tools. 

Students get what the needs are, and when allowed to have their own head with respect to what is being taught in class, they will tend to act like normal workers and researchers.  In this case they respond by working together and supplying mutual answers, but due to the honor code, that type of effort is difficult to reward.  This is a mark against the way computer science is taught these days.

I would challenge a professor, perhaps a professor of game technology that isn't on tenure track, tenured or a full time lecturer, which leaves an adjunct professor, at a teaching college to work with the students to design curriculum that they feel would motivate them and to do the best job of preparing for their needs.  In my view an adjunct would have to do so, since it is likely if they lose their next contract, it will not harm their career.  Also, the class term would have to be long enough to allow the student feedback, and for the professor to respond.

Conclusion: Great post by Alfred.

Leave a Comment
  • Please add 8 and 4 and type the answer here:
  • Post
  • Alfred Thompson discusses the concept of a Bachelor of Arts, Computer Science, and I have been working

Page 1 of 1 (1 items)
Generic Content

Legal Note:

  1. The author, Sam Stokes, is an employee of Microsoft
  2. There is no guarantee that anything I write is correct, I do try to make sure that what I write is correct.
  3. Use anything written in this blog at your own risk
  4. Test what I write about before using the information
  • Sometimes posts will disappear because I realized that they really don't fit with the total chaos of what I write about
  • Links are tested and available on date of publication, what others do with their links are out of my control

Restrictions:

  • Whatever I write on this blog is unedited by management or anyone, which should be obvious from the randomness of the blog.  I simply write about things I like.
  • Microsoft does not restrict me in anyway, so I generallyblather about whatever I want to.
  • For personal reasons I will not write about:
    • Company confidential stuff, mainly because Microsoft is more transparent than any company I have ever worked for.
    • Other people unless they give me permission to write about them