When I first heard term "vibe coding," I honestly thought it meant coding while listening to music. But nah, it is just a fancy way for people to justify taking shortcuts instead of actually learning the skill.

Thanks for the support, Hajar.

YouTube video by Block Open Source Codename Goose: A Local Open Source AI Agent Built on MCP

Quick 10-minute primer on how goose works as an AI agent, how it fits into the broader AI ecosystem, and how it uses MCP to interact with tools, automate tasks, and enhance productivity.

youtu.be/hFFwgyQeEQc

Day 100 of #100DaysOfCode

Today,

- I tried to fix the failing tests on the app.
- I troubleshooted issues with GitHub actions
- I modified the app README.

#buildinpublic

There's no particular plan. The only thing that is certain is to keep this momentum with project based learning, keep working on my problem solving skills via leetcoding and actively contributing to open source

Day 99 of #100DaysOfCode

Today,

- I continued writing tests for the expense tracker app.
- I spent time understanding and fixing bugs.

#buildinpublic

Day 98 of #100DaysOfCode

- I solved a LeetCode problem(Roman to Integer).
- I published a blog on the week 14 recap of #100DaysOfCode

#buildinpublic

Day 97 of #100DaysOfCode

Today, I solved LeetCode problem set on (Trapping Rain Water). And studied fundemantals of data structure.

#buildinpublic

Day 96 of #100DaysOfCode

Today, I made contribution to open source project. Issue description: custom icon and app name dose not apply to firefox mobile shortcut

#buildinpublic

What a nice way to end the week/month.

Day 95 of #100DaysOfCode

Today, I picked up where I left off, debugged the issues.

#buildinpublic

Day 94 of #100DaysOfCode

Today, I continued with the writing test for the app. And a whole lot of troubleshooting. I am still on it.

#buildinpublic

Day 93 of #100DaysOfCode

Today, I started writing test for the expense tracker app. I can't wait to be done with this app. I really want to pick up a new project.

#buildinpublic

Day 92 of #100DaysOfCode

Today, on the expense tracker app, I worked on the Firebase API authentication end on the backend for the register and login form.

#buildinpublic

After 28 hours of intense coding and reading documentation, my code finally passed all the test cases.

Day 91 of #100DaysOfCode

- I solve a LeetCode problem(Candy)
- Published a blog post on week 13 recap of #100DaysOfCode

#buildinpublic

Day 90 of #100DaysOfCode

- I solved a LeetCode problem(Gas station)
- Read a programming book (Cracking the coding interview)

#buildinpublic

Yess! Thanks for the support

Day 89 of #100DaysOfCode

I worked on the rest of the issues and I was able to fix a larger part of it.

#buildinpublic

Thanks for the kind words!

Day 88 of #100DaysOfCode

I was able to fixed part of the issues. I will continue to figure out other issues.

#buildinpublic

Thank you

Day 87 of #100DaysOfCode

No significant progress today, as I got stuck on debugging for seven hours plus, going from one troubleshooting issue to another. We go again later!

#buildinpublic

Day 86 of #100DaysOfCode

I realized issues with the receipts section so I worked on both the backend and the frontend of it.

#buildinpublic

The joy that follows when all test cases pass in your code is palpable! A well-spent night!

- Middleware for Protected
Routes: Verifies Firebase tokens before allowing access.

#buildinpublic

Day 85 of #100DaysOfCode

I worked on:
- User Registration: Creates a user using Firebase Admin SDK and logs them in automatically.
- User Login: Authenticates with Firebase REST API and returns a valid ID token.
- Secure Firebase API Key Handling: Uses environment variables for security.

Day 84 of #100DaysOfCode

- I solved LeetCode problem(Product of array except self)
- Published a blog post on week 12 recap for #100DaysOfCode

#buildinpublic

Day 83 of #100DaysOfCode

- I solved leetcode questions
- I stared learning fundamentals of DSA

#buildinpublic

Day 82 of #100DaysOfCode

Today, while testing the app, I found out that the form submission for the report is working but the report generation is not behaving as expected. I realized the issue is related to the form handling on the server side. Literally what I tackled today.

#buildinpublic