Barrel Aged Software Development: brewscheme as a four-year old

Billy Buchanan ()
Additional contact information
Billy Buchanan: Fayette County Public Schools

2019 Stata Conference from Stata Users Group

Abstract: The term software development implies some type of change over time. While Stata goes through extraordinary steps to support backwards compatibility, user-contributors may not always see a need to continue developing programs shared with the community. How do you know if/when you should add additional programs/functionality to an existing package? Is it easy/practical to extend existing Stata code or is it easier to refactor everything from the ground up? What can you do to make it easier to extend existing code? While -brewscheme- may have started as a relatively simple package with a couple of commands and limited functionality, in the four years since it was introduced it has grown into a multifunctional library of tools to make it easier to create customized visualizations in Stata while being mindful of color sight impairments. I will share my experience, what I have learned, and strategies related to how I dealt with these questions in the context of the development of the -brewscheme- package. I will also show what the additional features do that the original -brewscheme- did not do.

Date: 2019-08-02
References: Add references at CitEc
Citations:

Downloads: (external link)
https://wbuchanan.github.io/stataConference2019/#/

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:boc:scon19:30

Access Statistics for this paper

More papers in 2019 Stata Conference from Stata Users Group Contact information at EDIRC.
Bibliographic data for series maintained by Christopher F Baum ().