b-n

There's been some news in the last months of companies diving full in on the AI train, firing a bunch of their engineers. And then a couple of months later they're hiring engineers back again when they realise the hype was not delivering.

My thoughts go to:

When will we see some CEO's getting rolled in companies?
Isn't the job of a CEO to drive the business direction and to adequately validate the risks of decisions?
When are company boards going to start calling "Skill Check" on the CEOs on these decisions? Remember board members, those CEOs are messing with your investments.

Would I like to see some retribution? The childish part of me - sure - but I would honestly just like to see companies treating their future business with human eyes instead of following the blind crowd driven by hype beasts. Let's be in this for the long term, not the short term.

And if you want to amplify this in the faces of those CEOS, feel free to do that here: https://www.linkedin.com/feed/update/urn:li:activity:7419100041937588224/

#rustweek @raph@mastodon.online showing some new things landing in Velo, and showing the details on how to draw an R. Simd on the CPU can enable a bunch of speed without having to send to the GPU, very cool and a lot of deep details!

#rustweek with @ciura_victor@hachyderm.io - the brilliantly named duct tape chronicles. C++ isn't going anywhere [soon], and rust is becoming more popular, so finding a way to get a good interop is important to getting these languages to work together. A hard problem to solve, especially for moving targets.

#rustweek and Rust in Production being recorded live! Talking about some language design, and other rust history things with Niko Matsakis.

#rustweek with @alice_i_cecile@mastodon.gamedev.place - Breaking things can open up great opportunities, A++. Me (ben) has been doing web services dev for a while, and its always nice to see people in completely different areas of coding running into the same problems, we're not alone 😅

#rustweek and @pietroalbini@hachyderm.io talking about how to make errors better by looking at how rust does it in the compiler. Bad errors are bugs, and error messages are first class citizens of your application. Test your errors, remove the unhelpful stuff, and make it pretty and parsable by humans quickly!

Rust Week 2025 let's goooo #rustweek

#rustweek conference done! That's all they wrote!

#rustweek with Ralf Jung - minirust is an interpreter which can run a spec to help test (and encourage) the formal definition of rust. Removing the "mistakes" of languages gone past, and helping to define rust through testing the language specification directly through running real outputs to help remove undefined behaviour.

#rustweek Martin Larralde - writing bio libraries in rust instead of c. Going from MiB/s to GiB/s by moving language. Saving tax payers money by getting results in minutes instead of days, straight execution optimisation.

#rustweek and Waffle reinventing trait objects. A peak behind the hood of how rustc is representing trait objects in memory. Congrats on stabilising this in recent rustc version! Meow

#rustweek Day two! Full of coffee and croissant's. Let's gooooooo.

Michael "compiler-errors" Goulet - a deep dive into the compiler frontend. Not a talk for rust beginners, but definitely interesting when you have some knowledge about compilers. Of course the compiler frontend is just rust, but I never thought to look 😅

#rustweek Michał “FractalFir” Kostrubiec - rust has a modular compiler which can enable the translation of rust (through mir) into c, but beware, basic operations dont always translate and they need some manual massaging to get similar outputs.

#rustweek Thanks Rose Peck, I now have a reason for my gut distrust for floating points. Dont get me wrong, floating points are a nice tool, but this talk solidified my distrust for floating point math.

Jos Feenstra on developing the game Polders with Bevy. "I can trust the people writing the libraries, which allows me to write chaotic rust to get things out there fast" (paraphrased of course). #rustweek

A Part 2 to follow Part 1 of "Setting up a Matrix homeserver with kubernetes": @b_n@medium.com

In this one, we're connecting a Matrix homeserver to a slack workspace with the use of a Relay AppService. That's a lot of words, but what it means: Slack users can chat with Matrix users, and neither of them need an account on each others networks - bridging communities.

Part 3 will be for that use case where people want a single identity across both platforms (e.g. when they do have access to both platforms).