Zur Kurzanzeige

dc.contributor.authorSpeicher, Daniel
dc.contributor.authorDong, Tiansi
dc.contributor.authorCremers, Olaf
dc.contributor.authorBauckhage, Christian
dc.contributor.authorCremers, Armin B.
dc.contributor.editorKelter, Udo
dc.date.accessioned2023-02-27T13:44:12Z
dc.date.available2023-02-27T13:44:12Z
dc.date.issued2019
dc.identifier.issn0720-8928
dc.identifier.urihttp://dl.gi.de/handle/20.500.12116/40433
dc.description.abstractWhile we argued in that code quality needs to take context into account, there is now software that demands a really different quality culture like we would be entering another planet. Jupyter, to be precise: A “Jupyter Notebook is [a] web application that allows you to create and share documents that contain live code, equations, visualizations and narrative text.” It consists of text and code cells. The content of code cells is sent on demand to a Python session, executed and the output inserted below the cell. We will approach the quality of notebooks from the perspective of communicative code and design patterns.en
dc.language.isoen
dc.publisherGesellschaft für Informatik e.V.
dc.relation.ispartofSoftwaretechnik-Trends Band 39, Heft 2
dc.relation.ispartofseriesSoftwaretechnik-Trends
dc.subjectJupyter
dc.subjectQuality
dc.titleNotes on the Code Quality Culture on Jupyter (Notebooks)en
dc.typeText/Conference Paper
dc.pubPlaceBonn
mci.reference.pages17-18
mci.conference.sessiontitle21. Workshop Software-Reengineering und -Evolution (WSRE) und 10. Workshop Design for Future (DFF)
mci.conference.locationBad Honnef
mci.conference.date06.-08. Mai 2019


Dateien zu dieser Ressource

Thumbnail

Zur Kurzanzeige