Every job I have had has been maintaining and extending other peoples code. No
particular problem, so every situation has its own flavour of coding standards
and practices.
I have also written my own software from scratch too, and its not so much
different – when I reopen it some years later its the same job figuring out
what the programmer was doing – only that programmer was me. Sometimes I have
almost no recollection of the particular code so it might as well be written by
someone else, or I look at it and know I would never do it that way again...
Gary’s idea of code buddy is good, and as solo programmers we already do that
for each other – although its mainly for reassurance for clients as I would
never want to have to configure his rats nest of servers, and he wouldn’t want
to learn the intricacies of legal trust accounting (including mortgage compound
interest calculations all done with integer arithmetic). So far us old
bastards just keep on going and churning out working code, and no intention to
stop (so far anyway). 20000+ lines of code in the first part of this year I am
proud of.
From: Leigh Wanstead
Sent: Thursday, December 4, 2014 3:16 PM
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] Risk Management Plan
To be honest, it is not easy to maintain someone else's code. Rewrite the
source code will be easier than read someone else's code.
Regards
Leigh
On 4 December 2014 at 10:35, Cameron Hart <[email protected]>
wrote:
Hi John
You have had a lot of good answers but no one has yet mentioned that the risk
you are trying to manage is your clients risk, not your own. It is their
responsibility therefore and it would be usual for them to “cover the cost of
covering the risk”.
If you attempt to cover all of your clients risks you will be using your
capital (or risking your assets) to support their business, and you will
struggle to grow your own business.
Instead I suggest you put the responsibility back on the client and ask them
to sign up to a support plan with regular monthly payments which can give you
the confidence to employ another developer so their risk is reduced. This is
an investment by the client in you for their own benefit.
Cameron Hart
Flow Software Limited
PO Box 302 768, North Harbour
P
+64 9 476 3569
Auckland 0751, New Zealand
M
+64 21 222 3569
www.flowsoftware.co.nz
E
[email protected]
This message is intended for the addressee named above. It may contain
privileged or confidential information. If you are not the intended recipient
of this message you must not use, copy, distribute or disclose it to anyone.
P Please consider the environment before printing this email
From: [email protected]
[mailto:[email protected]] On Behalf Of John C
Sent: Wednesday, 3 December 2014 11:59 a.m.
To: 'NZ Borland Developers Group - Delphi List'
Subject: [DUG] Risk Management Plan
Hi all.
One of my clients is expanding their business (thanks to my software;-) and
asked me about a Risk Management Plan in case I would disappear, fair enough.
Me, myself and I are only a small company (as many of you might be too), so
no in-house backup developers available.
Has any of you any experience or ideas regarding a Risk Management Plan for a
one man band?
Thanks
John Sunshine
_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: [email protected]
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [email protected] with
Subject: unsubscribe
--------------------------------------------------------------------------------
_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: [email protected]
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [email protected] with
Subject: unsubscribe_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: [email protected]
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [email protected] with
Subject: unsubscribe
