Posts by Niko Sirmpilatze

Trusted by design (part 3): embrace radically open communication

Open-source software is public, yet much of the communication around it may happen in private emails, internal Slack channels and meetings with no minutes. This disconnect can erode the very trust that openness is meant to build. What if communication were radically open—a habit of constant, multi-way interactions visible to anyone who cares to look?

Read more ...


Trusted by design (part 2): release early, release often

‘Release early, release often’ is an often-repeated mantra, popularised by Eric S. Raymond in his 1997 essay “The Cathedral and the Bazaar”. I hadn’t fully grasped its significance until I switched from academic research to full-time software development. How early? How often? And why is this so critical to establishing and maintaining trust?

Read more ...


Trusted by design (part 1): define your software’s mission and scope

No project exists in a vacuum. Open-source software is a vast web of inter-connected and inter-dependent tools. When creating a new tool, your number one job is to carve out its place in the web consciously, openly and from the outset. How can you approach that?

Read more ...


Trusted by design (intro): set up your research software for community adoption

So, you want to create an open-source research software package—and not just for yourself or your group. You’d like people around the world to use it, and even contribute to it. How do you persuade them it’s worth their time?

Read more ...


Managing neuroscience projects with datashuttle

Create, validate and transfer standardised project folders

../../_images/datashuttle-overview-light.png

Read more ...


Data organisation with NeuroBlueprint

The challenge of unstandardised data in systems neuroscience

../../_images/errant-science-data-organisation.jpg

Read more ...