From: Larry McVoy <lm@mcvoy.com>
To: Larry McVoy <lm@mcvoy.com>, Theodore Ts'o <tytso@mit.edu>,
"tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] CMU Mach sources?
Date: Mon, 24 Jun 2019 21:18:06 -0700 [thread overview]
Message-ID: <20190625041806.GL7655@mcvoy.com> (raw)
In-Reply-To: <20190625005528.GA11929@wopr>
On Mon, Jun 24, 2019 at 05:55:28PM -0700, Kurt H Maier wrote:
> On Mon, Jun 24, 2019 at 05:45:23PM -0700, Larry McVoy wrote:
> >
> > Like I said, I can point anyone at code I wrote as a grad student that
> > while I'm not proud of the style, it has style and it is clean. Just
> > because you are a grad student that doesn't excuse messy code. If you
> > write messy code then you're a bad hire.
> >
>
> This is akin to complaining about laborers not polishing railroad spikes
> before hammering them into the sleepers. It's hard enough to find
> people willing to touch computers at all for grad-student "wages," much
> less ones both capable & willing to be held to production-code standards
> on budgets that barely put food on the table, one fiscal year at a time.
It is not about wages, when I was a grad student I got $16K and had to
pay tuition and rent and everything else out of that.
It's not about money. It's about caring about your craft. I cared,
the people I have worked with in industry cared, if they didn't I
left.
The point I was trying to make was that you can be a student and still
be a pro. Or not. The pros care about their craft. The Mach people,
in my you-get-what-you-paid-for opinion, were not pros. They got a
lot done in a sloppy way and they left a mess.
I don't know how to say it more clearly, there are plenty examples of
students that wrote clean code. Mach was cool, clean code it was not.
next prev parent reply other threads:[~2019-06-25 4:18 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 4:38 Chris Hanson
2019-06-23 5:15 ` Larry McVoy
2019-06-23 8:52 ` Andrew Warkentin
2019-06-23 13:39 ` Jon Forrest
2019-06-23 13:59 ` arnold
2019-06-23 14:03 ` Jason Stevens
2019-06-23 8:04 ` Jason Stevens
2019-06-23 14:54 ` Henry Bent
2019-06-23 21:52 ` Clem Cole
2019-06-25 0:06 ` Larry McVoy
2019-06-25 0:31 ` Theodore Ts'o
2019-06-25 0:45 ` Larry McVoy
2019-06-25 0:55 ` Kurt H Maier
2019-06-25 4:18 ` Larry McVoy [this message]
2019-06-26 23:19 ` [TUHS] Craft vs Research (Re: " Bakul Shah
2019-06-27 0:16 ` tuhs
2019-06-27 17:06 ` Clem Cole
2019-06-25 1:00 ` [TUHS] " Richard Salz
2019-06-25 8:00 ` Kevin Bowling
2019-06-25 12:11 ` Arthur Krewat
2019-06-25 12:17 ` Arthur Krewat
2019-06-26 2:45 ` Kurt H Maier
2019-06-26 2:56 ` Larry McVoy
2019-06-26 15:11 ` Theodore Ts'o
2019-06-26 17:44 ` Larry McVoy
2019-06-26 18:01 ` arnold
2019-06-26 18:18 ` Warner Losh
2019-06-26 19:22 ` Chris Hanson
2019-06-26 19:32 ` Ben Greenfield via TUHS
2019-06-26 20:21 ` Larry McVoy
2019-06-27 0:22 ` Chris Hanson
2019-06-27 1:02 ` Larry McVoy
2019-06-27 1:26 ` Chris Hanson
2019-06-27 4:01 ` Lyndon Nerenberg
2019-06-27 10:34 ` Ben Greenfield via TUHS
2019-06-27 10:59 ` arnold
2019-06-27 11:13 ` Ben Greenfield via TUHS
2019-06-27 11:39 ` arnold
2019-06-27 14:58 ` Warner Losh
2019-06-27 17:25 ` Larry McVoy
2019-06-26 19:30 ` Dennis Boone
2019-06-26 19:25 ` Adam Thornton
2019-06-23 8:27 ` Kevin Bowling
2019-06-25 3:07 ` Gregg Levine
2019-06-25 8:15 ` Kevin Bowling
2019-06-25 18:18 ` Chris Hanson
2019-06-25 20:23 ` Gregg Levine
2019-06-26 1:04 ` Jason Stevens
2019-06-26 0:53 ` Jason Stevens
2019-06-25 7:49 ` Jason Stevens
2019-06-25 7:59 ` Andreas Grapentin
2019-06-23 22:08 Noel Chiappa
2019-06-23 23:54 ` Theodore Ts'o
2019-06-24 17:04 ` Jason Stevens
2019-07-01 13:20 Jason Stevens
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=20190625041806.GL7655@mcvoy.com \
--to=lm@mcvoy.com \
--cc=tuhs@minnie.tuhs.org \
--cc=tytso@mit.edu \
/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).