WG211/M26Balaci

From WG 2.11
Revision as of 20:51, 9 October 2026 by Jacques (talk | contribs) (Created page with "Executable code often takes priority over documentation in software development. One inherent problem is knowledge duplication in code and documentation. Can we avoid that by generating everything? What would such a process look like? This talk will discuss exploratory work in Drasil, a software generation framework for complete scientific software artifacts fit for humans, where we define "complete" as containing all software artifacts normally contained in a code repo...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Executable code often takes priority over documentation in software development. One inherent problem is knowledge duplication in code and documentation. Can we avoid that by generating everything? What would such a process look like?

This talk will discuss exploratory work in Drasil, a software generation framework for complete scientific software artifacts fit for humans, where we define "complete" as containing all software artifacts normally contained in a code repository (code, documentation, build scripts, etc.), and "fit for humans" as being well-documented and being idiomatic with meaningful identifiers.

The software generation pipeline in Drasil resembles a highly rational, explainable software development process. This talk will deconstruct said process, discussing: codifying problem-space concepts with domain-specific languages, refining problems into solutions through making concrete decisions about how problems should be translated into software artifacts.

Retrieved from "http://mw.hh.se/wg211/index.php?title=WG211/M26Balaci&oldid=2920"