Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found

All solutions

  • Submitted


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

    For this project, I focused on implementing a clear and well-structured logic. Each functionality is encapsulated in distinct functions with clearly defined responsibilities, such as password generation, strength evaluation, and security bar updates. This approach ensures that the code is both maintainable and easily extensible for future improvements.

    I also paid close attention to thoroughly commenting the code, making it easier to understand and follow for anyone who might work on it.

    The event management is well-structured as well. Event listeners are properly attached to the DOM elements, with clear conditions for activating the different options. The handling of password state and its related options is efficient, with synchronized updates to the interface.

    Overall, the project is built to be both robust and user-friendly.

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

    One of the main challenges I encountered was the thought process behind the implementation, which required careful planning. I spent time ensuring that I followed best practices to deliver solid, maintainable, and readable code.

    I had to do some research to implement certain features, particularly the password generation logic, the dynamic visual updates when manipulating the slider, and the rendering of the security level bars. Additionally, I looked into how to implement the copy-to-clipboard functionality, ensuring it worked seamlessly within the app. Overcoming these challenges involved learning and applying new techniques while maintaining code quality.

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

    I would like to get a review on the logic part of the code, specifically to see if there might be an alternative approach that could improve it.

  • Submitted


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

    I’m most proud of having applied a coding pattern typically associated with declarative programming frameworks like React, but using TypeScript alone. This approach ensured the proper synchronization between data and the UI, enhancing both the robustness and maintainability of the application. Leveraging TypeScript’s features to manage state and update the UI seamlessly was a significant accomplishment and demonstrated my ability to adapt advanced programming concepts to different contexts.

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

    One of the main challenges I encountered was implementing the logic for calculating tips and totals. It required significant time for research and reflection to ensure accuracy and to handle various edge cases. I tackled this challenge by breaking down the problem into smaller, manageable parts, and researching best practices for real-time calculations. I also tested different scenarios to validate the calculations and ensure that the application provided correct and reliable results.

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

    Would like to be reviewed on the quality of the code if you know Ts, could be nice. Add me on github/linkedIn and let's share

  • Submitted


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

    1. Clear Interface and Enum Definitions The use of interfaces (Activity, Timeframes, TimeframeData) and enums (Timeframe) demonstrates a well-structured approach to data modeling. This improves code readability and maintainability, while also enforcing type safety throughout the application.
    2. Asynchronous Data Fetching The fetchData function uses async/await syntax for handling asynchronous operations. This results in cleaner, more readable code compared to nested callbacks, and makes error handling more straightforward.
    3. Separation of Concerns Functions like updateDashboard, setTimeframe, and displayError each have a single, clear responsibility. This adheres to the Single Responsibility Principle, making the code easier to understand, test, and maintain.
    4. State Management The use of a global currentTimeframe variable and the setTimeframe function shows a simple but effective approach to state management, ensuring that the application's state is consistently updated and reflected in the UI.
    5. Flexible and Reusable Code Functions like getTimeframeText demonstrate how the code is designed to be flexible and reusable. This reduces code duplication and makes future modifications easier.
    6. Use of Modern JavaScript Features The code leverages modern JavaScript features like template literals, arrow functions, and optional chaining. This results in more concise and readable code.
    7. Consistent Code Style The code maintains a consistent style throughout, which is crucial for readability and maintainability, especially in team environments.
    8. I added modern CSS animations to enhance the overall user experience.

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

    At the beginning, I coded the cards using a mix of grid for the overall layout and relative/absolute positions for overlapping the cards. It turned out that mixing these two layout algorithms made the responsive design extremely complex to manage. I had to break down all my code and redo it with a different approach. It was a real challenge for me to find the right arrangement of the elements.

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

    Again, if a TypeScript expert comes across this, you can find my file here: src/home.ts. I would appreciate feedback on the code. Thank you in advance. Feel free to add me on GitHub and LinkedIn to connect if you wish; just visit my profile. See you soon and happy coding.

  • Submitted


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

    I am proud of several aspects of the project, particularly the implementation of TypeScript for enhanced type safety. This not only made the codebase more robust but also improved the overall developer experience with better autocompletion and error detection.

    Organizationally:

    •	I grouped DOM elements within an interface, which brought a structured approach to handling DOM manipulations.
    •	The code is segmented into smaller, more specific functions, emphasizing clarity and readability.
    •	By focusing on reusability, utility functions can be easily reused across different parts of the project, reducing redundancy and promoting efficient coding practices.
    •	The modular structure of the codebase ensures that future modifications are straightforward and less error-prone.
    

    Additionally, I implemented email field validation both at the HTML level and using a regex tailored to the expected data type. This dual-layered approach enhances the reliability of the form validation process, ensuring that incorrect email formats are caught early.

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

    I have a strong recent experience with React and am accustomed to a declarative programming approach rather than an imperative one. The challenge here was to seriously reacquaint myself with vanilla JavaScript for this project, utilizing a functional programming paradigm.

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

    TypeScript Code Logic

    • I am interested in having a review of my TypeScript code to identify any areas where the logic can be improved.
    • I would appreciate suggestions on how to enhance the type safety and overall structure of the code.

    Code Organization and Structure

    Feedback on how the code is organized, particularly with respect to the separation of concerns and modularization, would be valuable.

    • Are there any best practices I can adopt to make the code more maintainable and scalable?

    Form Validation Approach

    • I implemented email validation both at the HTML level and using regex. I am open to constructive criticism on this approach and any recommendations for more effective methods or libraries.

    Performance Optimization

    • Any tips on optimizing the performance of my code, especially with respect to form handling and DOM manipulation, would be greatly appreciated.

    Usability and User Experience

    • Suggestions on how to improve the user experience, particularly in terms of providing clear and actionable feedback for form validation errors.
  • Submitted


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

    I really enjoyed the challenge presented by this project, which encouraged deep reflection on the behavior of the share component and how it adapts and positions itself in both desktop and mobile versions. For the desktop version, I used TypeScript to manage the display of the component with an event listener and a toggle class to show/hide the element, applying CSS properties tailored to this effect. For the mobile view, I used pure CSS to manage the component's behavior. This project allowed me to reinforce my HTML and CSS skills while also providing an opportunity to implement TypeScript in a practical context. The contrast between using TypeScript for interactive elements on desktop and relying on CSS for mobile layout adaptations was particularly instructive, showcasing different approaches to responsive design.

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

    The main challenge I encountered was the initial planning phase. It took some time to reflect and devise an effective solution to the problem presented in this challenge. I had to carefully consider different approaches for both desktop and mobile versions, weighing the pros and cons of various techniques

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

    I would greatly appreciate if the community could take a detailed look at my code and provide feedback on potential improvements or alternative solutions. I'm particularly interested in hearing about more efficient or elegant ways to handle the responsive behavior of the share component. Some specific areas I'd like input on include:

    The efficiency of my TypeScript implementation for the desktop version. The CSS approach used for the mobile layout - are there better techniques I could have employed? Overall code structure and organization - how could it be improved for better maintainability?

    I'm open to all constructive criticism and suggestions. Your insights could help me refine my skills and approach future projects more effectively. If you'd like to connect further or see more of my work, feel free to follow me on GitHub . I'm also active on LinkedIn, and I'm always eager to network with fellow developers and learn from their experiences. Thank you in advance for your time and expertise!

  • Submitted


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

    I am pleased to have been able to delve deeper into certain CSS techniques, particularly the stacking of elements on top of each other. Additionally, I managed to modify the arrangement of elements in complex layouts, such as the header that loads different images depending on the viewport size. Overall, I am satisfied with the result.

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

    I had to do some research for the layout and loading of images for the header, the number above the footer, and how to integrate a background image with an overlay color to achieve the desired effect on the footer.

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

    As usual, I welcome any feedback that can help me improve. Please feel free to provide a detailed review; it’s the ultimate goal of every project here. Thank you in advance, and you can add me on GitHub

  • Submitted


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

    I had a great time experimenting with grids, particularly utilizing grid-template-areas and grid-area properties this time. It allowed me to further enhance my skills in using media queries and responsive layouts in general.

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

    Integrating the SVG background on the first card required some research, as did creating the border around the characters’ avatars.

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

    I look forward to your advice if I ever need to improve parts of the code.

  • Submitted


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

    I was able to improve my understanding of media queries by using multiple breakpoints throughout the design integration process. I applied the responsive principles learned during the review of courses recommended by the platform.

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

    I encountered challenges while implementing the desktop layout grid, particularly in adapting it across different breakpoints. Initially, maintaining consistency and alignment across various screen sizes posed difficulties. To overcome this, I systematically adjusted the grid layout using @media queries, ensuring each breakpoint preserved the integrity of the design while accommodating different device dimensions. This iterative approach allowed me to refine the grid’s responsiveness effectively, achieving a cohesive layout experience across all targeted devices.

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

    please let me know if there is anything I could do better on this one. Thank you for reviewing my code. :)

  • Submitted


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

    Reflecting on the project, I am particularly pleased with how I implemented responsive design principles to ensure the product preview card component functions seamlessly across diverse devices. This involved using flexible layouts and media queries to adapt the interface from mobile screens to larger desktop displays, enhancing user accessibility and interaction.

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

    One of the main challenges I faced was mastering the element for loading different-sized images based on media queries, requiring focused learning and experimentation to integrate effectively into the project.

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

    I don’t need help with any specific areas of my project at the moment.

  • Submitted


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

    I learned new things, such as the possible styling of ordered and unordered lists. I was able to apply more responsive design in this project compared to previous ones.

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

    The styling of lists and tables presented challenges.

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

    No help needed here either.

  • Submitted


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

    I'm proud of using flexbox for responsive design and adding hover animations to links. The project was cool and not too difficult. Next time, I might challenge myself with more advanced techniques, but overall I'm satisfied with how I applied and reinforced my CSS skills in this project.

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

    I had to make some research to find that CSS property : white-space: nowrap;

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

    No help needed thanks

  • Submitted


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

    I'm proud of effectively implementing responsive design using SASS mixins, which streamlined the development process and resulted in a highly adaptable layout. Next time, I'd like to explore more advanced SASS features to further enhance the project's efficiency and maintainability.

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

    During this project, I discovered that it's possible to customize the cursor with a PNG file, which was an intriguing learning experience. This revelation opened up new possibilities for enhancing user interaction and visual feedback in web design.

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

    No help needed thanks

  • Submitted


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

    I learned how to use the Perfect Pixel chrome extension throught this project to deliver a perfect web integration. This project allowed me to come back on Figma and practice again with the app design

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

    nothing special with my experience it was not a problem

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

    no help needed