After spending time learning and strengthening my development skills, I've decided to take a more structured approach to becoming job-ready as a software developer.
I'm not trying to learn everything at once anymore.
Instead, I'm focusing on understanding how different parts of software development actually connect.
🛠️ What I'm currently learning
Frontend
- JavaScript
- React.js
Backend
- Node.js
- Express.js
- Python
- Django
Database
- SQL
- Database design
Problem Solving
- Data Structures & Algorithms
AI
- Machine Learning
- Generative AI
- Prompt Engineering
- AI-assisted development
But there's one thing I'm changing in the way I learn.
I don't want to just complete tutorials and move on.
I want to understand what happens behind the scenes.
For example:
React
↓
API Request
↓
Backend
↓
Authentication / Middleware
↓
Business Logic
↓
Database
↓
Response
↓
React UI
And eventually, I want to understand where AI/ML can fit naturally into these applications.
🧠 My current learning cycle
I'm following a simple approach:
Learn → Build → Break → Debug → Understand → Improve
If something doesn't work, I don't want to immediately copy a solution.
I want to understand:
- Why did it fail?
- Where did the request stop?
- What data was passed?
- What did the server receive?
- What did the database return?
- How can I prevent the same problem next time?
I think this is the difference between knowing a technology and actually being able to develop with it.
🎯 My goal
I'm currently preparing for fresher opportunities in software development and full-stack development.
I'll be sharing what I learn here — including the mistakes, bugs, confusing concepts, projects, and solutions.
Hopefully, documenting the journey will help me stay consistent and might also help someone else who is learning development from scratch.
Let's see where this journey goes. 🚀
Learn. Build. Debug. Repeat.
Top comments (0)