So this post touches on some Python concepts in async/await territory. I will not cover event loops nor how to interact with them, but something I uncovered/unearthed in a quest to make something work that was synchronous only. I will use the word async which itself is a shortening of the word asynchronous.

So recently I had the opportunity to make a proof of concept (PoC) in the Go language to share with some fellow developers. They are mostly Java developers and therefore I decided to make the PoC a MVC style REST API that returns JSON with a single Entity for now.

So these last few days I have been working more on this project. I can actually say it brings me great joy to do this project. It is the combination of tight restrictions that allows my creativity to flow and see just how far we can take this concept and library.

In the previous post I briefly highlighted my side project. This article will do a little more in depth.

I am currently working on and off on a side project and I named it crucible. It is to do with Shell scripts and I will explain briefly what it does and how.

Anyone who grew up watching the Pokémon anime in the 90s will think are we that old already and secondly about how Ditto plays a role in there. Ditto is a very cool Pokémon who could assume the form of any of the other Pokémon including moves.

This post will have a lot of code and Java at that, so warning has been given. I happened on this little gem in the Java standard library that allows you to make a nice asynchronous model of execution with some guidance. Only the thing missing from the documentation of the Java standard library, in contrast to the one provided by Python, are examples on how to use this one. There is an example on the main page of the package. So this is my attempt at creating the implementation of these interfaces and hooking them up together based on the wordings in the documentation.

This post is about a thin line between a helpful utility and full on magic show.

So for the smart people out there they might have already figured out that the result for 153 is the same as for 135,315,351,513 and 531. This means that we can calculate the result for all of those once and just check if the result of that calculation is in that list. Which is the case for the number 153.

The next mini optimization we can do is to bail out earlier because when summing the number and we overshoot the original then we can stop immediately. For example 9 ** 6 is a big number and so with bigger numbers it makes sense to bail out earlier.