ReactJS App Development Challenges and Lessons Learned

My #backendDevelopment #bugFixes I have been assigned for my team's #ReactJS / #Python food-related app are taking longer than expected, again. (also #Flask, #JWT, #SQLAlchemy are used) The level of understanding of code required requires time and human effort. That is why my team and I are prepared to take on new projects in this era of automation, because, unlike our counterparts who are entering this field by copy-pasting without first understanding, we understand (though far from expert-level), or are constantly and actively growing in our understanding, of the basics of what's going on under the hood and what to look for when editing code (unlike "black boxes" where you don't know and can't control what's under the hood). We are now deciding that the MVP will be a working model but more changes will have to be made after that before it is production-ready. That's okay, because it's better to ensure a secure and stable application in order to test it with real users. Right now the database is only being tested locally. But this app's concept is genuinely novel and something that would benefit at least one company out there, maybe more, even beyond the food industry -- and no, it is not an application that claims to run on "AI" -- it is funny how that fact actually makes us stand out. I am eager to share more specifics about it and my team members' GitHub links if and when it clears the development phase. Lessons learned: build one layer at a time, and don't rush a professional project if it will result in a bad or unreliable product. #HammondSoftware

  • graphical user interface, text, application, chat or text message

Curious why you chose flask over fastApi?

To view or add a comment, sign in

Explore content categories