olivero2.bsky.social
Kotlin Multiplatform Software | High-Concurrency Event-Based Systems | Advanced Testing
60 posts
54 followers
69 following
Regular Contributor
Active Commenter
comment in response to
post
Also a big shoutout to @ivcanet.bsky.social for all the inspiring discussions that made TestBalloon what it is, and for being first to use the initial release about 6 hours after its publication: gitlab.com/opensavvy/gr...
comment in response to
post
Thank you so much! I felt just the same when chatting with you. Please let me know how it works for you.
The Maven Central publication issue turned out to be what I'd consider to be a bug in the publication plugin, requiring an additional line of Gradle configuration.
github.com/infix-de/tes...
comment in response to
post
I wanted to, but after spokes breaking one after another on my rear wheel, my (pretty old) bike is up for serious repair or replacement. I won't have a trustworthy solution for KotlinConf, so it'll be the train for me. But if you touch Hamburg on your way, let me know!
comment in response to
post
Gute Doku, der jedoch ein gewichtiger Verzerrungsaspekt fehlt. #Volksverpetzer erklärt, dass 20% der nicht-deutschen Tatverdächtigen keinen Wohnsitz in Deutschland hatten und weitere 20 bis 30 Prozent keinen festen Wohnsitz oder einen unbekannten.
www.volksverpetzer.de/faktencheck/...
comment in response to
post
👍 For sure, without considering this paranoid. Allowing a single point of failure 🧨 has never been a good idea.
comment in response to
post
Did you try Signal? Worked well for me so far.
comment in response to
post
Der Hyperfokus auf fiktive Probleme ist ein Zeugnis der eigenen Inkompetenz: Wer echte Probleme lösen kann, braucht keine Sündenböcke.
comment in response to
post
I'd say the factor is complexity ÷ activity. While we could easily handle a low-complexity library without community help, doing so is rarely feasible with a large, complex library.
comment in response to
post
Lust habe ich auch morgen auf die Menschen, die sehen, was ist und sich nicht wegducken. Die Widerständen und Bequemlichkeiten trotzen, sich verantwortlich verhalten und für ein lebenswertes Morgen einsetzen. Wie hier wieder.
comment in response to
post
If so, wouldn't each interpreter based on that key/value structure in effect create its own configuration language?
comment in response to
post
The initial arguments were compelling: "composable simplicity". So I read on...
Would I be wrong in summarizing this as "Here's my key/value configuration language, you'll have to put in the beef by supplying a parser and interpreter for everything else"?
comment in response to
post
Cool move! You’ll keep the X-itter account, obstructing malicious takeovers, won’t you?
comment in response to
post
I still think the better approach is to keep the X-itter account in order to block the name and prevent malicious actors from repurposing its reputation. Even more important for high visibility accounts.
comment in response to
post
First rule in benchmarking: Either you know when and how to use a black hole or you’re doing it wrong.
comment in response to
post
On point.
comment in response to
post
Nothing beats a thorough understanding of dynamics and a proper design. In the end, what really makes development and maintenance of large systems efficient is clarity, simplicity and less code, not more.
comment in response to
post
Finally, cross-cutting changes requiring modifications in all intermediate layers will arrive and eat the idea for breakfast. Even if it was executed as planned (which, as you correctly pointed out, will just not happen in many cases).
comment in response to
post
Introducing middleware layers, multiplying the number of moving parts to do the same thing makes it worse and slows down development.
comment in response to
post
Cool insights. I never got very deep into the approach, as it seemed like committee-designed bloatware. Trying to protect up-front against all sorts of possible changes is a premature optimization which loads lots of technical debt onto any large system.
comment in response to
post
Short, to the point, 👍 and did ring a 🔔 bell to me. Seems like we have seen similar territory: slack-chats.kotlinlang.org/t/15633155/i...
comment in response to
post
I wanted to go by train this year, but travel options for speakers were limited to flights. I didn't want to stress the organizing team, so I complied. Next year, I'd rather pay by myself and just skip the flight booking.
comment in response to
post
According to the author on LinkedIn, the study "measures developer productivity by analyzing the functionality of source code across Git repos". If someone has actually found a meaningful dev productivity metric, I'd love to see their peer-reviewed publication.
comment in response to
post
Uh oh, are we going NPM-style micro-packages? 🙃
comment in response to
post
Useful information. One piece appears to be a bit ahead of time for mere mortals: The "Can be DumbAware" inspection is unavailable in IntelliJ IDEA 2024.3. A newer DevKit release is there, but wants 2024.3.1, available as RC.
comment in response to
post
This one? bsky.app/profile/chr....
comment in response to
post
There is ITU-T's E.123 (en.wikipedia.org/wiki/E.123), E.164 and of course lots of national/regional stuff. The North American Numbering Plan (US, CA) definitely does not let you call worldwide. Interesting to learn about how this works in France these days.
comment in response to
post
By the time this becomes usable, we'll all be on WebAssembly.
comment in response to
post
Hopefully, one day we'll finally free ourselves from such stuff. 🙃
comment in response to
post
And BTW, opinionated with good quality is fine with me, using Python's black, for example.
comment in response to
post
I did, but found ktfmt inadequate. It's been a while, but if I remember correctly, ktfmt was way too opinionated, but lacking quality, deviating from IJ default's and Kotlin's coding standard in many ways. Today, I'm using ktlint with a bunch of .editorconfig adjustments.
comment in response to
post
ktlint
comment in response to
post
Another option would be to go back in time and get sufficient exposure to, say, Algol68 (maybe even further, don't know who first came up with this backwards stuff). 😆
comment in response to
post
Start small with if ... fi. 😉