jonathan@researchcomputingteams.org
Parent categories: Technical Leadership
Other tags: | Technical Leadership: Software Development | Strategy: Research to Development Maturity Ladder |
Testing And Scale - Daniel Bell This is a short read talking about the difference in the need for testing at the initial, exploratory phase of coding (where detailed testing is brittle and slows you down) as opposed to the stage of development where the code is being used for real things (where lack of detailed coding makes the codebase brittle because it can’t be easily safely modified). This this is particularly relevant to research software development, where I’ve argued a maturity model is a...
Continue...Other tags: | Technical Leadership: Software Development |
How I think about Code Management - Andreas Klinger A lot of research software we start dealing with…., well, let’s say “has many opportunities to be made even better”. Klinger has a nice summary of maintaining and improving a code base over time. He sees it as having two components: Reducing complexity, and Increasing confidence And that both of those can and should be addressed incrementally and continuously. Klinger says that you handle the code complexity over time with refactoring (including my favourite refactoring, deleting...
Continue...Other tags: | Technical Leadership: Software Development |
I just threw away a bunch of tests - Jonathan Hall The evolution of the SciPy developer CLI - Sayantika Banik, Quantsight Labs Related (but not limited) to ease of developer onboarding - I was just having this conversation with a friend. Test suites are code, too, and part of your product - they’re not some weird kind of “meta-code” for which the usual rules don’t apply. As Hall points out, that means keeping them documented, making them easy to run, refactoring them, and discarding...
Continue...