comp.lang.ada
 help / color / mirror / Atom feed
From: taurus!grus!shimeall@lll-winken.llnl.gov  (timothy shimeall)
Subject: Re: Software Engineering Education
Date: 22 Nov 91 18:17:04 GMT	[thread overview]
Message-ID: <3396@grus.cs.nps.navy.mil> (raw)

Has anyone considered the difficulty in even defining what "real world
computing" is, let alone teaching it? How would you provide a willing
university with the information it needs to design a "real world
computing" curriculum?

+ "Real world computing is what my company does" - This works great,
  until your graduates start working for more than one company...

+ "Real world computing is what programmers in general do" - I welcome
  suggestions as to how:
   a) A survey can be conducted to determine what programmers in
      general do (and how the results can be checked to determine
      that the programmers filled them out, not management or 
      clerks);
   b) A source of funding can be identified to pay for the survey
      mentioned in a)
   Note that the net, big as it is, is a biased sample.  People with
   time to spend on netnews aren't likely to be typical programmers.

   Note also that a casual survey of newspaper want ads shows that
   the most-requested types of programmers work in COBOL and RPG
   (Using ads from the San Jose Mercury News, serving most of Silicon
    Valley).  This may suggest that "programmers in general" isn't
   even the correct target, definitional problems aside.

+ "Real world computing is what the top-of-the-line companies do"
   -- this breaks down into two methodological problems: 
   a) How do we identify "Top-of-the-line" companies
   b) How do we get said companies to allow us to identify what
      their programmers do

As one final note, consider a MUCH simpler problem - profiling
CS professors (this is simpler, as the professors wouldn't have to get
an OK from corporate lawyers to describe their working habits).  While 
I've seen figures for average time/week for professors at various levels,
I've never seen figure breaking down what professors do during that time...
-- 
Tim Shimeall ((408) 646-2509)
The proper response to detecting a bug isn't to fix the bug - it's to make 
sure you'll never have to worry about that bug again.  --- Richard Hamming

             reply	other threads:[~1991-11-22 18:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1991-11-22 18:17 timothy shimeall [this message]
  -- strict thread matches above, loose matches on Subject: below --
1991-11-20 23:51 Software Engineering Education sun-barr!cronkite.Central.Sun.COM!newstop!sunaus!assip.csasyd!condor!dave
1991-11-19 16:18 Ray Harwood
1991-11-18 23:05 agate!spool.mu.edu!tulane!uno.edu!JNCS
1991-11-18 17:12 David A. Hasan
1991-11-18 15:45 Bill Yow
1991-11-16 17:02 Gregory Aharonian
1991-11-16 16:37 agate!spool.mu.edu!yale.edu!qt.cs.utexas.edu!zaphod.mps.ohio-state.edu!ca
1991-11-15 19:26 cis.ohio-state.edu!udecc.engr.udayton.edu!blackbird.afit.af.mil!galaxy.af
1991-11-15 19:18 Michael Feldman
1991-11-15 17:33 Dana Newman
1991-07-14  7:40 Orville R. Weyrich
1991-07-09 21:27 cis.ohio-state.edu!magnus.acs.ohio-state.edu!zaphod.mps.ohio-state.edu!wu
1991-07-08 21:44 spool.mu.edu!caen!zaphod.mps.ohio-state.edu!rpi!bu.edu!m2c!risky.ecs.umas
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox