How We Grow by Sharing Knowledge

Sharing knowledge is therefore deeply ingrained in our culture, both internally and with the community around us.

Talks: From Lightning Talks to PyCon

Every quarter, we organise in-depth knowledge sessions, but we also like to keep things accessible with Lightning Talks. These are short presentations where we update each other on a new tool, a clever hack, or an interesting technical topic.

We’re also always looking ahead to external events. If there’s an opportunity to speak at a PyCon, Wagtail Space, or an alumni event, we’re happy to seize it. Nothing is mandatory, but there are always a few of us who love taking the stage. Would you like to speak but still find it a bit nerve-wracking? Then we use our internal sessions as a “dry run.” By presenting to your colleagues first, you’ll get honest feedback and can polish your presentation before taking the stage.

Always Relevant Topics

We decide for ourselves what to talk about. We regularly gauge where people’s interests lie and find a speaker to address those topics. It might be a deep technical dive that’s really only interesting to developers, but sometimes we also discuss the softer side of our work, such as collaborating more effectively. We always start with engagement; we delve into our clients’ ambitions to ensure that the choices we make align with their goals. As a result, we don’t just build software—we build solutions that matter.

Our Developers Meeting: Taking Control of the Process

We also share knowledge during our Developers Meeting. Here, all our developers come together to discuss internal projects. We look beyond the issues of the day and client assignments. We discuss how we can speed up our own work or how we can create a clearer overview. Sometimes you have to take a step back to examine your own process.

We don’t build disposable software; we strive for sustainable, high-quality solutions, and proactively engaging in discussions about technology is part of that. Maintainability is a key topic. For example, we discuss when to optimize, what to include in our “cookie-cutter” templates, or how to make technical components generic, and we develop internal quality tools that we use for all our clients.

Code Reviews and “Self-Explanatory” Code

In our day-to-day work, we share our knowledge through code reviews during merge requests. Our philosophy is that code should fundamentally be “self-explanatory.” Is a piece of logic truly very complex? Then we provide the necessary documentation. We do this directly in the code or in our Confluence space, so that a colleague (or you yourself in six months) immediately understands what’s happening.

Presenting with Reveal.js

As developers, we prioritize efficiency over manually formatting PowerPoint slides. To quickly put together a polished presentation, we use internal tools based on Reveal.js. This allows us to build our slides using simple HTML code. It’s fast, looks great, and fits perfectly into our workflow.

Would you like to grow with us?

Do you also value continuous self-development, sharing knowledge, and working in a team where initiative is appreciated? We’re always looking for talented developers to join our team. We offer challenging platform engineering in fields with social and economic relevance, in a work environment that combines structure, autonomy, and professional development.

Check out our job openings, and who knows—you might soon be giving your first Lightning Talk (or just enjoying listening in, of course).