Website | https://michal.pawlik.dev |
Github | https://github.com/majk-p |
Blog | https://blog.michal.pawlik.dev |
Website | https://michal.pawlik.dev |
Github | https://github.com/majk-p |
Blog | https://blog.michal.pawlik.dev |
🎶 It's the final countdown 🎶
https://github.com/scalalandio/chimney/releases/tag/1.0.0-RC1
New video: 10 flavors of Scala's future - Scalar 2024 recap
Here are the slides and #Scala code for "How slow is your tram?" talk I gave on #ScalarConf 2024
Welcome @majkp as the next #Scalarconf speaker!
How slow is your tram?
Grab your ticket
🛒 https://sml.io/tickets
Own your own website. Own your mailing list. Own your newsletter. Own your blog and prioritise your RSS feed.
This is the stuff that works in the long term.
Chasing virality on every new shiny platform is a waste of time.
Managing resources in an integration test in #Scala can be very simple. Check out https://blog.michal.pawlik.dev/posts/scala/weaver-localstack if you want to learn how to combine #Weaver and #Testcontainers to test your code against #Localstack.
When creating software that makes heavy use of cloud infrastructure, it is wise to test the integration in the end-to-end fashion. Doing so in cloud environment is one option, but it may not be viable for all cases. It can be pricy and you cannot do it in an local environment. A popular solution to this problem is to run Localstack and test your code against it. In this post we’ll explore how to manage your Localstack resources for E2E tests using Testcontainers, Cats-effect Resource and Weaver.
🤔 Do you know that since Scala 3.3.1 LTS, the compiler can check your code for any non-unit statements?
This way, you can avoid many footguns, especially when dealing with asynchronous code. 🕵️