Platform engineers have a tendency to believe that saying "no" is a sign of maturity and seniority. Let me say it's the exact opposite. Platform engineering is about enablement, where "no" is rarely a good answer. Your work consists on finding the "how".
Spend a minute thinking if you understand "responsibility" as "power". Think if you like your role because you enjoy responsibility (i.e. being on call, being responsible of everyone else's experience) or if, instead, what you like is the sense of power.
I’ve tried to vibe code in Rust a couple of projects (around 20KLOC). The worst result so far compared to other languages. Absolute slop in terms of ownership: it adds clone(), lifetimes, Arc, to_vec, etc absolutely randomly just to shut the compiler. (Opus 5.5). I think Rust has too complex semantics and requires rigorous ownership design. My personal top of languages in terms “write prompt get nice code back”:
- Go (!) it’s just hard to fuck up such primitive code.
- C/C++. I guess huge training data size does the job.
- Java / Kotlin. Solid, but you tend to get “enterprise patterns”.
- Python / TS. They okay for small programs, for larger ones LLMs abuse gradual typing.
…
- Rust. Outright slop.
The actual GOAT of our IT industry who co-created the C programming lang and helped develop the Unix OS. Happy birthday to a true legend whose work shaped modern computing.
Mercury Transfer Module separation confirmed! 📡 ✅
After nearly eight years in space and billions of kilometres travelled, #BepiColombo's Mercury Transfer Module has successfully separated.
Signal acquired via our Cebreros deep-space antenna confirms the spacecraft is healthy and operating as expected.
The MPO and Mio spacecrafts are now on their way to Mercury orbit insertion on 21 November.
Farewell, MTM. Mercury awaits. ☀️🛰️