Path: ...!feeds.phibee-telecom.net!news.mixmin.net!news2.arglkargh.de!news.karotte.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: alt.folklore.computers,comp.os.linux.misc
Subject: Re: The joy of FORTRAN
Date: 2 Oct 2024 02:12:10 GMT
Lines: 23
Message-ID: <lm3ofqF1legU1@mid.individual.net>
References: <pan$96411$d204da43$cc34bb91$1fe98651@linux.rocks>
	<5mqdnZuGq4lgwm_7nZ2dnZfqnPSdnZ2d@earthlink.com>
	<vcub5c$36h63$1@dont-email.me>
	<36KdnVlGJu9VLW77nZ2dnZfqn_qdnZ2d@earthlink.com>
	<971448126.749088380.092448.peter_flass-yahoo.com@news.eternal-september.org>
	<vd5195$edas$1@dont-email.me> <59CJO.19674$MoU3.15170@fx36.iad>
	<vd6vto$r0so$1@dont-email.me> <iJEJO.198176$kxD8.81657@fx11.iad>
	<3hOdnWpQ649QMGr7nZ2dnZfqnPidnZ2d@earthlink.com>
	<vd8doi$15q07$1@dont-email.me> <vd8eg7$15v1j$2@dont-email.me>
	<cxicnVzg_cn_eGX7nZ2dnZfqnPadnZ2d@earthlink.com>
	<vdapbn$1kp35$5@dont-email.me>
	<xD2dnSerYr-8kmf7nZ2dnZfqn_ednZ2d@earthlink.com>
	<llv25bFa6uvU2@mid.individual.net>
	<n-ednbNVDrThwWf7nZ2dnZfqn_ednZ2d@earthlink.com>
	<1114392917.749421134.280786.peter_flass-yahoo.com@news.eternal-september.org>
	<WHudncjyj7eEHGb7nZ2dnZfqnPWdnZ2d@earthlink.com>
	<lm2u9aFs3voU6@mid.individual.net>
	<066d7009-983d-3dc8-b78f-bc37a915da18@example.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net KsLZFxjx2InbAC0ruI0XIAxSTQdshavOTD+pBNerwgv73clIAg
Cancel-Lock: sha1:AXdEQ6i/iWL/PhBs9J4b9vzrunU= sha256:cMYTKBmgskJgmYeEwCVDOhDFIeCIeIIoM4oLRAehFOA=
User-Agent: Pan/0.149 (Bellevue; 4c157ba)
Bytes: 2877

On Tue, 1 Oct 2024 21:28:14 +0200, D wrote:

> I think there's some old programmer saying from the beginning of time,
> that says something like the third time I completely rewrite the program
> it gets done right.

Over the years new buzzwords like agile have been tacked on but my process 
always started with the assumption that the client didn't know what they 
really wanted. Throw together a quick and dirty prototype with enough 
functionality that they can play with it. Take notes on the complaints, 
modify the prototype. Rinse and repeat until they're mostly happy.

Scrap the prototype, possibly retaining some code, and build the product. 

There is a related process I call 'reconnaisance by fire'. That's when 
you're handed an API that you're pretty sure is incomplete, inconsistent, 
and missing vital information. Build the interface, test it, find out 
where it fails, and try something else. If you're lucky the other party 
will be helpful although I have had instances where they were hostile.

The most important part is not developing an ulcer while dealing with 
human nature. Easily perturbed people probably should try another career 
path.