Path: ...!fu-berlin.de!uni-berlin.de!not-for-mail
From: ram@zedat.fu-berlin.de (Stefan Ram)
Newsgroups: comp.misc
Subject: Re: Code Reuse (was Re: The Continuous Amnesia Issue)
Date: 17 Apr 2024 13:12:37 GMT
Organization: Stefan Ram
Lines: 28
Expires: 1 Feb 2025 11:59:58 GMT
Message-ID: <reusability-20240417141033@ram.dialup.fu-berlin.de>
References: <slrnv1rafb.3l3.bencollver@svadhyaya.localdomain> <uvnf78$1ct1p$3@dont-email.me> <wwv8r1cpg7w.fsf@LkoBDZeT.terraraq.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: news.uni-berlin.de s4IdvkZ45m9yAUkRn47XDAF+FCdCCxBNKnHw2PINHIRCJn
Cancel-Lock: sha1:pVUv4Xwhts+u2znHVA5ESQA/esw= sha256:PUu1+fB2gYjUdoT+idlQ2DkSU2cijSd3q9rdl7Al2bg=
X-Copyright: (C) Copyright 2024 Stefan Ram. All rights reserved.
	Distribution through any means other than regular usenet
	channels is forbidden. It is forbidden to publish this
	article in the Web, to change URIs of this article into links,
        and to transfer the body without this notice, but quotations
        of parts in other Usenet posts are allowed.
X-No-Archive: Yes
Archive: no
X-No-Archive-Readme: "X-No-Archive" is set, because this prevents some
	services to mirror the article in the web. But the article may
	be kept on a Usenet archive server with only NNTP access.
X-No-Html: yes
Content-Language: en-US
Bytes: 2490

Richard Kettlewell <invalid@invalid.invalid> wrote or quoted:
>A cursory search finds only a couple of remarks about re-use.

  A modern software dev gotta know the skinny on reusability.
  Here's the lowdown:

  - Focus on crankin' out top-notch, well-abstracted, and
    well-documented reusable software goodies (code, designs,
    specs, the whole nine yards)

  - Make sure them reusable components are loosely coupled and
    can be tweaked to fit different contexts

  - Set up them organizational processes and incentives
    that'll reward and grease the wheels of reuse

  - Invest in some serious testing, version control, and
    security checks for them reused components - gotta keep
    'em squeaky clean 

  - Prioritize that modular, clean, and maintainable code
    design to set the stage for future reuse

  - Leverage them design patterns, architecture principles,
    and software frameworks

  - Gotta work across teams and projects to develop them
    widely-accepted, high-quality reusable resources