It was a fun week. There was a bit of laziness, for sure, but also some work done. I didn’t create a video this week and took a bit of a break. I think it is as important to upskill as it is to maintain streaks of uploading.
“The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn.”
— Alvin Toffler
This week was a bit frustrating, but I really want to continue what I am working on. However, life is pushing me in a different direction, and I am so confused. I have responsibilities to perform and situations to tackle. It is a bit hard to live ahead, but I will stay with my three pillars: curiosity, consistency, and grit.
This week, I created one video, and that’s it. It was just a bit of a hectic weekend, so I didn’t have much free time. However, on weekdays, I was able to learn about subdomains, LLMs, and more. I read a lot about writing, and at this point, I am overwhelmed with writing advice. I think it is high time to write consistently.
It was a bit of lazy day, not that lazy though, did a lot of things while being lazy. I had been doing a lot of things in the past few weeks, so this week I decided to take things a little slowly. If I just keep on being that productive, it would be a burnout soon.
So, I created a new kind of video using a presentation-style approach, wrote a bit of python, and debugged it a ton, and now I see why tests are handy. I don’t have to debug the issue every time I make a change here, If run tests, I know exactly which test failed and where to look out for so easily.
This week was really fun and exciting, I am continuing with more productive weeks. I was able to fix a lot of things this week. I created three videos this week. Worked on the side project with 2 live streams. Was able to demonstrate to the team at my work about the AI Agents. It was a great week.
Next week I am planning to wrap up the series of CRUD Applications with Golang, Netlify cloud functions, and LibSQL by adding authentication and authorization.
It was an exciting week, I did complete a lot of things on my work side, I had a bit of change in the routine of my work, an hour early, which makes me really productive and gets a lot of things done quite early and more importantly, I am now able to dedicate myself more time to learning new things.
This week, I didn’t release any videos, I was a bit exhausted and wanted to slow down a little, but I was not sitting idle, I was evaluating a project idea for some future videos, and the project is ready. Next week, expect some high-quality and in-depth videos.
We have explored GET, POST, PUT, and PATCH methods in our previous entries for this series. It is the final entry for all the HTTP methods which is going to be the DELETE method. In this entry of the series, we will take a view on how to construct and request an HTTP DELETE Method to an API Endpoint.
The DELETE Method is quite simple. You just provide the URI of the resource. Most often, the request body is not needed. That request will simply delete the request entity from the server (in the database or wherever the resource is stored).
In previous sections of this series, we’ve covered the GET, POST, and PUT methods. Now, we will explore the PATCH method, which differs from the others in several key ways. The PATCH method is somewhat more flexible and depends on how the server or API you’re working with is designed.
In this section, we’ll focus on understanding what the PATCH method is and how to use it. While we will dive deeper into building and structuring a full CRUD API later in the series, the focus here will be on the what and why of the PATCH method, not the how.
It was an exciting week. I was pretty excited from the end of the past week with a new beginning to my work-life goal. After completing one, I have a new challenge in front of me: diving into the world of cutting-edge LLMs, agents, and Workflow. This can’t be more exciting.
This week, I was researching and exploring the frameworks, libraries and tools to create Agentic Workflows with LLMs, I can’t share much, but I see myself creating content around the things I will learn at my work/day job.
We are in 2025! Happy New Year
It feels good to carry this newsletter through the year from July 2024 to January 2025 and counting ….
It was a huge roaring start to the year, I created a video on the 1st, and that too a big video, I put in everything I could know about the thing I wanted to talk about in little as I could, and it’s gaining views and is likely to spike as the Golang 1.24 release date approaches. 200 IQ move there.