From: NiGHTS <nights@unku.us>
Subject: Re: Code organization
Date: Thu, 27 Sep 2018 08:09:51 -0700 (PDT)
Date: 2018-09-27T08:09:51-07:00 [thread overview]
Message-ID: <f83642f8-7e25-43ae-9ed3-377b53b2bb5c@googlegroups.com> (raw)
In-Reply-To: <poiqkg$llo$1@dont-email.me>
On Thursday, September 27, 2018 at 10:48:49 AM UTC-4, Jeffrey R. Carter wrote:
> In my experience, good code organization is a product of design.
I agree with this, and clearly a project that has been spec'd in great detail prior to its development would directly lead to a better organized project.
Then you get into the coding and realize Ada doesn't exactly agree with your organization strategy and imposes some design constraints, particularly with a heavily multi-threaded project. This is kind of how it worked out for me. Once Ada forced me into nesting what would have otherwise been living in other packages, my ambitions for file organization went down the drain. And it didn't help that I was on strict deadline by this point in time.
next prev parent reply other threads:[~2018-09-27 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 14:24 Code organization NiGHTS
2018-09-27 14:43 ` Shark8
2018-09-27 15:01 ` NiGHTS
2018-09-27 15:33 ` NiGHTS
2018-09-27 14:48 ` Jeffrey R. Carter
2018-09-27 15:09 ` NiGHTS [this message]
2018-09-27 19:49 ` Jeffrey R. Carter
2018-09-27 20:46 ` Brian Drummond
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox