For me, the best learning process is regularly switching between learning and doing, theory and practice. The last post was research; hence, this one will be coding.
So far, we have learned the basics of Rust syntax, developed a custom Kubernetes controller, and integrated with the front-end with Wasm.
This is the 7th post in the Start Rust focus series. Other posts include:
I’ve been using the JVM for two decades now, mainly in Java. The JVM is a fantastic piece of technology. IMHO, its most significant benefit is its…
The guiding principle is creating a Kubernetes controller that watches pods’ lifecycle and injects a sidecar into them. …
Last week, I dived into the Rustlings exercises. It was a bit long, and I decided to split my understanding into two different posts. Now is the time to finish them.
This is the 4th post in the Start Rust focus series.Other posts include:
There’s a single exercise for threads. It’s a bit disappointing because it’s a weak point of mine: I’d have loved more practice.
One of the talks in my current portfolio is Migrating from Imperative to Reactive. The talk is based on a demo migrating from Spring WebMVC to Spring WebFlux in a step-by-step approach. One of the steps involves installing BlockHound: it allows to check whether a blocking call occurs in a thread it shouldn’t happen and throws an exception at runtime when it happens.
I’ve presented this talk several times in the previous week, both in its Java version and its Kotlin one. One such presentation was at Javaday Istanbul. After the talk, one of the questions I received was, “How…
To continue building my understanding of Rust, I searched for some simple Rust exercises. Hence, I dedicated my weekly personal work time to the Rustling exercises.
Greetings and welcome to rustlings. This project contains small exercises to get you used to reading and writing Rust code. This includes reading and responding to compiler messages!
I believe that this workshop is pretty neat. Thanks to everybody who contributed to it! I’ll split my notes into two posts, as Rustlings contain many (many!) exercises. Besides that, I need to learn about the more advanced themes such as threading. In those…
Last week, I drank my first cup of Rust. I learned concepts that are foreign in the languages I know: ownership, borrowing and lifetimes. This week I want to drink the second cup and see where it leads me.
It’s time to implement another exercise from the initial exam:
Given a collection of
Super, return the sub-collection of those who have a sidekick.
We need to change the model to add a
sidekick attribute of type
It all started with an informal chat with my friend Anthony. We were talking about languages, and I said that I preferred compiled ones. He then went on to mention Rust. We admitted that we were too afraid to learn it because of its perceived complexity.
After the chat, I thought about it, and I wondered why I didn’t check by myself. I did. And I became interested.
There are tons of resources on the Web on how to learn Rust. This post is a memo of the steps I followed. …
The JVM ecosystem is mature and offers plenty of libraries, so you don’t need to reinvent the wheel. Basic — and not so basic — functionalities are just a dependency away. Sometimes, however, the dependency and your use-case are slightly misaligned.
The correct way to fix this would be to create a Pull Request. But your deadline is tomorrow: you need to make it work now! It’s time to hack the provided API.
In this post, we are going through some alternatives that allow you to make third-party APIs behave in a way that their designers didn’t intend to.
Dev Advocate @Hazelcast . Former developer and architect. Still teaching, learning and blogging.