I like the fact that you're leveraging books more often. That's a good move.
I'd suggest to draw your mental model/design and go through it step by step and figure out how to do each one, before writing any code.
A lot of your questions will raise here and you'll check a book or Google the concept of what you are trying to do and apply it to your use case.
Also, I would recommend not to default to Stack Overflow if something doesn't work. First, trace back your implementation, debug and/or follow the flow and try to isolate where is not working. Think about it for a while and read the necessary documentation (if using a library/framework or the specific language docs), chances are you'll figure out why this is not working.
If you didn't find out why, you'll probably come up with better keywords to search instead of just an error message.
Good luck!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You're going in the right direction, congrats!
I like the fact that you're leveraging books more often. That's a good move.
I'd suggest to draw your mental model/design and go through it step by step and figure out how to do each one, before writing any code.
A lot of your questions will raise here and you'll check a book or Google the concept of what you are trying to do and apply it to your use case.
Also, I would recommend not to default to Stack Overflow if something doesn't work. First, trace back your implementation, debug and/or follow the flow and try to isolate where is not working. Think about it for a while and read the necessary documentation (if using a library/framework or the specific language docs), chances are you'll figure out why this is not working.
If you didn't find out why, you'll probably come up with better keywords to search instead of just an error message.
Good luck!