public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Richard Villa <rvilla1@swbell.net>
To: speakup@braille.uwo.ca
Subject: Re: Computer Science
Date: Thu, 14 Mar 2002 17:02:55 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0203141700130.4756-100000@dhcppc2> (raw)
In-Reply-To: <Pine.LNX.4.31.0203141959580.30744-100000@c213-100-2-58.swipnet.se>

I wonder when the last time anyone did any real programming not just 
coding using a language like assembler.

I don't believe anyone knows what programming is until they have to 
write in an assembly language.
On Thu, 14 Mar 2002, Johan 
Bergström wrote:

> In sweden the universities teach lisp/ada/c/c++ and other programming
> languages. Not IDE's. At least the ones I know about. There are separate
> windows programming classes, at some places, which are specially for
> people who enjoy that kind of stuff, where they debug the windows kernel
> using softice and stuff like that. They run most of their server in a *nix
> based enviroment.
> 
> johbe
> 
> On Thu, 14 Mar 2002, Thomas Ward wrote:
> 
> > Amanda so true. I am a CS student myself and I know exactly what my college
> > teaches. They teach you Visual Basic, html with Javascript,  Visual C++, MS
> > SQL, MS Access, and you get the point.
> > Almost everything is now Microsoft this, and Microsoft that. In fact all the
> > computers in the CS labs have Windows NT on them.
> > They use to offer Unix C programming courses, but I don't think they do any
> > more. Been a while since I stepped into a class room, and when I went
> > through they were just making the switch to MS everything.
> >
> >
> > ----- Original Message -----
> > From: Amanda Lee <amanda@shellworld.net>
> > To: <speakup@braille.uwo.ca>
> > Sent: Thursday, March 14, 2002 9:36 AM
> > Subject: Re: Computer Science
> >
> >
> > > Nope, Unix, Mainframes aren't standard anymore.  The college grads we get
> > > these days at Verizon have no clue what Unix or Mainframes are all about.
> > > Everything is taught on a Windows-based Platform.  I believe JAVA is
> > > taught, probably Visual Basic, Maybe sometimes C Language but usually C
> > > Plus Plus which was actually abandoned in the project I work on for
> > > straight C Language.
> > >
> > > I would think in the future though, there will be a change back to at
> > > least teaching Linux since it can run on a less expensive platform.  It's
> > > pretty disgraceful how the content of Computer Sciences education has been
> > > degraded and these kids coming out have an ego bigger than life and think
> > > they can take on the World in a day!
> > >
> > > They really struggle when they can't understand how to program and the
> > > quality of code coming out is pretty awful.  There is even this mentality
> > > in the Corporate World which indicates that one can learn everything they
> > > need to on the job and yet they can't figure out why  there are so many
> > > problems with efficiency and the costs resulting from poor efficiency.
> > >
> > > Amanda Lee
> > >
> > >
> > >
> > > On Thu, 14 Mar 2002 jwantz@hpcc2.hpcc.noaa.gov wrote:
> > >
> > > > Hi Chris,
> > > > I'm not going to get involved in the "bookshare wars', but since you
> > were
> > > > chastizing others on this list because most people use WINDOWS and not
> > > > linux, I think its only fair to point out that your computer science
> > > > department is very nonstandard.  Though I am a meteorologist, not a
> > > > computer science person, I know many computer science students in the
> > past
> > > > and the present.  Teaching WINDOWS programming is very nonstandard.  I
> > > > would guess that at least 90 percent of the schools teach programming on
> > a
> > > > UNIX variant of some kind.  In the past thre was a fair amount of people
> > > > using VMS.  However, a lot of beginning C and C++ classes did use
> > > > Turbo/Borland.  WINDOWS programming is much more difficult than UNIX
> > > > programming, so I suppose you are to be congratulated for making it
> > > > through such a tough curriculum.
> > > >
> > > >      Jim Wantz
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > >
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
It is better to give then to receive.  You don't believe me, just ask a 
boxer.

Richard





  parent reply	other threads:[~ UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 jwantz
 ` Amanda Lee
   ` Thomas Ward
     ` Johan Bergström
       ` Igor Gueths
       ` Richard Villa [this message]
         ` Amanda Lee
           ` Bruce Noblick
             ` Richard Villa
               ` Amanda Lee
         ` jwantz
     ` Igor Gueths
       ` Alex Snow
     ` jwantz
   ` jwantz
   ` Gregory Nowak
   ` Victor Tsaran
     ` Amanda Lee
       ` jwantz
         ` Amanda Lee
           ` jwantz
             ` Amanda Lee
     ` Brian Borowski
 Ameenah Ghoston
 ` Amanda Lee
 ` Janina Sajka
 computer science Saqib Shaikh
 ` jwantz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.33.0203141700130.4756-100000@dhcppc2 \
    --to=rvilla1@swbell.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).