Hello from sunny and hot Vienna and welcome to another newsletter!
These weeks are a bit more quiet for me work-wise, since I’m just moving into a new office. I’ve said a few times that programmers don’t need much equipment, only a laptop and some coffee, but when you have a lot of recording gear, including a green screen and lighting, and are a fan of working ergonomically, and you own a standing desk and a treadmill, that actually adds up :-)
In July, I’m holding new online workshops again, this time on all things Quarkus. I’m planning a few more topics, such as developer productivity, if there’s enough interest, so let’s see how that works out.
I hope you’re doing well where you are, and in case it’s as hot as in most of Europe, stay cool and safe.
New Quarkus workshops in July
I’ll be holding two full-day online workshops on how to do modern, effective development with Quarkus, at the end of July. These workshops aim to boost one’s knowledge, skills, and productivity for developing and testing modern enterprise applications.
Have a look at the workshop pages and their agendas, for details:
In case both topics sound intriguing, you can book the workshop package for both days and save some money.
Right now, we don’t have the minimum number of sign-ups yet, so I hope there’s enough interest that both will take place.
Reducing your development turnaround times with Quarkus
From my point of view, one of the biggest advantages of using Quarkus is that is reduces the turnaround times while we’re developing.
dev mode especially enables to quickly get feedback of whether our code works — and with quickly I mean something between 50ms to 2s.
I’ve created two posts on how to further reduce your turnaround times. Quarkus 2.0 allows us to shrink our test waiting time with its continuous testing feature, not even because of the “continuous” aspect but because it launches and runs the tests extremely fast, usually within less than 50ms.
Have a look at the post and its video for some demonstration: Reducing test turnaround times with Quarkus 2.0
Also what’s interesting is that you can use Quarkus and the
dev mode for projects that aren’t actually Quarkus projects.
While this sounds weird at first, it works and there’s some value in, in order to execute the tests quickly as well, while we’re developing.
In the following post and video, we’ll see why that makes sense and how it works: Using the Quarkus dev mode for non-Quarkus projects
Regarding this topic, it was interesting to see that Java Guru Adam Bien also uses a similar solution, which made me feel better that it wasn’t only me writing about such “dirty hacks” :-) Check out his variant as well.
Thanks a lot for reading and see you next time!
Did you like the content? You can subscribe to the newsletter for free: