From: Clem Cole <clemc@ccc.com>
To: Norman Wilson <norman@oclsc.org>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Anyone ever heard of teaching a case study of Initial Unix?
Date: Wed, 3 Jul 2024 11:52:30 -0400 [thread overview]
Message-ID: <CAC20D2NrBORVf7Jiek0KznE39sH2Wr=vmZ2GROGyaOq2R+8RcA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2OYSM_5OciHNfSPixtLLcqB7C5U+jbY6wk5z1FtF1_yyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2732 bytes --]
s/be far/be fair/
Sorry, Grammerly rewrote that and I missed it with my dyslexia.
ᐧ
ᐧ
On Wed, Jul 3, 2024 at 11:45 AM Clem Cole <clemc@ccc.com> wrote:
>
>
> On Wed, Jul 3, 2024 at 10:46 AM Norman Wilson <norman@oclsc.org> wrote:
>
>> Steve Jenkin:
>>
>> I've never heard of a Computer Science or Software Engineering program
>> that included a `case study' component, especially for Software
>> Development & Projects.
>>
>> [...]
>>
>> How about the course for which John Lions wrote his famous
>> exegesis of the 6/e kernel?
>>
>> Norman Wilson
>> Toronto ON
>
> This >>might<< be far from an OS >>developer<< perspective [*i.e*., for a
> practitioner of SW development for an OS]. However, I'm quite sure it is
> the same thing. In Lion's case, he looks at the code and final system in
> the same manner to examine the technical output/result (a complete
> timesharing system than in "modest HW", that a single person could
> understand as it was less than 9000 KLOCs). This is like an architecture
> class might take apart drawings of Notre Dame Cathedral to examine how the
> structure was developed to carry such huge loads of stone, wood, and lead
> but still allow so much light in the building (such as the class on my CMU
> roommates who became a restoration architect for buildings like 30th Street
> Station in Philadelphia). Case studies (which originated at HSB and are
> now de rigor in most B-schools) look at the choices made, given a set of
> initial conditions to create a (business) result [positively and
> negatively]. What could be learned from the conditions, choices, and
> results so that feature (business) leaders can recognize what might not be
> obvious? The idea is that you are teaching managers about choices
> that change/predict a future outcome. This is not the same as field
> practitioners trying to make a structure/machine/program to >>operate<< to
> do some design function.
>
> So, the place where a case study for SW projects (using books like
> Mythical Man Month) would be helpful is an in-software engineering course.
> Writing an HSB style case for something like UNIX, or Tenex or maybe
> Oracle; particularly to compared to something like Brook's book would be
> fascinating to read, I'm not sure Lion's text qualifies. I think the
> content of such a "case" would be quite different.
>
> Again, it comes back to what "success" is. If success is defined as
> winning the market, OS/360 was a huge success, as was DOS. But neither
> would I consider a success from the standpoint of building something that
> future generations of programmers would want to learn to emulate.
> ᐧ
> ᐧ
>
[-- Attachment #2: Type: text/html, Size: 5600 bytes --]
next prev parent reply other threads:[~2024-07-03 15:53 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 14:46 [TUHS] " Norman Wilson
2024-07-03 15:45 ` [TUHS] " Clem Cole
2024-07-03 15:52 ` Clem Cole [this message]
2024-07-03 16:12 ` Chet Ramey via TUHS
-- strict thread matches above, loose matches on Subject: below --
2024-07-05 13:20 Douglas McIlroy
2024-07-03 4:51 [TUHS] " sjenkin
2024-07-03 5:02 ` [TUHS] " Al Kossow
2024-07-03 6:46 ` arnold
2024-07-03 14:04 ` Clem Cole
2024-07-03 15:22 ` Theodore Ts'o
2024-07-03 15:36 ` Larry McVoy
2024-07-03 14:59 ` Marc Rochkind
2024-07-03 23:35 ` G. Branden Robinson
2024-07-04 13:00 ` Marc Donner
2024-07-03 9:04 ` A. P. Garcia
2024-07-03 15:17 ` Vincenzo Nicosia
2024-07-03 15:35 ` Marc Donner
2024-07-03 17:39 ` Jon Forrest
2024-07-03 17:49 ` segaloco via TUHS
2024-07-03 18:16 ` Erik E. Fair
2024-07-03 19:58 ` Rich Salz
2024-07-03 23:15 ` Dave Horsfall
2024-07-03 23:23 ` Marc Donner
2024-07-03 23:26 ` Rik Farrow
2024-07-04 23:26 ` Dave Horsfall
2024-07-03 15:37 ` Al Kossow
2024-07-03 16:01 ` Al Kossow
2024-07-03 16:05 ` Warner Losh
2024-07-03 23:29 ` Marc Rochkind
2024-07-03 23:50 ` G. Branden Robinson
2024-07-04 8:23 ` Vincenzo Nicosia
2024-07-04 20:34 ` Nevin Liber
2024-07-04 20:44 ` segaloco via TUHS
2024-07-04 21:41 ` sjenkin
[not found] ` <7AC009E5-C985-44AD-A55E-E0BFC05CDD31@serissa.com>
2024-07-05 9:41 ` Steve Jenkin
2024-07-05 9:47 ` Steve Jenkin
2024-07-05 0:03 ` Stuff Received
2024-07-05 0:12 ` Larry McVoy
2024-07-05 2:24 ` Adam Thornton
2024-07-05 2:42 ` Bakul Shah via TUHS
2024-07-05 7:13 ` arnold
2024-07-05 7:42 ` Bakul Shah via TUHS
2024-07-05 8:20 ` arnold
2024-07-05 8:52 ` G. Branden Robinson
2024-07-05 7:36 ` Dave Horsfall
2024-07-05 10:18 ` Peter Yardley
2024-07-07 22:00 ` Dave Horsfall
2024-07-07 23:28 ` Brad Spencer
2024-07-08 6:17 ` Dave Horsfall
2024-07-08 6:27 ` Lars Brinkhoff
2024-07-08 6:51 ` Dave Horsfall
2024-07-08 9:36 ` David Arnold
2024-07-08 6:59 ` arnold
2024-07-08 13:22 ` Larry McVoy
2024-07-08 15:37 ` Al Kossow
2024-07-08 17:22 ` Tom Lyon
2024-07-08 17:04 ` Clem Cole
2024-07-08 15:28 ` Brad Spencer
2024-07-08 15:33 ` Al Kossow
2024-07-08 0:21 ` John Levine
2024-07-08 0:35 ` Dave Horsfall
2024-07-08 12:29 ` Peter Yardley
2024-07-05 16:40 ` Jon Steinhart
2024-07-06 13:20 ` Dave Horsfall
2024-07-05 0:08 ` Marc Rochkind
2024-07-04 1:53 ` John Levine
2024-07-04 2:59 ` segaloco via TUHS
2024-07-04 6:53 ` Rob Pike
2024-07-04 15:07 ` Larry McVoy
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='CAC20D2NrBORVf7Jiek0KznE39sH2Wr=vmZ2GROGyaOq2R+8RcA@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=norman@oclsc.org \
--cc=tuhs@tuhs.org \
/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 NNTP newsgroup(s).