DEV Community

Daniel Ioni
Daniel Ioni

Posted on

# Building in Public: Today’s Development Update

Building in Public: Today’s Development Update

Today was one of those days where several pieces started moving at the same time — product, infrastructure, security, payments, and the work Nicola is pushing forward.

Here’s a quick development update on where things stand.

LIFE 2027 and the scientific side

We continued moving forward on the LIFE 2027 track, particularly around the scientific component and the contacts needed to strengthen that side of the project.

The goal here is not simply to prepare an application, but to make sure the technical and scientific foundations are credible enough to support what we want to build.

There are still conversations and validations ahead, but the direction is becoming clearer.

Stripe and MYZ-49

Work also continued around Stripe and MYZ-49.

Payments are one of those areas where the implementation itself is only part of the job. The surrounding flows, edge cases, configuration, and production readiness matter just as much.

We’re progressively closing those gaps and getting the payment layer into a more solid state.

Security: RustSec and MYZ-12

Another important area today was dependency and security work connected to RustSec / MYZ-12.

Security work is rarely the most visible part of a product, but it is exactly the kind of work that becomes expensive when postponed.

So the approach remains simple:

  • identify the issue;
  • understand the dependency path;
  • remove or mitigate the vulnerable surface;
  • verify that the fix doesn’t introduce regressions.

It’s maintenance work, but it’s foundational maintenance.

Nicola’s progress: N4K48

Nicola also continued pushing forward on N4K48.

This is particularly useful because we’re starting to turn several previously separate pieces into a more coherent development path.

Rather than treating each task as an isolated ticket, the focus is increasingly on how the pieces interact: what blocks what, what can be shipped independently, and what needs to be stabilized before moving to the next layer.

That should help us reduce unnecessary rework as development accelerates.

What comes next

The immediate priorities are now fairly clear: continue consolidating the payment work, close the relevant security issues, keep N4K48 moving, and advance the technical/scientific groundwork around LIFE 2027.

There’s still a lot to build.

But today was less about starting new things and more about connecting existing work into something increasingly coherent.

And that’s usually when a project starts getting interesting.

buildinpublic #development #startup #rust

Top comments (0)