All solutions

What are you most proud of, and what would you do differently next time?

I used Next.js for the first time, which was very interesting and educational. Additionally, I believe I successfully created a full-stack application using Firebase as the backend. I’m particularly proud of figuring out many new technologies and implementing complex functionalities. If I were to do it again, I would spend more time planning the application’s architecture to avoid some of the difficulties I encountered during implementation.

What challenges did you encounter, and how did you overcome them?

One of the challenges was that I had to read a lot of documentation to understand and implement various features. This slowed down the process but also helped me gain a deep understanding of the technologies. Another perennial problem is working with forms. In this project, I chose to work with Formik, and although there were some roadblocks, everything worked out in the end. Solving form-related issues involved continuously reading the documentation and looking for real-world usage examples.

What specific areas of your project would you like help with?

I would be very grateful for any feedback :)

What are you most proud of, and what would you do differently next time?

I'm most proud of successfully integrating multiple APIs into the Vue Clock App and creating a seamless user experience. Next time, I would focus more on code organization and modularization to improve maintainability and scalability. Additionally, I would invest more time in testing to ensure robustness and reliability.

What challenges did you encounter, and how did you overcome them?

One challenge I encountered was handling asynchronous data fetching and rendering in Vue components. I overcame this challenge by leveraging Vue's lifecycle hooks and asynchronous methods, ensuring that data is fetched and components are updated appropriately.

What specific areas of your project would you like help with?

I would appreciate help in optimizing the performance of the Vue Clock App, especially in terms of reducing initial loading times and improving rendering efficiency.

What are you most proud of, and what would you do differently next time?

I'm proud of solidifying my Redux skills by creating a store for the application and crafting custom styles using Tailwind CSS (great practice for me). However, next time, I'll take a moment to carefully consider the most optimal approach for the project before diving in. Rushing into routing initially turned out to be unnecessary, leading to substantial rework under Redux.

What challenges did you encounter, and how did you overcome them?

There weren't major hurdles, but I did spend some time fine-tuning style conditions for selected, correct, and incorrect answers. Applying different classes based on the situation helped me address this task effectively.

What specific areas of your project would you like help with?

I'd appreciate insights on simplifying and enhancing code readability while optimizing specific aspects of the project for better efficiency and scalability. Additionally, I'm interested in streamlining certain project elements to improve its overall performance.

Creating the Tic Tac Toe project proved to be both engaging and challenging. 😅 Despite the seemingly straightforward concept of the game, it took approximately 33 hours to bring it to life using JavaScript. 🕰️ The main difficulties arose from the need to understand the intricacies of game logic, ranging from displaying hover effects when hovering over a player's move to implementing a smarter algorithm for the computer's moves. 🤔

One area of uncertainty in my code lies in the sheer number of JavaScript files – instead of the anticipated couple, I ended up with 11. 😱 Attempts to reduce the codebase didn't yield the desired results. I would greatly appreciate any feedback, especially if you come across any bugs. 🐞 While tests have been conducted and everything should be functioning correctly, there's always a chance something might have slipped through the cracks. Please feel free to reach out with any issues or suggestions! 🙏

Overcoming the intricacies of integrating Firebase posed a notable challenge, and grappling with webpack, particularly given my first-time engagement with the tool, required a substantial investment of effort.

My confidence in the flawless and optimal operation of the system remains somewhat tentative :)

An issue has arisen in the application flow: following the manual reordering of tasks, subsequent updates, such as sorting by status or marking a task as completed, disrupt the established sorting order. This anomaly appears to be tied to interactions with the Firebase database. I would greatly appreciate any guidance or assistance in addressing this specific challenge.

1. What did you find difficult while building the project?

   • It was challenging to position the images within the hero section, and I also had to learn Sass.

2. Which areas of your code are you unsure of?

   • Everything seems to be fine at the moment.

3. Do you have any questions about best practices?

   • I would like to know if there's a better way to structure my code. Additionally, I'm curious if it's a good practice to use unordered lists (ul) when there are similar elements, or if it's acceptable to use multiple div elements consecutively instead.