Design comparison
Solution retrospective
This was a really fun project! What I thought was a pretty simple project (in the bigger scheme it actually is), turned out to be much more complex. Soon, after a few hours of work, I was working with some pretty messy code and bugs that were hard to deal with.
What is the best way to structure a project like this, where there are multiple "states"? I did do a little bit of planning before I started coding, but obviously, I could not account for all of the possibilities on paper. While coding, I separated most big actions into function blocks, but I kind of threw together the relationships between the functions on the fly.
I know in digital logic gates, people would draft up things like "finite state machine diagrams", and I was wondering if there was some kind of thing like that for programming. I'd greatly appreciate any resources or tips on this kind of "structuring code" issue!
Community feedback
- @palgrammingPosted over 3 years ago
Yes this is not a easy project here
- currently no hover color state for the buttons
- one cannot add .5 + .5 or 35 + .5
- it would be good to add keyboard inputs
1@darenhuaPosted over 3 years ago@palgramming All great tips! As the project went on it got pretty scuffed, but in the end, I decided to drop the project at a "working" state because I think I would learn more from doing more projects instead of driving myself mad fixing bugs.
0@palgrammingPosted over 3 years ago@darenhua yep that is what happened to mine also. I am still working on mine but little at a time
0 - @darenhuaPosted over 3 years ago
AHH Apologies everyone! I was too excited to post the solution after finishing javascript work that I forgot I needed to make the page responsive...
0
Please log in to post a comment
Log in with GitHubJoin 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