Project Review

[TechProblemSolver]

Select Topic Area

Product Feedback

Body

Dear Reader,

Can someone please review this project and give feedback on them? I would appreciate it.
Here is the repository link: https://github.com/DenzelDCB/WeatherAppPython

The purpose of the weather app code is to implement data mining in python and getting data from a weather API and show the user the weather for that latitude and longitude location. Then I decode it and get the data from the backend.py (getWeather.py) and bring it to frontend.py (test.py).

There is also an html file of the full thing, along with the link.

Sincerely,
TechProblemSolver

[queenofcorgis]

Thanks for posting in the GitHub Community, @TechProblemSolver !

We’ve moved your post to our Programming Help 🧑‍💻 category, which is more appropriate for this type of discussion. You are more likely to get a useful response if you are explicit about what type of feedback you're looking for, giving a few more details might help someone give you a nudge in the right direction.

Please review our guidelines about the Programming Help category for more information.

[TechProblemSolver]

I'm looking for a feedback on what they feel like should be changed, added, or removed.

[sumit1642]

bro you are asking this at the wrong place, and also no one is gonna review a project like this, but you can still try on sub-reddits lik r/coding , there are many more like it.

[varunpats]

Hey @TechProblemSolver,

I've reviewed your project on high level. Below are few points for improvement.

1. Backend (backend.py)

Strengths

• Uses requests to fetch data — simple and readable.
• API URL construction is straightforward.

Areas to Improve

• No exception handling — network errors will crash the app.
• Hardcoded latitude/longitude — should allow parameters.
• No logging — debugging would be harder if something fails.
• Response isn’t validated — if the API changes, it could break silently.
• getWeather.py logic could be modularized into smaller functions.
• File naming could be more descriptive: backend.py -> weather_backend.py

2. Frontend (frontend.py)

Strengths

• Likely serves HTML or calls backend endpoint directly.
• Simple data flow between backend and frontend.

Areas to Improve

• If it directly prints results, should handle JSON serialization properly.
• No CORS handling if accessed from browser frontend.
• No input validation before sending request to backend.
• File naming could be more descriptive: frontend.py -> app.py or weather_frontend.py

002.html file seems unrelated, should be removed from repo if it’s not part of the weather project.

Hope this is what you are looking for, thanks.

[varunpats]

Hey @TechProblemSolver, hope above response helped you. If so, could you please mark it as a answer? It'll help me, thanks.

[jawad-js]

Hey! I took a quick look at your WeatherAppPython repo — nice job connecting to the API and structuring it with separate backend and frontend files. Even as someone still learning Python, I can see you’ve kept the code readable.
Overall, looks like a solid starting point for a weather app. Keep building! 🚀

[sumit1642]

Who are u?

[TechProblemSolver]

Thanks to @varunpats for the analyzation.

[TechProblemSolver]

I am a software developer, why?