Still has not recovered from my long distance run decline but my pinky toe is now healed.

As usual, flood again in my area and I really detest the flood here because one time when it was the beginning of the rainy season but but summer has not closed yet, as the first flood came in due to the higher tides from the river, I saw a bunch of human and animal shit floating in the water in dense groupings coming from the west and that is I realized that the floods might be washing makeshift toilets from the communities near the fucking river.

So I decided to not do what I was doing since 2023 where I wade thru the flood and instead use my mountain bike. On the other hand, I have kept my new road bike or the racer cycling bike to keep it from the rain and not to immerse it on flood waters which is not only dirty but also salty hence it corrodes metal faster. The reason why my mountain bikes are corroded.

I been exhausted and busy reviewing a lot of my software engineering knowledge and skills for my job applications getting back to the engineering career.

I have not review front-end tools yet but mostly backend and observability tools including REST API, microservices, CI/CD, images, containers, design patterns, Java, and a lot more but I noticed I was very rusty in data structure and algorithms as there was an exam on DSU and it was not that complicated but I failed it, hence I went to review algorithms but then a second exam from another company came thru and I failed and that time it was bloody hard. Turns out I was not familiar with Palindrome related concepts such as optimal number of deletes to maintain Palindrome or LCS for Long Common Subsequence algorithm. Was asking myself why I didn't know about this LCS back in BSCS nor in MSCS and I detest that I was not familiar with LCS.

Last night I was looking into LCS implementation in Java and in C. This is the first time that I review algorithm coding not only Java but C.

I also seen examples of Industrial C compared to a typical C for classroom assignments. Not only I am not using Compiler only similar to college days but now I have my Makefile setup and so a lot of the command line becomes a one line execution of the make command. Also separated functionalities in header and c files. Extensive use of guard preprocessors for inclusion of header files, pointers, use of size_t, checks for parameter nullity and string emptiness, use of other header files apart from stdio.h, seen how to get string length without using the function strlen.

On the other hand while I am busy on reviewing my Software Engineering knowledge and skills which is vast now, I also went to enroll on an AI Engineering course from Udemy hence I am learning Python and Ollama on the sides with the use of Cursor IDE and Jupyter notebooks. Installed a lower parameter llama3.2 on my local and had run some example Python codes from Jupyter notebooks that connects to my local AI model. I tried llama3.2:1b for 1 billion parameters but it failed so as to not waste time I decided to pull llama3.2 but this is 3 billion parameters yet still run son my local hence I was able to run the Python codes connecting to my local llama3.2 successfully.

I promised myself to take a break from this exhausting technical review and today I should be at the gym doing and later doing my long distance run of 21km but LSD.