I do find that everything related to Python is especially badly documented and/or maintained. Maybe I’m just not looking the in right place though? I don’t generally use Python as my primary language.
I do find that everything related to Python is especially badly documented and/or maintained. Maybe I’m just not looking the in right place though? I don’t generally use Python as my primary language.
Usually API docs are tucked away inside a “developer dashboard” or whatever they decided to call it. So I think you can assume at least moderate API and web development knowlege and programming skills.
You should read up on what’s called “rubber ducky” debugging
Here’s a link to a comic that summarizes the idea succinctly: https://www.smbc-comics.com/comic/the-rubber-duck-method Wikipedia article here: https://en.wikipedia.org/wiki/Rubber_duck_debugging
In those kinds of situations you need to remember to try to break the problem down into simpler sections to identify where the problem lies. One of the first steps would be to run SELECT * FROM mainWorkSpace WHERE user_id = @user_id
and see if that returns anything.
One place I worked at recently was still using Node version 8. Running
npm install
would give me a mini heart attack… Like 400+ critical vulnerabilities, it was several thousand vulnerabilities all around.