Walkthrough: best practices in software development #117

New issue

Open

opened 2025-09-30 15:12:38 +00:00 by richelbilderbeek · 2 comments

richelbilderbeek commented

2025-09-30 15:12:38 +00:00

(Migrated from github.com)

The academic literature has some ideas what are best practices in software development. Share some of these.

I can imagine different teachers have different favorite aspects here.

My favorite aspects will be Test Driven Development, assert and continuous integration and software architecture.

The academic literature has some ideas what are best practices in software development. Share some of these. I can imagine different teachers have different favorite aspects here. My favorite aspects will be Test Driven Development, assert and continuous integration and software architecture.

👍 10

mahesh-panchal commented

2025-09-30 16:02:00 +00:00

(Migrated from github.com)

This would be an interesting discussion.

I think one view is that many of us don't see us as software developers and the code is a by-product of the analyses we perform. Do practices such as test driven development have a place in contexts where code is exploratory in nature.

This would be an interesting discussion. I think one view is that many of us don't see us as software developers and the code is a by-product of the analyses we perform. Do practices such as test driven development have a place in contexts where code is exploratory in nature.

jwindhager commented

2025-10-09 08:53:16 +00:00

(Migrated from github.com)

I like the idea and was thinking an "overview" (perhaps along the lines of SciLifeLab's open science software checklist?) could be a good first step, followed by branching out to the individual topics in more depth in individual walkthroughs?

EDIT: perhaps the Open Science Software Checklist could also have its own walkthrough, independent of this?

I like the idea and was thinking an "overview" (perhaps along the lines of SciLifeLab's [open science software checklist](https://data.scilifelab.se/open_science/resources/)?) could be a good first step, followed by branching out to the individual topics in more depth in individual walkthroughs? EDIT: perhaps the Open Science Software Checklist could also have its own walkthrough, independent of this?