I just skimmed/read this article. It states that PHP is just as good as Rust/C/Java. That the opinion that it is bad is just 10 years out of date.

I have gotten some experience using the Flow constructs in a real scenario and learned some lessons. Therefore I wanted to make some code changes to my original design.

So I recently started using Spring WebFlux and Project Reactor as stated in this post. One more thing I came across as I was debugging why a certain job was not running was that if you do not catch all exceptions and do not have a doOnError statement it will just keep that thought hidden from you and all to itself.

I started a project recently using Spring WebFlux which is based upon Project Reactor. I chose this one because it was new and I thought for the client it would suit the best as a lot of data was involved.

This year I tried to do the advent of code again, and I got to day 13 this time. Not because I got stuck, it is mainly due to time management issues.

So this will hopefully convey the message on how to model your code in order to have things done in a nicer way.

This idea comes from JavaScript when there were no classes yet as there are now in ES6. You would write something like this:

This article concerns Web Components, Mozilla, Google and something GitHub created called Catalyst touching on ideas and that sometimes pride can get in the way of good things.

To be honest I have no idea what you can do with the following pattern and if it is good at all. It just a thought I had and it felt like there was something there, so I decided to write it down. Hopefully you can use the following pattern for something.

This post is about why you want immutable objects and how to achieve that in various ways. I specify the language as Java this time because I want to showcase the Quarkus framework. This pattern can be used in any language and framework combination using the tools available in that language of course.