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.