🚀 CodeAlpha Internship — Day 12/30 Another day of building, debugging, getting stuck, and learni...🚀 CodeAlpha Internship — Day 12/30 Another day of building, debugging, getting stuck, and learni...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
🚀 CodeAlpha Internship — Day 12/30
Another day of building, debugging, getting stuck, and learning. 💻
Today I continued working on my TaskFlow project, a full-stack project management application built with React.js, Node.js, Express.js, and MongoDB.
Today wasn't just about adding new features. A big part of my work was understanding why something wasn't working and how to fix it
🔧 What I worked on today
✅ Continued developing the Project Board
✅ Worked on the Create Task workflow
✅ Connected the task form with the backend API
✅ Worked with project IDs and task IDs
✅ Connected frontend requests with Express routes
✅ Worked on saving task information in MongoDB
✅ Worked with task properties such as:-
Task title
Description
Priority
Status
Assigned user
🐛 Where I got stuck
One thing I’m learning from this project is that a feature can look simple from the frontend, but behind it there are many connected parts
For example:
Frontend → API request → Express route → Authentication middleware → MongoDB → Response → Frontend
If even one part doesn't match, the feature may fail.
I faced issues with things like API routes, project IDs, task model fields, and connecting the frontend form correctly with the backend.
Instead of simply moving on, I tried to understand where the request was going, what the backend was receiving, and where the error was happening.
🧠 My biggest lesson today
I'm realizing that becoming a developer doesn't mean memorizing every line of code.It's more important to understand:
What am I building?
Why do I need this code?
How does the frontend communicate with the backend?
How does the backend communicate with the database?
What happens when something goes wrong?
I'm using AI and VS Code assistance to make my development process faster, but my goal is not just to copy code.
I want to understand the flow and logic, so I can modify the code, debug it, and eventually build similar features myself.
🚀 Day 12 complete
This project is teaching me something that tutorials cannot fully teach:
Real development means building → getting stuck → debugging → understanding → fixing → improving.
Still learning. Still making mistakes. Still building.
2/30 days completed. One step closer to becoming a better full-stack developer. 🚀
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started