Built KharchaFlow π
A smart expense tracking web app that helps users manage income and expenses, visualize spending habits, and gain actionable financial insights through analytics.
π kharchaflow.vercel.app
#WebDevelopment #FinanceTracker #JavaScript #FullStackDevelopment
2
βοΈ Frontend Backend, Automated
Why juggle multiple tools when you can build everything in one seamless workflow?
With MetaInside, AI handles the heavy lifting across your entire stack:
π¨ UI components
βοΈ APIs & backend logic
π Smart contract and blockchain interactions
Spend less time switching between tools and more time building what matters.
One workflow. One platform. Endless possibilities. π
#Web3 #AI #dApps #NoCode #Blockchain #FullStackDevelopment
2
8
76
π Day 31 - Restarting My Full-Stack Journey
Today was one of the most exciting milestones in my backend journey so far.
Instead of learning isolated concepts, I built a complete backend project and connected multiple technologies together to create a real-world API.
π οΈ Project Built:
π Contact Manager API
Built using:
* Node.js
* Express.js
* MongoDB
* Mongoose
* JWT Authentication
* bcrypt
π What I learned today:
β
Express Project Structure
* Routes
* Controllers
* Models
* Middleware
* Config Files
β
MVC Architecture
* Separating business logic from routes
* Writing cleaner and scalable code
β
MongoDB & Mongoose
* Creating Schemas
* Creating Models
* Performing CRUD Operations
* Database Relationships using ObjectId references
β
User Authentication
* User Registration
* User Login
* Password Hashing with bcrypt
* JWT Token Generation
β
Authorization
* Protected Routes
* Token Validation Middleware
* Accessing authenticated user information
β
Custom Middleware
* Authentication Middleware
* Centralized Error Handling Middleware
β
Environment Variables
* Storing secrets securely
* Database connection strings
* JWT secret keys
π οΈ Features Implemented:
β
Register User
β
Login User
β
Generate JWT Token
β
Create Contact
β
Get All Contacts
β
Get Single Contact
β
Update Contact
β
Delete Contact
β
Protected API Routes
π‘ Biggest takeaway:
Today was the first time I felt like I was building a real backend application instead of just experimenting with APIs.
Understanding how authentication, databases, middleware, controllers, and routes work together gave me a much clearer picture of how modern backend systems are structured.
From simple Express servers to a complete authenticated CRUD API , the journey is getting more exciting every day π
#100DaysOfCode #FullStackDevelopment #BackendDevelopment #NodeJS #ExpressJS #MongoDB #Mongoose #JWT #WebDevelopment #LearningInPublic #ChaiCode
@Hiteshdotcom @piyushgarg_dev @yntpdotme @surajtwt_ @ChaiCodeHQ @nirudhuuu
Jun 12
π Day 30 - Restarting My Full-Stack Journey
Today was a very practical backend development day.
Instead of focusing only on theory, I spent most of my time building APIs with Express.js and understanding how routing and middleware work behind the scenes.
This was one of those days where concepts started feeling much more real because I could actually see requests moving through my application.
π What I learned today:
β
Express Fundamentals
* Creating Express applications
* Understanding request and response objects
* Working with JSON data using:
app.use(express.json())
* Sending responses using:
* `res.send()`
* `res.json()`
* `res.status()`
* `res.redirect()`
* `res.sendStatus()`
β
Route Parameters & Query Parameters
Worked with:
/menu/:id
and
/search?q=biryani
Understanding the difference between:
* `req.params`
* `req.query`
β
HTTP Methods in Express
Implemented:
* GET
* POST
* PUT
* PATCH
* DELETE
Built CRUD-style APIs and understood where each method should be used.
β
Express Routing
* Route handlers
* Dynamic routes
* Wildcard routes
* Route chaining using:
app.route()
β
Middleware Deep Dive
Learned how middleware works in Express:
* Request logging middleware
* Timing middleware
* Authentication middleware
* Authorization middleware
Understanding:
next()
and why forgetting it can cause requests to hang forever.
β
Authentication & Authorization
Built custom middleware for:
* Token validation
* User identification
* Role-based access control
Understanding the difference between:
* Authentication β Who are you?
* Authorization β What are you allowed to do?
π οΈ Practical Work
Built multiple Express applications that included:
β
Basic Express Server
β
Route Parameters
β
Query Parameters
β
CRUD Operations
β
Request Logging
β
Authentication Middleware
β
Role-Based Authorization
β
Custom Response Handling
π‘ Biggest takeaway:
Today made me realize that middleware is one of the most powerful concepts in backend development.
Instead of writing the same code in every route, middleware allows us to handle logging, authentication, validation, and many other concerns in a clean and reusable way.
Backend development is starting to feel much more structured and scalable now π
#100DaysOfCode #FullStackDevelopment #BackendDevelopment #NodeJS #ExpressJS #JavaScript #APIs #Middleware #LearningInPublic #ChaiCode #DAY1 #DAY30 #100DaysOfSilence
@Hiteshdotcom @piyushgarg_dev @yntpdotme @surajtwt_ @ChaiCodeHQ
1
14
Before anyone sees a beautiful website, there are countless moments like this behind the scenes. ππ»
Developer's daily reminder: If there's no bug, are you really coding? π»
#OsitexCreativeHub #WebDeveloperLife #FullStackDevelopment #TechJourney #DebuggingMode
1
6
123
Jun 12
Day 29/90 π
Solved LC 160 & LC 15 today.
Also reviewed the state of our Research Application Portal and planned the next phase: University Registration, Synopsis Evaluation, Thesis Evaluation, Viva Management, and Admin Dashboard π»
#100DaysOfCode #DSA #FullStackDevelopment
8
59
Jun 12
π Day 30 - Restarting My Full-Stack Journey
Today was a very practical backend development day.
Instead of focusing only on theory, I spent most of my time building APIs with Express.js and understanding how routing and middleware work behind the scenes.
This was one of those days where concepts started feeling much more real because I could actually see requests moving through my application.
π What I learned today:
β
Express Fundamentals
* Creating Express applications
* Understanding request and response objects
* Working with JSON data using:
app.use(express.json())
* Sending responses using:
* `res.send()`
* `res.json()`
* `res.status()`
* `res.redirect()`
* `res.sendStatus()`
β
Route Parameters & Query Parameters
Worked with:
/menu/:id
and
/search?q=biryani
Understanding the difference between:
* `req.params`
* `req.query`
β
HTTP Methods in Express
Implemented:
* GET
* POST
* PUT
* PATCH
* DELETE
Built CRUD-style APIs and understood where each method should be used.
β
Express Routing
* Route handlers
* Dynamic routes
* Wildcard routes
* Route chaining using:
app.route()
β
Middleware Deep Dive
Learned how middleware works in Express:
* Request logging middleware
* Timing middleware
* Authentication middleware
* Authorization middleware
Understanding:
next()
and why forgetting it can cause requests to hang forever.
β
Authentication & Authorization
Built custom middleware for:
* Token validation
* User identification
* Role-based access control
Understanding the difference between:
* Authentication β Who are you?
* Authorization β What are you allowed to do?
π οΈ Practical Work
Built multiple Express applications that included:
β
Basic Express Server
β
Route Parameters
β
Query Parameters
β
CRUD Operations
β
Request Logging
β
Authentication Middleware
β
Role-Based Authorization
β
Custom Response Handling
π‘ Biggest takeaway:
Today made me realize that middleware is one of the most powerful concepts in backend development.
Instead of writing the same code in every route, middleware allows us to handle logging, authentication, validation, and many other concerns in a clean and reusable way.
Backend development is starting to feel much more structured and scalable now π
#100DaysOfCode #FullStackDevelopment #BackendDevelopment #NodeJS #ExpressJS #JavaScript #APIs #Middleware #LearningInPublic #ChaiCode #DAY1 #DAY30 #100DaysOfSilence
@Hiteshdotcom @piyushgarg_dev @yntpdotme @surajtwt_ @ChaiCodeHQ
Jun 11
π Day 29 β Restarting My Full-Stack Journey
Today I went deeper into Node.js and learned what actually happens behind the scenes when JavaScript runs outside the browser.
This was one of those topics where understanding the internals made many previously confusing concepts finally click.
π What I learned today:
β
How JavaScript Runs in Browsers vs Node.js
* Browsers provide Web APIs
* Node.js provides Node APIs
* Both use JavaScript but have different runtime environments
β
Understanding Node.js Architecture
* V8 JavaScript Engine
* Node.js APIs
* C/C Bindings
* libuv
* Event Loop
Understanding how all these components work together to execute JavaScript outside the browser.
β
Node.js Process Lifecycle
Learned what happens when we run:
```bash
node index.js
```
* A Node.js process is created
* A main thread is allocated
* Top-level code starts executing
* Modules are loaded
* Event callbacks are registered
* Event loop starts processing tasks
β
Event Loop Deep Dive
Explored major event loop phases:
* Timers
* I/O Poll Phase
* `setImmediate()`
* Close Callbacks
And how Node.js decides when to continue or exit the process.
β
Main Thread vs Thread Pool
Learned:
* JavaScript runs on the main thread
* CPU-blocking code can freeze execution
* libuv uses a thread pool for certain expensive operations
* Why blocking code like `while(true)` should be avoided
β
Understanding Asynchronous Execution
Practiced examples using:
* `console.log()`
* `setTimeout()`
* Event Loop execution order
And understood why asynchronous callbacks execute after synchronous code completes.
π οΈ Practice:
* Explored Node.js execution flow
* Tested event loop behavior using timers
* Experimented with callback execution order
* Learned how blocking code impacts application performance
π‘ Biggest takeaway:
Before today, I knew that Node.js was "single-threaded."
Now I understand what that actually means.
Learning about the event loop, libuv, the main thread, and asynchronous execution helped me understand how Node.js handles thousands of operations efficiently without blocking the application.
The deeper I go into backend development, the more fascinating it becomes π
#100DaysOfCode #FullStackDevelopment #BackendDevelopment #NodeJS #JavaScript #EventLoop #WebDevelopment #LearningInPublic #ChaiCode #dayxwebtoon #TrendingforPavel #100DaysOfSilence #DAY29
@Hiteshdotcom @nirudhuuu @yntpdotme @ChaiCodeHQ @surajtwt_ @codedailybot @_100DaysOfCode @100days
1
44
Jun 12
Build a Real-World Social Media Platform from Scratch!
Join our 1-Month Full Stack Developer Internship and gain hands-on experience with React, Node.js, MongoDB, REST APIs, and real-world project deployment.
#FullStackDevelopment #Internship #CubenSquare
10
Multilingual AI is the future. Making technology more accessible through natural conversations. π
#AI #VoiceAI #FullStackDevelopment #MachineLearning #FutureTech
1
12
Jun 11
Day 16/75
Today's JavaScript Progress:
-Strings
-if/else Conditions
-Arrays
15 days ago I was learning HTML.
Today I'm writing JavaScript logic.
Small daily improvements lead to big results. ππ»
#75DaysOfCode #JavaScript #FullStackDevelopment #Coding #WebDevelopment #BuildInPub
12
Next generation apps will not just have interfaces.
They will have conversations. ππ€
#AI #VoiceAI #FullStackDevelopment #MachineLearning #FutureTech
1
15
Jun 11
Day 28/90 π
Solved LC 28 using KMP and LC 11 using Two Pointers.
Also implemented the RRC review workflow for our Research Application Portal with applicant/expert roles, JWT auth, dashboards, and review actions π»
#100DaysOfCode #DSA #FullStackDevelopment #BuildInPublic
1
2
29
Jun 11
Hey everyoneππ½ !!
Starting my Full Stack Development journey in public..
I'm currently building small projects and making mistakes along the way.. Looking forward to sharing what I build, what I learn along the way..
#100DaysOfCode #WebDevelopment #FullStackDevelopment
9
Jun 11
π Day 29 β Restarting My Full-Stack Journey
Today I went deeper into Node.js and learned what actually happens behind the scenes when JavaScript runs outside the browser.
This was one of those topics where understanding the internals made many previously confusing concepts finally click.
π What I learned today:
β
How JavaScript Runs in Browsers vs Node.js
* Browsers provide Web APIs
* Node.js provides Node APIs
* Both use JavaScript but have different runtime environments
β
Understanding Node.js Architecture
* V8 JavaScript Engine
* Node.js APIs
* C/C Bindings
* libuv
* Event Loop
Understanding how all these components work together to execute JavaScript outside the browser.
β
Node.js Process Lifecycle
Learned what happens when we run:
```bash
node index.js
```
* A Node.js process is created
* A main thread is allocated
* Top-level code starts executing
* Modules are loaded
* Event callbacks are registered
* Event loop starts processing tasks
β
Event Loop Deep Dive
Explored major event loop phases:
* Timers
* I/O Poll Phase
* `setImmediate()`
* Close Callbacks
And how Node.js decides when to continue or exit the process.
β
Main Thread vs Thread Pool
Learned:
* JavaScript runs on the main thread
* CPU-blocking code can freeze execution
* libuv uses a thread pool for certain expensive operations
* Why blocking code like `while(true)` should be avoided
β
Understanding Asynchronous Execution
Practiced examples using:
* `console.log()`
* `setTimeout()`
* Event Loop execution order
And understood why asynchronous callbacks execute after synchronous code completes.
π οΈ Practice:
* Explored Node.js execution flow
* Tested event loop behavior using timers
* Experimented with callback execution order
* Learned how blocking code impacts application performance
π‘ Biggest takeaway:
Before today, I knew that Node.js was "single-threaded."
Now I understand what that actually means.
Learning about the event loop, libuv, the main thread, and asynchronous execution helped me understand how Node.js handles thousands of operations efficiently without blocking the application.
The deeper I go into backend development, the more fascinating it becomes π
#100DaysOfCode #FullStackDevelopment #BackendDevelopment #NodeJS #JavaScript #EventLoop #WebDevelopment #LearningInPublic #ChaiCode #dayxwebtoon #TrendingforPavel #100DaysOfSilence #DAY29
@Hiteshdotcom @nirudhuuu @yntpdotme @ChaiCodeHQ @surajtwt_ @codedailybot @_100DaysOfCode @100days
Jun 10
π Day 28 - Restarting My Full-Stack Journey
Today was another exciting backend day as I moved beyond theory and started understanding how web servers, Express.js, TypeScript tooling, and backend project workflows work together.
I also built my first basic backend Todo CRUD application to put these concepts into practice.
π What I learned today:
β
Understanding Web Servers
* How clients and servers communicate
* Ports and server processes
* Why servers continuously listen for incoming requests
β
Node.js HTTP Module
* Creating a basic web server using the built-in `http` module
* Understanding:
* Request (`req`)
* Response (`res`)
* Handling different routes and HTTP methods manually
β
Dependency Management
* Understanding:
* `node_modules`
* Dependency trees
* `package-lock.json`
* Why dependency locking is important for consistent environments
β
Introduction to Express.js
* Creating APIs with Express
* Routing using:
* `app.get()`
* `app.post()`
* Parsing JSON using:
* `express.json()`
β
TypeScript Project Setup
* `tsconfig.json`
* `rootDir`
* `outDir`
* Compiling TypeScript into JavaScript
β
Development Workflow Improvements
* Local TypeScript installation
* `tsc-watch`
* Auto compilation and server restart during development
β
Type Definitions
* Understanding `@types/*`
* Installing:
* `@types/node`
* Express type definitions
* Better IntelliSense and type safety
β
Runtime Validation
* Introduction to Zod
* Understanding why TypeScript alone is not enough for validating external inputs
π οΈ Practical Work
Built a basic Todo CRUD API using:
* Node.js
* Express.js
* TypeScript
Implemented:
β
Create Todo
β
Read Todos
β
Update Todo
β
Delete Todo
This was my first step toward building real backend applications.
π‘ Biggest takeaway:
Frontend taught me how users interact with applications.
Backend is teaching me how applications actually process requests, manage data, and communicate with clients behind the scenes.
Building my first CRUD API made the client-server relationship much clearer and made backend development feel far less intimidating.
Excited to keep moving deeper into Node.js, Express, APIs, validation, and databases π
#100DaysOfCode #FullStackDevelopment #BackendDevelopment #NodeJS #ExpressJS #TypeScript #WebDevelopment #LearningInPublic #ChaiCode #DaysCount #DAY1 #DAY28 #trendingsongs #100daysofadam
@Hiteshdotcom @piyushgarg_dev @nirudhuuu @surajtwt_ @yntpdotme
49
Jun 11
TypeScript tip π
"./src/**/*.ts" in your tsconfig include field means:
./src/ β src folder **/ β every subfolder recursively *.ts β any TypeScript file
one line. tells TypeScript exactly where to look.
#TypeScript #fullstackdevelopment #buildinpublic
15
Jun 11
Turn your passion for technology into a rewarding career with our Full Stack Web Development Program.
VISIT YOUR NEAREST CENTRE NOW!
Contact: 91 98201 27177
#FullStackDevelopment #WebDevelopment #Coding #Programmer #Developer #HTML #CSS #JavaScript #WordPress #CareerInIT
14
π Need a Full Stack Development Service?
From idea to deployment, our expert team handles the complete development journey so you can focus on growing your business.
π© Let's build something amazing together.
#FullStackDevelopment #WebDevelopment #SoftwareDevelopment
2
3
Jun 10
Day 27/90 π
Solved LC 636 Exclusive Time of Functions and completed my current Stack journey on LeetCode.
Next up: Monotonic Stacks.
Also planned Applicant, Expert, and Admin workflows for our Research Portal with my teammates π»
#100DaysOfCode #DSA #FullStackDevelopment
1
8
78
Jun 10
Day 15/75
Started JavaScript today! β‘
β
V8 Engine
β
let, var & const
β
Data Types
β
JavaScript Fundamentals
From static websites to interactive applications.
#75DaysOfCode #JavaScript #FullStackDevelopment #WebDevelopment #BuildInPublic
1
2
25
Jun 10
Father's Day is June 21.
Every year, the card aisle offers the same options for dads who'd rather be on a trail than at brunch: neckties, golf balls, grill jokes.
That's the gap I built TerraGreetings to fill β and it's also the reason I believe AI-assisted building is a professional skill, not a party trick.
The product side:
I run a nature-inspired greeting card platform for people whose best stories happen outside. Our Father's Day collection skips the clichΓ©s entirely β cards for the dad who taught you to read a map, the grandpa with the tackle box, the stepdad who chose to show up, the new dad still figuring it out. Print at home in minutes, or send a digital link the same day.
The build side:
I designed and shipped the entire platform myself β the product in @Cursor with @AnthropicAI's Claude Opus; the visuals in @Adobe Firefly, @grok Imagine, and @FlowbyGoogle for both static card art and motion β no dev team, no agency, no design studio.
What's actually running in production:
β Full-stack product β Next.js, Supabase, Clerk, Stripe subscriptions, client-side print-ready PDFs, shareable card links
β AI creative pipeline β Custom prompt builder that assembles image generation briefs from character data, 63 national park locations, mood/style/composition rules. Not "make me a card." Shot-list-level art direction.
β Original IP β Wild Reactions, a structured character universe (10 crews, 45 defined characters) that keeps AI output consistent instead of random
β Admin tooling β Bulk upload, scheduled publishing, marketing calendar, pricing controls β the unglamorous ops layer that makes a one-person company viable
I spent years as a Knowledge-Centered Service (KCS) Program Manager at Broadcom β working with a dedicated team running KCS end-to-end: structured content governance, enterprise search tuning, article health and reuse metrics, and the SEO/AEO workflows that help people actually find answers without opening a ticket. TerraGreetings is what happened when I stopped using AI to assist that work and started using it to build a company.
The skill that transfers everywhere: knowing what to ask for, what to reject, and when the model is wrong.
If your dad's happy place looks like a trail, a river, or a campfire β there's finally a card for him.
If you're looking for someone who integrates AI across product, engineering, creative direction, and content systems β I'd love to connect.
What are you building with AI right now?
#BuildInPublic #AI #PromptEngineering #FullStackDevelopment #NextJS #CreativeDirection #IndieFounder #TerraGreetings #FathersDay #FathersDay2026
1
1
195