When is learning chargeable to a client?

2003-01-08 Thread Jeff Snoxell
Hi,

I suppose this may be slightly off topic and not really relevant to a mysql 
mailing list, sorry... but...

I've spent the last month getting up to speed with MySQL with much help 
from you guys and Mr DuBois' book. I've done this because an existing 
client of mine has a system which works with a database engine we developed 
in house for cheap and cheerful little database applications but their 
requirements have increased to a point where our little engine is running 
at max throttle. I proposed that I convert their setup to work with MySQL 
and said that I would not charge for my time spent learning how to use MySQL.

My question is: when developing _any_ software it's almost always a bit of 
a learning process. I'm always referring to reference manuals etc. etc. 
whenever I'm developing, even in the languages I'm most familiar with. So 
where do I draw the line?

How can I identify a reasonable point at which it's fair to start logging 
some hours down to my client?

Many thanks,


Jeff Snoxell


-
Before posting, please check:
  http://www.mysql.com/manual.php   (the manual)
  http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php



RE: When is learning chargeable to a client?

2003-01-08 Thread Simon Green
It is up to you, but for a guide have a look at what MySQL training cover
and if you know that then you are up to speed?
Simon

-Original Message-
From: Jeff Snoxell [mailto:[EMAIL PROTECTED]]
Sent: 08 January 2003 09:25
To: [EMAIL PROTECTED]
Subject: When is learning chargeable to a client?


Hi,

I suppose this may be slightly off topic and not really relevant to a mysql 
mailing list, sorry... but...

I've spent the last month getting up to speed with MySQL with much help 
from you guys and Mr DuBois' book. I've done this because an existing 
client of mine has a system which works with a database engine we developed 
in house for cheap and cheerful little database applications but their 
requirements have increased to a point where our little engine is running 
at max throttle. I proposed that I convert their setup to work with MySQL 
and said that I would not charge for my time spent learning how to use
MySQL.

My question is: when developing _any_ software it's almost always a bit of 
a learning process. I'm always referring to reference manuals etc. etc. 
whenever I'm developing, even in the languages I'm most familiar with. So 
where do I draw the line?

How can I identify a reasonable point at which it's fair to start logging 
some hours down to my client?

Many thanks,


Jeff Snoxell


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail
[EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: When is learning chargeable to a client?

2003-01-08 Thread David T-G
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jeff, et al --

...and then Jeff Snoxell said...
% 
% Hi,

Hi!


% 
% I suppose this may be slightly off topic and not really relevant to a mysql 
% mailing list, sorry... but...

*grin*  I agree that it is but at least it isn't a flame war.  This
probably belongs on an independent consultant list, even though you are
working within a company, because of the nature of ongoing learning
without a large infrastructure, but I don't happen to know of one of
those.  [If anyone does, I'd be happy to hear about them, since I am an
independent...  But now we're drifting even further OT :-]


% 
% I've spent the last month getting up to speed with MySQL with much help 
...
% at max throttle. I proposed that I convert their setup to work with MySQL 
% and said that I would not charge for my time spent learning how to use 
% MySQL.

How nice of you.  I don't know that I would go *that* far if the need to
learn something new is driven by a client, but I've come close...  Of
course, there's always the matter of doing whatever it takes to keep the
client happy.


% 
% My question is: when developing _any_ software it's almost always a bit of 
% a learning process. I'm always referring to reference manuals etc. etc. 
% whenever I'm developing, even in the languages I'm most familiar with. So 
% where do I draw the line?

A good question, and a good point.  I'd say to take a look at the sorts
of things you already do and try to quantify how much you do in a time
period (hour, day, month) in a given language (so many lines of php code
or so many tables in a database design or whatever; it will be tricky).
Then apply that same measure to the new language, and evaluate your level
in the same sort of context (how much work you get done in a time period
(and nobody get picky and remind me of the physics definition of work,
OK? :-) versus how much time you're thrashing or reading or thinking).


% 
% How can I identify a reasonable point at which it's fair to start logging 
% some hours down to my client?

You can take two approaches (well, a huge number of them, but I use two
for most things):

- - If it's core learning and no arrangement has been made, then it's on
  your time.  That's just for core learning, though; once you can start
  to do some things the client starts to pay (see next, though).

- - If a learning arrangement has been made, or once you are starting to
  do work for your client even if you're not yet up to expert speed, bill
  them for the proper number of hours but either at a reduced rate or
  with a credit back.  The client needs to see the time you're spending
  and understand some of what's going on, but at the same time shouldn't
  pay the full rate for less-than-full-speed work.

- - Once you're comfortable in the language, reduce the discounts.  When
  you're proficient, stop altogether (discounting/crediting, that is ;-)

Because I started with the discounted-rate model (rather than credits
back), I've evolved to a SysAdmin rate multiplier of 1.0, a php and perl
multiplier of 0.5, and a mysql multiplier of 0.25.  I was doing php (and,
since I was rusty, perl) at 0.25 until recently and have just made the
jump; yay :-)  Meanwhile, if you're tracking your pro-bono and/or learning
time, it may be better for you to credit back the hours because you can
then count up what you've given away.


% 
% Many thanks,

HTH  HAND


% 
% Jeff Snoxell

mysql query,
:-D
- -- 
David T-G  * There is too much animal courage in 
(play) [EMAIL PROTECTED] * society and not sufficient moral courage.
(work) [EMAIL PROTECTED]  -- Mary Baker Eddy, Science and Health
http://justpickone.org/davidtg/  Shpx gur Pbzzhavpngvbaf Qrprapl Npg!

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE+HAg8Gb7uCXufRwARAkL9AJwPedAiCJ1o482xxjed7Znf1tvk5wCghBz4
R6VUhDg7jcs4t4FFE4gLb5U=
=R/XS
-END PGP SIGNATURE-

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php