Day 42–43 of #100DaysOfCode

- Deep-dived into X.com’s OAuth 2.0 flow with PKCE and got a working demo app up and running for X APIs + authorization flows.
- Played with Node.js file modules and tried out different Multer strategies for handling uploads in efficient, real-world use cases.

Day 39–41 of #100DaysOfCode

- Implemented **social authorization** and dug into Twitter APIs (v1.0a vs v2.0). Honestly, their complexity had me going in circles, but the experiments with the official docs paid off.

Day 38 of #100DaysOfCode

- Read LLM Insiders and explored the concept of cosine similarity — one of the core mechanisms behind how LLMs reason and compare meanings.

Day 37 of #100DaysOfCode

- Continued exploring GitLab — creating templates felt pretty similar to GitHub’s approach.
- Created a few issues, feature requests, and merge requests (basically GitLab’s version of PRs).

Day 36 of #100DaysOfCode

- Started exploring GitLab today. The look and feel are obviously different from GitHub, but it still feels a bit off for me right now.
- Just tinkered around the platform — nothing major coded, more about getting familiar with the environment.

Day 35 of #100DaysOfCode

- Explored different tracking and analytics strategies. Came across @posthog.com docs and got introduced to how product analytics can be set up.
- Set up basic event tracking and analytics with PostHog to test how it works in practice.

Day 32–34 of #100DaysOfCode

- Spent time diving into different middleware strategies for Node.js projects. Looked into ways to strengthen backend security and safeguard APIs.
- Applied security-focused middleware and experimented with adding layers of protection for the backend.

Day 30–31 of #100DaysOfCode

- Continued experimenting with AI agents while exploring LangChain, LangSmith, and LangGraph. Signed up for LangChain Academy to cover their fundamentals in a structured way.

#WebDev #AI #LangChain #100Devs #LearnInPublic #BuildInPublic

Day 29 of #100DaysOfCode

- Focused on strengthening my @nodejs.org backend knowledge by deep diving into the docs. Explored `process.nextTick`, `setImmediate`, `setInterval`, and `setTimeout`, and studied how they tie into the event loop.

Day 25 of #100DaysOfCode

- Went deeper into how promises and async/await work in Node.js — focusing on how they handle asynchronous operations and error flow.

Day 24 of #100DaysOfCode

- Spent the day tackling TypeScript compilation errors — which pushed me to carefully consider the different response types my code might return. It also sharpened my code-review process.
- Cleaned up the codebase by resolving type issues and made the res. predictable.

Day 23 of #100DaysOfCode

- Got back into the frontend side by solving bugs and preparing code for production deployment. Realized again how careful you have to be — one small mistake can bring the whole thing down.

Day 22 of #100DaysOfCode

- Worked on an open-source project that’s migrating from JavaScript to TypeScript — got plenty of exposure to how type errors pop up and how to tackle them. Also explored @coderabbitai.bsky.social it for automated code reviews.

Day 17–21 of #100DaysOfCode

- Took some proper rest days, then shifted focus to setting up the project structure for a new backend project. Looked into the flow for implementing social logins with providers like Google and GitHub. using Oauth 2.0 strategies.

Day 16 of #100DaysOfCode

- Started learning GraphQL from the basics, following the roadmap.sh roadmap to get a structured path.
- Set up some initial GraphQL examples to get comfortable with queries and the overall syntax.

#WebDev #GraphQL #Backend #100Devs #LearnInPublic #BuildInPublic

Day 13–15 of #100DaysOfCode

- Took a couple days of proper rest, then read an interesting article on why early-stage startups lean towards being open source. Also explored how OAuth 2.0 works for handling logins through providers like GitHub and LinkedIn.