Kotlin developer & teacher @ 4SH, learn more about me: ivan.canet.dev
Open source at https://opensavvy.dev • @opensavvy.techhub.social.ap.brid.gy
Organizing the Kotlin Bordeaux User Group at https://bordeauxkt.io
Ivan “CLOVIS” Canet
Loading...
It was interesting writing this one, I had to research the topic in a bunch of languages.
#golang, #kotlin and #java are the winners: they are the languages where it's easiest to avoid the bug.
I'm surprised to find #rust and #haskell at the bottom of the list. I expected better from them.
I really like Spine from @opensavvy.dev and @ivcanet.bsky.social.
It offers a really cool and ingenious way of defining typed endpoints in #Kotlin for #Ktor that you can share between the server & client! 🔥
It just moved into beta with the 0.11.0 release. Check it out.
spine.opensavvy.dev
The problem with watching a show centered around hacking is... I know they're bullshitting everything.
The only thing that's accurate is that hackers have a screen behind them. Yeah that one's accurate. Don't ask me why.
I've found a 4th bug in the official MongoDB driver
Claude's dynamic workflow feature is *very* half-baked.
If you reach the end of your quota during the workflow (very likely), it's not able to resume from there once quota is back.
KtMongo 0.31.0 will support ALL* filter and update operators
* except JSONSchema and deprecated operators
Can you find the bug in this code?
ivan.canet.dev/blog/2026/06...
In which order should Kotlin parameters be declared?
ivan.canet.dev/blog/2026/06...
👀
kotlinweekly.net
ivan.canet.dev/blog/2026/06...
What's your strategy for testing the failure conditions of complex algorithms?
Context: KtMongo is a new multiplatform driver for MongoDB. I want to know in advance the failure conditions (before users report them). Socket fails? Database crashes?
How can I find out about these?
