From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} hire a programmer or company?
Date: Thu, 31 May 2012 00:58:18 +0200 [thread overview]
Message-ID: <20120531005818.496cc0f1@khamul.example.com> (raw)
In-Reply-To: <CAN0CFw1MS4yRbYBD8jQcfcZhihtB0GJ5kPp2GO1cTLktepzg4A@mail.gmail.com>
On Wed, 30 May 2012 02:11:54 -0700
Grant <emailgrant@gmail.com> wrote:
> >> > You can get away with almost anything except these two things:
> >> >
> >> > Do not micro-manage
> >> > Do not tell them how to do what they do
> >>
> >> Could you give me an example of this last one?
> >
> > - I see you are using Perl with hashrefs to do function xyz. Have
> > you considered (i.e. I would like you to) using
> > $INSERT_SOMETHING_HERE?
>
> So if I see a way that their coding could be improved (faster
> execution, greater legibility, etc) I just keep quiet about it?
>
> > - Wanting to personally review the code often. I've seen some
> > managers want to do this daily.
>
> How often should I read their code? I was planning on reading it a
> lot.
Perhaps I was too literal. Those examples should be read in the context
of obsessively fiddling with someone else's work. Alternatively, doing
those examples and not producing anything worthwhile from doing it.
Code reviews and suggestions are valuable, but there's a time and a
place and a forum for them. All productive teams eventually reserve a
time slot for review and demos of running code. You and the entire team
can and should discuss optimizations then.
Let me put it another way - you likely don't like it if someone else
fiddles with your work while you are trying to do it, or gives
"helpful suggestions" while you are trying to concentrate. All I'm
saying is to avoid doing that to others. Good old common sense will
tell you when this is happening - you already know how to do it, no
need to analyze the thing any further than that
--
Alan McKinnnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2012-05-30 23:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 11:26 [gentoo-user] {OT} hire a programmer or company? Grant
2012-05-26 11:44 ` Florian Philipp
2012-05-27 6:22 ` Grant
2012-05-27 8:27 ` Alan McKinnon
2012-05-27 8:51 ` Florian Philipp
2012-05-27 16:09 ` Grant
2012-05-27 16:35 ` Volker Armin Hemmann
2012-05-27 16:53 ` Grant
2012-05-27 21:18 ` Alan McKinnon
2012-05-28 15:30 ` Michael Orlitzky
2012-05-27 21:18 ` Alan McKinnon
2012-05-28 16:00 ` Grant
2012-05-28 20:50 ` Alan McKinnon
2012-05-29 8:34 ` Grant
2012-05-29 12:08 ` Alan McKinnon
2012-05-29 17:51 ` Grant
2012-05-29 20:10 ` Alan McKinnon
2012-05-30 9:00 ` Grant
2012-05-29 12:30 ` Pandu Poluan
2012-05-29 13:58 ` Michael Mol
2012-05-29 14:05 ` Michael Orlitzky
2012-05-29 14:37 ` Alan McKinnon
2012-05-29 23:52 ` Peter Humphrey
2012-05-30 9:11 ` Grant
2012-05-30 12:57 ` [gentoo-user] " Nicolas Sebrecht
2012-05-30 22:58 ` Alan McKinnon [this message]
2012-05-31 6:44 ` [gentoo-user] " Grant
2012-05-29 17:02 ` [gentoo-user] " James
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=20120531005818.496cc0f1@khamul.example.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.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