From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} hire a programmer or company?
Date: Tue, 29 May 2012 09:58:00 -0400 [thread overview]
Message-ID: <CA+czFiDv5J_o6hyjxBdLbZzOz5p2m=b+GD7CrbcOAXTp+wH_JQ@mail.gmail.com> (raw)
In-Reply-To: <CAN0CFw2BGSS6f-Waqh5ttFk6EngTSuF-DsbHOzbY+ZfAmBY4Hg@mail.gmail.com>
On Tue, May 29, 2012 at 4:34 AM, Grant <emailgrant@gmail.com> wrote:
>>> >> I'll be getting my feet wet with this shortly. Any other tips
>>> >> regarding the management of one or more programmers working on
>>> >> various small web projects? Maybe workflow or any key procedures
>>> >> a newbie manager should follow?
>>> >
>>> > 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?
>>
>> - Fiddling with the roadmap. Somehow, this always ends up like the
>> homeowner overriding the architect and trying to get the roof up
>> before the walls.
>>
>> - Giving "advice" on the process such as saying how awesome a concept
>> stakeholders and product owners are in Scrum. But they use
>> ExtremeProgramming.
>>
>> - Wanting to personally review the code often. I've seen some managers
>> want to do this daily.
>>
>> - Get personally involved on their level.
>>
>>
>> All these things class as interference. Managers and owners who do this
>> have miles of justifiable reasons for doing so, but it's always hogwash
>> - they interfere, plain and simple.
>
> This is really interesting to me. Is there a forum/website/book with
> more gritty, practical advice like this on managing programmers?
> These are the kinds of mistakes I will definitely make if someone
> doesn't tell me not to.
>
> Could you tell me really briefly what a manager *should* do?
>
> I think I'll try to manage a single programmer working few hours and
> see how it goes. My asking stupid questions is due to my lack of
> experience and there's only one way to fix that.
I'd probably suggest reading The Mythical Man-Month.
http://en.wikipedia.org/wiki/The_Mythical_Man-Month
--
:wq
next prev parent reply other threads:[~2012-05-29 14:00 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 [this message]
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 ` [gentoo-user] " Alan McKinnon
2012-05-31 6:44 ` 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='CA+czFiDv5J_o6hyjxBdLbZzOz5p2m=b+GD7CrbcOAXTp+wH_JQ@mail.gmail.com' \
--to=mikemol@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