🚀 Getting Back Into Building Mode

After dedicating time to enhance my programming abilities, I've opted for a more systematic method to become job-ready as a software engineer. Rather than attempting to master everything simultaneously, I'm concentrating on grasping how various software development components interact. Presently, I'm studying frontend technologies like JavaScript and React.js, backend systems made with Node.js and Express.js, Python's Django framework, as well as database management and SQL, data structures, algorithms, and generative AI.

However, I'm adopting a novel learning approach. I aim to not only complete tutorials but truly comprehend the underlying processes. For instance:

React.js communicates with APIs, which in turn interact with backend services. These services handle authentication and middleware, manage business logic, interact with databases, and then return responses back to the frontend, which is displayed as the React UI.

Ultimately, I aspire to understand how AI/ML can be seamlessly integrated into these systems. My current learning cycle follows this pattern: Learn → Build → Break → Debug → Understand → Improve. If something doesn't function as expected, I don't want to hastily copy a solution. Instead, I want to understand the reasons behind the failure - where the request stalled, what data was transmitted, what the server received, and what the database returned. How can I avoid encountering this issue in the future?

My objective is to prepare myself for entry-level positions in software development and full-stack development. I will be documenting my learning process, sharing the challenges, errors, puzzling concepts, projects, and solutions I encounter along the way. By documenting this journey, I hope to maintain consistency and potentially assist others who are learning to develop from the ground up. Let's see how this path unfolds.