As you may know, I have significant disagreements with @unclebobmartin about the software design advice in his book "Clean Code". He and I recently discussed some of these issues, and a transcript of the discussion is available at https://t.co/GdubtPw6y7.
🔥 Compose Multiplatform for iOS is Stable and Production-Ready! 🔥
Build mobile apps faster with shared UI code, full control over native experiences, and the confidence to ship at scale.
Explore all the updates in Compose Multiplatform 1.8.0: 👇
https://t.co/F1Zs9VgcT4
🚀 Kotlin Multiplatform Tooling – Shifting Gears!
We’re doubling down on KMP support in IntelliJ IDEA and Android Studio! As a result, we’re discontinuing KMP support in Fleet, but all the insights we've gained will fuel our future efforts. Get the details here: https://t.co/NsqSEnTwSp
#Kotlin #KotlinMultiplatform #JetBrains #DevTools
As a veteran of robotics and AI, @rodneyabrooks offers predictions and annual evaluations of the state of the field. His insights cut through the hype, fostering a realistic understanding of current advancements. Highly recommended read! https://t.co/6Nzuxf2ulP
Bu cuma yayımlanacak köşe yazımdan. Almanya'da dikey tarım yapmak isteyen girişimcilerin hikayesi...
Girişimciler önce Kuzey Ren Wesfalya eyaletinde bir yer bulur. Ancak mahalle sakinleri “buraya çok kamyon girip çıkmasını istemiyoruz” der. Bavyera’da bir yere bakarlar, çiftçiler “sebze toprakta yetişir, biz dikey tarım istemezük” der.
Girişimciler, sonunda Berlin yakınlarında yolu, elektriği olan güzel bir yer bulurlar. İzin almaya gelince, Alman devleti uzun süre tesisin zirai mi sınai mi olduğuna karar veremez. Bu konuyu tartışmak için 42 kurumun katıldığı bir “istişare toplantısı” düzenlenir.
Sonra tesisin kurulacağı arazide Bronz Çağı’ndan kalan harabeler olduğu ortaya çıkar.
Bu sorun da birkaç senede aşıldıktan sonra, yakındaki bir rüzgar santralinin sahibi kanatların olumsuz etkileneceği iddiasıyla şikayetçi olur.
Sekiz yıllık maceranın sonunda proje rafa kalkar.
Big news! The Epic Games Store and other app stores are coming to the Google Play Store in 2025 in the USA - without Google's scare screens and Google's 30% app tax - thanks to victory in Epic v Google.
https://t.co/1g6uuw1CJB
What happens if your CPU gets something wrong? If it wakes up one day and decides 2+2=5?
Well, most of us will never have to worry about that. But if you work at a company the size of Google, you do, which is why this paper on "mercurial cores" is so fascinating.
What the authors report--and supposedly this is common knowledge at the hyperscalers--is that a couple cores per several thousand machines are "mercurial." Due to subtle manufacturing defects or old age, they give wrong answers for certain instructions. These can cause all sorts of impossible-to-diagnose issues. Some rare problems at Google that were traced back to bad CPUs include:
- Mutexes not working, causing application crashes
- Silent data corruption
- Garbage collectors targeting live memory, causing application crashes
- Kernel state corruption causing kernel panics
What makes CPUs go bad? It's very hard to tell. The authors posit that issues are becoming more frequent as CPUs get more complex, but there aren't solid numbers behind that. There are certainly strong relationships between frequency, temperature, voltage, and bad CPU behavior--most mercurial CPUs only cause problems under very specific conditions, but those conditions vary from CPU to CPU. Age is another source of problems, as older CPUs are more likely to exhibit problems.
Bad CPUs are an especially serious problem because they're very hard to detect. If cosmic rays flip bits in storage or on the network, that can be detected through error coding. But there's no analogy for a CPU that allows cheap online verification of its correctness. Instead, the best detection techniques involve monitoring for symptoms. If a core exhibits exceptionally high rates of process crashes or kernel panics relative to its fellows, that's a strong indication something is wrong with it. For the most critical applications, the authors propose triple modular redundancy--redoing each of its computations on three cores and majority-voting a reliable result.
More than anything, this paper is a call to action--letting everyone know that CPUs can fail. So now, if you ever find a bug you can't diagnose, you can blame the CPU! 🙂
https://t.co/LGKIFuYisa
"And we have to be careful not to become that person who drives their car into a lake just because the navigation system tells them to."
So this just happened:
- a bot found a vulnerability in a dependency
- a bot sent a PR to fix it
- the CI verified the PR
- a bot merged it
- a bot celebrated the merge with a GIF
https://t.co/mHnWudZlUs
One of my most controversial software opinions is that your sleep quality and stress level matter far, far more than the languages you use or the practices you follow. Nothing else comes close: not type systems, not TDD, not formal methods, not ANYTHING.
Allow me to explain why.