All solutions

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

This is a simple Tip Calculator web application that helps you calculate the tip amount and total amount per person based on the bill amount, the number of people sharing the bill, and the desired tip percentage. The application also supports custom tip percentages. Real-time Calculation: Automatic calculation of tip and total amounts as you type.

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

#Javascript fetch Data with async/await

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

• Check the validation of the email when the user enters it. email.addEventListener('input', updateButtonState)
• Update submit button status and color based on email validity. function updateButtonState()
• Show or hide error messages depending on email validity.
• Change the color of the submit button when hovering in or out if the email is valid. onmouseover onmouseleave
• Display success notification and email value when the user presses the submit button and the email is valid. addEventListener('click', function)

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

Reflecting on my project, I am most proud of successfully implementing a smooth fade-in and fade-out effect on mouseover and mouseleave events, respectively. These animations enhance user interaction and provide a polished user experience.

One of the main challenges I faced was ensuring cross-device compatibility and smooth animation transitions. To address this, I utilized setTimeout to delay the display: none property, and animation & transform css, ensuring the effects perform reliably across different devices and event triggers.

Looking ahead, I aim to improve the codebase's structure for better readability and maintainability. This includes refactoring to streamline the logic and enhance overall code efficiency. By doing so, I believe the project will not only perform better but also be easier to maintain and extend in the future.

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

I'm confused between two properties:

• grid-template-columns and grid-template-areas Both can help complete this exercise. However, grid template columns have brought optimization in terms of time and neatness.

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

I was hesitant to choose between Flexbox and Grid to responsive for 4 cards. In the end I decided to choose Grid with grid-templete-areas property, because I thought maybe it would help more and faster than flexbox in this case.

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

Separate the featured image and content into two parts, so that responsive css style can be applied

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

The effort to write concisely and easily to understand, ensuring class reuse and uniqueness

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

How to make it as neat as possible, but still ensure comprehensibility. Make class names unique