I’m on the market for a staff/principal role. I have a passion for #SoftwareArchitecture, Developer Experience, community, mentoring, #performance, and interacting with business and domain experts.
But it no longer feels so. Maybe it was a case of "you have to move fast to fix things" and as incumbents raise their game the window of opportunity closes. The vast investment in established stacks incentivises patching the most egregious weaknesses.
One exception seems #golang, which found a network niche
#Scala gets stick for being past the hype peak and yet there are already TWO fantastic speakers lined up for the next London Meetup in January. That and the New Year inspired me to look for upcoming #Kotlin and #Java talks but I couldn't find anything planned or much in the recent past. I didn't realise how fortunate I was. The London #Scala community is blessed with very interesting speakers and amazing volunteers (most particularly Zainab in this case). https://www.meetup.com/london-scala/events/294866415/
Neue Ideen: Das Spiel soll einen Level Editor bekommen, bei dem jeder seine eigenen Levels bauen kann. Per QR Code kann dann das selbst erstellte Level an Freunde und Bekannte weitergegeben werden. Sogar ganz ohne Internet. Da die Level nicht sonderlich kompliziert sind, passen alle Daten in den QR Code selber rein.
I'll be honest, after years of using #Kotlin working with #Dart and #Flutter in the year 2023 feels reminiscent of how it was using Java 7 for Android development more than a decade ago.
Hey all you #Kotlin (and #JVM) experts. Is there a a makro I can use to raise a compile-time warning which is then shown in #AndroidStudio / #IntelliJIDEA ?
My Kotlin Native project started giving me link errors after installing Fedora 39.
My Kotlin code links libgmp using cinterop, and when building on Fedora 39 I get this error:
undefined reference to '__isoc23_strtol', version 'GLIBC_2.38'<br></br>
I know that I'm probably one of very few people that uses Kotlin Native for a large project, so the chances of someone actually having stumbled across this issue is probably small, but I'm still mentioning it here in case anyone has any ideas.
I think the biggest problem I have with #kotlin is that there's all these fancy things you can do with it, but most of my day to day work involves hooking up buttons to do network calls and trying to refactor code written six years ago.
It reminds me of a comic where during the interview, the person is asked to write a red black tree, but when they get the job, they're asked to move a button five pixels to the right.
Atomic Kotlin by Bruce Eckel and Svetlana Isakova is on sale on Leanpub! Its suggested price is $39.00; get it for $12.00 with this coupon: https://leanpub.com/sh/KI2gp0Iy#Kotlin
Rust on mobile is an exciting space, and a LOT has happened in the past few months.
This post focuses on idiomatic (yes, really!) binding generation between a Rust core, Swift, and Kotlin. And of course, we also cover the pitfalls we've encountered so far 😄
Audile is a music recognition application that can help you quickly and accurately identify a music track playing nearby you. This application uses the AudD® service as a Music Recognition API.
In this new #eventsourcing blog post we will considered several ways to implement state to be used in decision-making. We're equipped with a varied range of tools suitable for different sizes and maturity of problems, from deriving the state with #kotlin stream extension functions to employing finite state machines.
JetBrains introduces Amper. An experimental project description language for #Kotlin Multiplatform. The underlying system using the notation is still #Gradle.
Happy to see such developments. The #Java / #JVM build system is Gradle's killer application. But in its core it's a powerful framework to create build systems on top of.
The huge feature set of vanilla Gradle is probably it's biggest weakness when used directly by end users. Excited to see where this goes.