Today's software development toolbox is powerful, offering lots of features and quick development. But once requirements call from stepping away from the beaten path, it's the understanding of the inner workings of the tools that will enable you to utilize them to full potential.
My name is Patrik, and I develop Java backend applications in Jakarta EE. For me, it's all technology, zero magic.
I was managing a few Kubernetes clusters over the last few years and the developer experience on Azure vs AWS is... quite different. These are notes from the operations guide I had written on the topic of upgrading the clusters.
Web applications that use Unpoly will primarily use HTML markup and custom attributes to drive interaction. It is not against the philosophy to use JavaScript — quite the opposite. Unpoly offers a very open API that lets custom code and Unpoly interact very comfortably.
While majority of Unpoly magic happens on the client-side the server still stays in control. Unpoly utilizes HTTP headers in request and response to steer both server and client-side actions
I am great fan and supporter of Unpoly. It enables you to create very responsive user interfaces while enabling very reasonable server-side model and allows you to keep most of the interaction decisions at server side. I had the opportunity to speak at Devoxx Belgium about it in 2024, and this is textual version of that talk.
First step in resurrecting the blog was to make it deploy to Netlify. It ended up being quite straightforward.