Ivan “CLOVIS” Canet

I'm nominated in ‘online presence’, vote for me!

✊🏻

Un mail de la BNP Paribas dont le sujet est "Ivan Canet, je vous aime… et votre argent encore plus"

Ils ont pété un câble…

(oui c'est un mail officiel)

again? :/

Yes, 100%

Oh yes you could. Have random ‘I'm adult’ paper tokens that you can buy at liquor stores or other places that already age-check.

Protection for children. Full anonymity. It can be done.

The AI Vampire This was an unusually hard post to write, because it flies in the face of everything else going on.

steve-yegge.medium.com/the-ai-vampi...

...I *hope* they would find a better name

I'm sure with hindsight they wouldn't name them this way 😅

Gradle vocabulary: projects, builds, artifacts… - Ivan “CLOVIS” Canet Software engineering, open source and computer security

Are you confused by Gradle terminology? What's a module, a configuration, a build, a project? Unless you're deep into Gradle, they probably aren't what you think.

I wrote an article to organize all of that → ivan.canet.dev/blog/2026/03...

Idea: halfway through your integration tests, switch to the new version, see what happens.

Just a heuristic, not as powerful as what the article describes, but it could be quite simple to set up?

This is a *very* interesting read on managing new versions of existing deployments.

www.iankduncan.com/engineering/...

Better Immutability in Kotlin aka "Value Classes 2.0" -- Motivation and Design Space · Kotlin KEEP · Discussion #472 We are happy to finally share a new KEEP proposal exploring the motivation and design space for better value classes in Kotlin -- an evolution of the current inline value classes aimed at making im...

Though, it won't be a big change on behavior, since value classes are moving towards doing what we use data classes for.

The Kotlin team is asking for your thoughts on what will probably become the roadmap for the next few years → github.com/Kotlin/KEEP/...

This may look like a small feature on the outside, but it will radically change how we write #Kotlin code.

Once this is implemented fully, almost all existing data classes will be replaced by value classes. This may be the most impactful change in overall code style in a while!

This is a screenshot from the Cucumber test framework titled "Sharing state between scenarios", with the content "Don't do it."

Nice xD

I'm curious, how are people positioned? Is it mainly based on follows?

Rework the BSON hierarchy (#112) · Issues · OpenSavvy / KtMongo • Alpha · GitLab Currently, we have: Bson: a stored BSON document BsonArray: a stored BSON array BsonValueWriter: a writer...

Have you used KtMongo? Are you planning to?

I'd love your thoughts → gitlab.com/opensavvy/kt...

It's not even fully rolled out yet!

British folks at 3 AM

My brain isn't made for little-endian IEEE754

It's also much easier to write a test that verifies the actions of a component is isolation.

This is better than a two way binding (though more verbose) because the data flow is the same as the component hierarchy, so a parent component can ‘intercept’ writes to veto/augment them or anything else.

Usually this is done by having a prop that contains the value and a second one that contains a function to change the value. The value is only mutable in the common parent, but all components that are given the callback can change it.

youtrack.jetbrains.com/issue/KT-844...

<============-> 93% EXECUTING [7m 57s] > IDLE > IDLE > IDLE > IDLE > IDLE > IDLE > IDLE > :server-arrow:compileKotlinJvm

Well, what I can tell you is that it absolutely tanks the performance of the compiler 😅

That module only has 177 LOC total

This is also the reason why LLMs alone are very specifically poorly suited for engineering because automation is fundamentally about *removing* repetition whereas LLMs are built to *amplify* repetition

Dependency upgrades (!155) · Merge requests · OpenSavvy / Build and automation / Vite for Kotlin · GitLab Gradle plugin to use Vite and Rollup in Kotlin Multiplatform projects

yup that works

gitlab.com/opensavvy/au...

“too big to render” 😅

But yeah that's a good idea

Any recommendations on what I can put in the hello-world so it stays bigger than 4kB so my tests pass? 😅

The Vite for Kotlin test suite fails with Kotlin 2.3.0 because...

Kotlin Wasm has been optimized enough, that the generated Wasm file is so small, that Vite decides to inline it entirely, so there is no visible Wasm in the output