We provide four guiding principles that are concise, actionable, and will help make organising an inclusive academic event a piece of CAKE 🎂:

• Connectivity: Is everyone seen?
• Adaptability: Is everyone themselves?
• Kinship: Does everyone feel like they belong?
• Empowerment: Can everyone (and the community) grow?

• Github repo
• Paper

2024 is my last edition of the Computational Neuroscience Imbizo, a gathering to share knowledge, create connections, and an adventure that has changed my life.

I’ve given dozens of presentations to thousands of people. Sometimes it’s only to a handful of experts, other times to hundreds of eager learners. Many times the audience has a mixed background of skills, languages, and cultures. Here are some broad expectations I’ve laid out for myself to improve my presentations and the audience experience.

1. Set expectations early and often
2. Set up then show and tell
3. Breadcrumbs guide the way
4. Less is more
5. Context is key(note)
6. Highlight powerful points
7. Hierarchy of information
8. Interact
9. Keep learning and adapting
10. Accessibility

Our paper, published in “Scientific Reports,” addresses the phenomenon of echo chambers in social networks, where users often engage with like-minded peers, leading to polarization. We propose a method, the Random Dynamical Nudge (RDN), to bridge polarized communities and achieve a neutral consensus. The RDN exposes users to a random selection of opinions, avoiding the need for intensive surveillance of individual opinions. Our computational models show that RDN can effectively depolarize existing echo chambers and prevent their formation. This approach could be a practical tool for social media networks to manage online community segregation on complex social issues.

• Paper
• Code

Christopher B. Currin

University of Cape Town

In fulfilment of the requirements for the degree

Doctor of Philosophy in Neuroscience

Supervised by Dr Joseph Raimondo

I have always been fascinated by how we think and learn. I find beauty in the irony that we know more about what is “out there” than what is in our heads. Becoming a professional problem-solver, i.e., a scientist and software engineer, was a natural progression from this wonder.

Results are processed, reviews are in, the paper is a go. Why on earth would I spend an extra 8+ hours to clean, comment, and commit my code to GitHub for something that’s technically “done”?

Because science deserves better than shoddy code, or worse, no transparency at all…

Dual booting can be both useful and inconvenient.

How we facilitate the formation of a cohesive community that transcends race, gender and geographic boundaries in just three weeks.