In article <65ff8942$1@news.ausics.net>, dxf wrote:
>On 23/03/2024 8:30 pm, mhx wrote:
>> My current project has 13,938 lines of code (and documentation).
>> That is too large to keep every detail of it in my head.
>>
>> The reason to not factor it in a number of smaller files is that
>> there are many (unavoidable) global variables and data blobs. These global
variables prevent me from dividing the application
>> up into smaller programs that can run standalone. They also prevent me from
documenting sub-tools, and giving such tools their own help words [ The main
application now has lots of help
>> text that is not relevant for a user interested in working with
>> only one of the specific tools. ]
>
>I recall Elizabeth saying that (circumstances allowing) Chuck would write
>as many as three versions of an application, each successively better.
>So when are you going to start Version 2?
That is methodology that fits Chuck Moore. I'm not proficient at writing
bug free code, and I cherish anything that has passed tests.
The other method is evolution. You were evolved from a single cell
organism, this evolution thing can be quite successful.
You can compare the first version of manx that originated from Marcel
Hendrix to tmanx now, or fig-Forth 8086 to ciforth.
Quantitative changes in the end lead to qualitative changes.
I agree with Chuck Moore, that you should relentlessly cut superfluous
branches, only disagree that you have to start over.
A good source control system helps, psychologically. You don't have
to worry that you can't go back, although you never will.
Groetjes Albert
--
Don't praise the day before the evening. One swallow doesn't make spring.
You must not say "hey" before you have crossed the bridge. Don't sell the
hide of the bear until you shot it. Better one bird in the hand than ten in
the air. First gain is a cat purring. - the Wise from Antrim -
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
