Skip to content
Submitted 6 months ago

Age Calculator App

CJ-Cepe•200
@CJ-Cepe
Preview site (opens in new tab)View code (opens in new tab)
This is a solution for...Age calculator app
  • HTML
  • CSS
  • JS
2junior

Design comparison

SolutionDesign

Solution retrospective

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

  • Most Proud of:

    • Practicing Sass (mixins, functions)
    • Implementing responsive design.
    • Making some design changes.
    • Expected Completion Time: 1-3 days
      • Actual: about a week (due to ADHD) 😑
    • Technologies used
      • 📄: HTML
      • 🎨: CSS (SASS)
      • 🖥️: Desktop First Design
      • 📅 : Date-fns

  • Changes for Next Time:

    • Implement unit testing.
    • Experiment with a web framework.
What challenges did you encounter, and how did you overcome them?

  • Challenges Encountered:

    • Dealing with dates in JavaScript, which lacks a built-in subtraction method, particularly when considering leap years.
    • Lack of references for exact dimensions or specific styles applied.
    • Lack of motivation to complete the challenge.

  • Solutions Implemented:

    • Used date-fns for date manipulations.
    • Applied the unit or style that seemed most appropriate.
    • Consumed snacks while working on the challenge as a source of dopamine fuel.
What specific areas of your project would you like help with?
  • Curious if the use of global variables is considered a bad practice.
  • Seeking suggestions for better elements to enhance semantic HTML.
  • Open to feedback if I’ve overlooked something or if there’s an issue with the logic or design.

Thank you

Community feedback

  • Koda👹•3,830
    @kodan96Posted 6 months ago

    hi there! 👋

    For your first question:

    Generally it's not a good practice to use and depend on global variables. You should encapsulate most of them into functions, so your code can run with better performance, and using global variables can cause unexpected behavior, especially if you use this a lot.

    In environments where JavaScript is used in concurrent contexts, global variables can introduce race conditions and concurrency issues, making the code prone to errors and difficult to debug.

    Following modular programming principles and encapsulation is a better way to handle things. You can also create closures. Of course sometimes it's just easier to use global variables, but it's better to use the least amount of them.

    Hope this was helpful 🙏

    Good luck and happy coding! 🙌

    Marked as helpful
    2
    CJ-Cepe•200
    @CJ-CepePosted 5 months ago

    @kodan96 Thank you very much 😊. I’ll read about and try encapsulation and modular programming, and reduce the use of global variables in my next projects. This was helpful, thankies again! ❤️

    0

Please log in to post a comment

Log in with GitHub

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord