[DUG] Risk Management Plan

stephen at bertram.co.nz stephen at bertram.co.nz
Thu Dec 4 21:33:32 NZDT 2014


While contracting I have found that, while I may disagree with the approach
and/or standards, I have had little difficulty reading and expanding the
existing code base in Delphi.  This is one of the reasons I like the
language as the unit structure gives a lot of clues as to the thinking of
the original programmer (and their competence).

I have also had the (dubious) pleasure of taking over C programs with
little documentation and have found this challenging when the originator
used cryptic naming and multiple indirections, which is against the norm in
the Delphi community.

S0.02

Stephen
---- Original Message ----
From: "John C" 
To: "'NZ Borland Developers Group - Delphi List'" 
Sent: Thu, Dec 4, 2014, 6:00 PM
Subject: Re: [DUG] Risk Management Plan
	Hi Leigh 
	A rewrite could be a major and very costly job. The readability of your
source depends very much on how it has been written. As you (should) know,
it helps (and also yourself!!) when using: 

	·         adequate notes in the source 

	·         having the program divided in multiple functional modules 

	·         using multiple feature related function libraries 

	·         etc. 
	When not using this method (or better) you may find yourself struggling
maintaining your own program ;) 
	John 
	From: delphi-bounces at listserver.123.net.nz
[mailto:delphi-bounces at listserver.123.net.nz] On Behalf Of Leigh Wanstead
 Sent: Thursday, December 4, 2014 3:17 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  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 (tel:%2B64%209%20476%203569)  
	Auckland 0751, New Zealand    

	M    

	+64 21 222 3569 (tel:%2B64%2021%20222%203569)   
	www.flowsoftware.co.nz  (http://www.flowsoftware.co.nz)   

	E    

	cameron.hart at flowsoftware.co.nz  (mailto:cameron.hart at flowsoftware.co.nz) 

	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: delphi-bounces at listserver.123.net.nz
(mailto:delphi-bounces at listserver.123.net.nz)
[mailto:delphi-bounces at listserver.123.net.nz
(mailto:delphi-bounces at listserver.123.net.nz)] 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: delphi at listserver.123.net.nz (mailto:delphi at listserver.123.net.nz)
 Admin: http://delphi.org.nz/mailman/listinfo/delphi
(http://delphi.org.nz/mailman/listinfo/delphi)
 Unsubscribe: send an email to delphi-request at listserver.123.net.nz
(mailto:delphi-request at listserver.123.net.nz) with Subject: unsubscribe  

	    
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20141204/35f5a4d4/attachment.html 


More information about the Delphi mailing list