I'm heading to @fosdem.org this weekend to present 2 research software-related talks. Come say hi, tune into the livestream, or watch the recordings later. #FOSDEM fosdem.org/2026/schedul... I'm also using this as a chance to kick off a short blog post series. Details in the thread.

My first talk is on Saturday, in the Bioinformatics & Computational Biology devroom. fosdem.org/2026/schedul... I'm presenting movement, our Python package for analysing animal motion.

In this 2nd talk, I'll distil lessons learnt through my transition from academic research to research software engineering with @neuroinformatics.dev Tune in if you've written code that solves a problem—maybe for your own analysis, maybe for your lab—and hope it can be useful to others.

While prepping the talk, I realised there was much to say on this topic, so I've also prepared a 3-part blog post series. You can find the overview here: neuroinformatics.dev/blog/trusted...

Part 1 is about finding your software's mission and scope. Open-source software is a vast web of inter-connected tools. When creating a new tool, your first job is to carve out its place in the web openly and from the outset. How can you approach that? See neuroinformatics.dev/blog/trusted...

Parts 2 and 3 to follow in the next few weeks (will post under this thread).

Part 2 of the "Trusted by design" blog series is out today @neuroinformatics.dev. 'Release early, release often' is an often-repeated mantra, but... How early? How often? And why is this so critical to establishing and maintaining trust? See neuroinformatics.dev/blog/trusted...