l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2002 Nov 13 21:09

The following is an archive of a post made to our 'vox mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
[vox] Dealing with "God Coders" (was: cheating suspected)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vox] Dealing with "God Coders" (was: cheating suspected)

If commented code was rewarded equally with features, lack of bugs,
ability to work well with others, and be on time with deadlines and
projects, then there might be more drive for coders to comment.

However, the western work ethic of sacrificing the future work and support
(TCO) for higher immediate productivity reigns supreme.

Employees who do not comment code increse the company's *need* for the
employee, and effectively enhance job security. An employee would be hard
to convince to alter their action to benefit the company and risk thier
own safety.

I say, force people to cross support each other's projects and then
provide a peer based forum for live review of coder's work. The manager
can pick the code they dislike the most (maybe something from 6 months
back) and the put the coder on the spot with zero notice of which code
they would be reviewing.

Then the coder must explain their old project to their peers.

Their God status quickly is lost if they dont remember and have no comments.

IBM has employed this with their coders. It is brutish, but quickly gets
people to make code that at least *they* can understand with zerto prep
time 6 months later. ]:>

Bob said:
> I sure hope you take credit off for lack of comments and poor
> formatting. My pet peeve is that the people teaching people to code
> ignore the fact that the code should be readable and heavily commented.
> True, it's overkill for one liner's but once the habit is learned (to
> not comment) it's really hard to break.
> Then, as an employer, I have to baby sit these self-proclaimed code gods
> who think their code is perfect without comments and everyone else is a
> fool..
> It's been my take (after taking many programming courses) that
> commenting and layout is not on very many professors agenda.  I
> personally think that it's because they've never had to find a bug at
> 3am in some X year old legacy code..
> bobm
> ----- Original Message -----
> From: "Peter Jay Salzman" <p@dirac.org>
> To: <vox@lists.lugod.org>
> Sent: Wednesday, November 13, 2002 12:36 PM
> Subject: Re: [vox] code sleuths needed - cheating suspected
>> just for the record, i don't want to get anyone in trouble.  i don't
>> plan on making it "official" or anything.  i just don't want to give
>> credit for the homework if it was copied.
>> so i guess maybe it's silly to even worry about it in the first place.
>> pete
>> _______________________________________________
>> vox mailing list
>> vox@lists.lugod.org
>> http://lists.lugod.org/mailman/listinfo/vox
> _______________________________________________
> vox mailing list
> vox@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox

vox mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.