In the tapestry of these past moons, I, a wanderer of codes, have traversed realms, crafting visions in diverse programming tongues. From the ethereal realms of low-level C++, where custom network protocols dance, to the sacred shores of a nascent data lake, where a NiFi pipeline unfurls its serpentine beauty. Alas, amidst this symphony of creation, I stumbled upon a disheartening truth—a recurring melody in my recent mistakes, born of shallow introspection and hasty assumptions.

In the past few days I decided to spend some time playing with the spring framework. My favorite build environment for JAVA is gradle, so the first step was to figure out how to have Webpack and NPN seamlessly work together. I also like for my code to support being compiled from both Windows and Linux. The major issue was how to configure the gradle build file. In fact, by following the instruction found online, WebPack and NPN would fail on Windows for multiple reasons (one of them was path related).

For years I underestimated the importance of fixing the capacity of my data structures. Today while I was tracking a nasty bug in one of my software I finally realized that has to stop. After some thinking these are the conclusions I arrived: By assigning a size… It is possible to understand more easily what “pipe” has filled in situations where the memory allocation keeps slowly escalating (either because it is not released or because new data is generated more frequently than consumed) and consequently not being overwhelmed during the fixing process; It is possible to keep track of performances by being warned about structures that are frequently filled; It is possibly to keep under control the memory footprint of the software.

Today I was playing with hugo and I wanted to automate my pipeline a bit so I made a script that looked like this: eval 'rm -rv !("hugo"|*.sh)' But I quickly discovered that even if that would work on a shell it would not work on a script. That is because a script doesn’t know how to process globbing (round parentesys expansion). To fix that I enabled glob changing the script as follows: